DAMA
INTERNATIONAL SYMPOSIUM and WILSHIRE META-DATA CONFERENCE
April
28-May 2, 2002 – San Antonio Convention Center, San Antonio, Texas
Agenda is subject to change.
TUESDAY-THURSDAY SESSIONS
Tuesday, April 30, 2002
10:15 AM - 11:15 AM (Concurrent
Sessions)
The Same or Different: UML Class Diagrams & Entity Relationship Diagrams
Carrie Sherier
Data Architect
Williams Communications
Communication between data modelers and
object modelers is often difficult. One of the reasons for this is different
terms (“lingo”). In reality, many of the class diagram-related terms have
corresponding terms in the data modeling world. This presentation will present
UML modeling terms from a data modeler's perspective. Once we have a foundation
of terms, we will compare data models to the corresponding class diagram models.
For example, given a many-to-many relationship: How is this shown in the class
diagram? In the relational data model? We will also study inheritance notation
in UML and it’s impact on super/sub-types in the relational data model.
The attendee will learn about:
Object modeling terms
Differences between object models
& ERD’s
Super/sub-types & Inheritance
Reasons to create both Object Models
& ERD
Examples of relational models and corresponding class models
Carrie Sherier has worked in the data modeling field for over 13 years. The first ten years were for a natural gas pipeline company, spending the last few years designing the data model for a major facility management application. She currently works for a major telecommunications company as a Data Architect. Carrie has been working on object-relational projects, utilizing class diagrams to design objects, and implementing them in a relational database. She has been involved in leading the company's data modelers as they make the paradigm switch to object modeling.
From Entities to Stars, Snowflakes, Clusters, Constellations and Galaxies: A Methodology for Data Warehouse Design
Daniel Moody
Associate Professor, Norwegian University
of Science and Technology and
Senior Research Fellow, Monash University
This presentation describes
a method for developing dimensional models from traditional Entity Relationship
models. This can be used to design data warehouses and data marts based on an
enterprise data models. The
advantage of this is that it provides a more structured design procedure, which
is based on the underlying relationships among the data. This allows data marts to be developed in an architected
manner and simplifies extraction from production systems. The first step of the method involves identifying “event”
entities in the data model¾these
correspond to fact tables in dimensional models. The second step involves identifying hierarchies in the model¾these
correspond to dimensions in dimensional models. The final step involves collapsing these hierarchies and aggregating
transaction data to form dimensional models. A number of design alternatives are presented, including a flat schema, a
terraced schema, a star schema and a snowflake schema. We also define a new type
of schema called a star cluster schema. This
is a restricted form of snowflake schema, which minimizes the number of tables
while avoiding overlap between different dimensional hierarchies. Individual
schemas can be collected together to form constellations or galaxies. The method is illustrated using a simple example, and also with a real
world case study.
Daniel Moody holds a joint position as Associate Professor at the Norwegian University of Science and Technology and Senior Research Fellow in the School of Business Systems at Monash University. He is the National President of the Data Management Association (DAMA) and Australian World-Wide Representative for the Information Resource Management Association (IRMA). Daniel has held senior data management positions in some of Australia’s largest commercial organizations, and has consulted in a wide range of organizations both in Australia and overseas, including Canada, Singapore, Hong Kong, Indonesia, Taiwan and South Korea. He has held academic positions at a number of Australia’s leading universities, including the University of Melbourne, the University of New South Wales, the University of Queensland and Queensland University of Technology. His research interests include data modeling, information resource management, information economics, data warehousing and knowledge management. He has published over 50 papers in the IS field, in both practitioner and academic forums, and has chaired a number of national and international conferences.
Data Stewardship: If only I knew then, what I know now
Carol Knight
Principal Consultant
Knight Consulting, LLC
Throughout my career, I’ve been plagued with a naïve, idealistic, assumptive approach to implementing programs that will enhance our ability to manage data effectively. After all, who wouldn’t want to support this lofty goal? Each effort rewards me with valuable lessons learned. My recent attempt to define and implement a distributed data stewardship program within a large organization reinforced prior lessons learned, provided some unexpected “gotcha’s”, and established in my mind some specific prerequisites before I would embark on this endeavor again. This presentation is intended to save other zealous data management practitioners from experiencing my pain and perhaps offer an opportunity to achieve more gain.
What are we trying to accomplish with
data stewardship?
Who are the key players and what are
their perspectives on the issues?
How can we make this a WIN – WIN –
WIN – WIN ….. (for all involved) ?
What do you absolutely have to have a
commitment to, or already have in place to allow (not ensure) success?
What will automatically ensure
failure?
Why do we keep trying?
Carol Knight is an independent data management consultant. She has over 20 years experience in a variety of roles within the data management arena including implementing data management functions; managing DBA and DA staff; evaluating data management tools; creating logical data models; facilitating JAD sessions; designing data management programs, policies, and procedures; and applying methodology to processes. Carol has been a conference speaker on data management topics and an avid supporter of the Atlanta chapter of DAMA.
Managing Business Intelligence Programs - the Seven Streams Approach
Derek Strauss
CEO
Gavroshe USA Inc.
Business Intelligence (BI) is not a
project: you never complete BI. It is a program, ongoing, forever changing and
becoming more and more honed and sophisticated, as the business needs change.
But how do you achieve this? And once you have 'done it', how do you sustain it?
This presentation describes a proven BI Planning Framework , which assists
organizations to achieve:
A thorough understanding of BI’s
total cost of ownership
Better scoping of effort and less
overrun risk
Better understanding of the 'big picture' and interdependencies
Ongoing/sustained success with BI
There are 7 major streams of activities
which need to be simultaneously initiated, concurrently driven, co-ordinated and
monitored:
STREAM 1: Corporate Data Model
STREAM 2: Corporate Knowledge
Co-ordination
STREAM 3: Corporate Information
Factory Development
STREAM 4: Data Profiling and Mapping
STREAM 5: Data Cleansing
STREAM 6: Infrastructure Management
STREAM 7: Data Quality Management
Many BI Programs have failed because of a lack of understanding of the real issues. The paper defines each stream and the activities inside each stream giving description, deliverable, dependencies, and duration. It also discusses team (size, skills, role), and risks and pitfalls. Attendees will learn how to establish and sustain a successful BI Program.
Derek Strauss has 25 years IT industry experience, 15 years of which were in the Information Resource Management (IRM) field. He established Data Resource Management, Architecture and IRM Functions in several large Corporations using the Zachman Framework as an architectural basis. He holds a BSc (Hons) degree from Witwatersrand University. Derek has spoken at several international conferences on IRM-related issues, including a series of seminars on BI and Data Warehousing in Eastern Europe and South Africa. He has experience in the Financial, Manufacturing, Retail, Government, Utility, and Distribution sectors of the economy and was Program Manager for a $45 million Data Quality Improvement Initiative in a large USA Bank.
Meta Data Partnerships: The Key to Populating the Dictionary
Stan Slossberg
Director, Data Administration
CIGNA
A company can bring in a repository
tool, and architect it into the development and production environments.
However, metadata is knowledge which is most often stored in
the heads of individuals who have other, more mission-critical tasks to perform.
Providing dictionary definitions is not one of those tasks. This presentation shows how CIGNA has developed an approach which ensures
that quality data definitions are provided to Data Administration to form a
robust, completely defined metadata repository.
The REAL issue is how to get the business community to provide and validate business names, definitions, allowable values and business rules. Attendees will learn a simple approach to creating successful partnerships which will bring definitions to the table.
Stan Slossberg has 20 years in Data Administration, from dictionary/repository administrator to metadata architect. He is Chapter Founder and served as 3-term President of the Connecticut Valley DAMA Chapter; served on the Board of Officers, DAMA Boston. He is also a member of TDWI. He has designed/deployed customized repository solutions, including CIGNA's current site, supporting 42,000 employees worldwide, and getting over 8,000 hits a week. The implementation continues to grow into a more robust metadata portal. Stan has spoken at DAMA and other DA and repository sessions in Dallas, Boston, Chicago, Seattle, and other locations. Besides notable recognition in the Data Management field, he has also received the CTM certification from Toastmasters International, and has distinguished himself by receiving the Highest Level Achievement Award from Dale Carnegie.
Common Warehouse Metamodel (CWM): An Introduction to the Standard for Data Warehouse Integration
John Poole
Distinguished Software Engineer
Hyperion Solutions Corporation
Dan Chang
Member of the
Database Technology Institute
IBM
Doug Tolbert
Consulting
Engineer
Unisys Corporation
David Mellor
Consulting
Engineer
Oracle Corporation
The Common Warehouse Metamodel (CWM) is
a technology standard of the Object Management Group (OMG) for meta data
integration in the data warehousing and business analysis environments. CWM
provides the long sought-after, common language for describing meta data, based
on a shared, vendor-neutral metamodel and corresponding XML-based meta data
interchange facility. CWM is rapidly gaining momentum within the data
warehousing and business analysis communities and is being incorporated into
various vendors' next generation of data warehousing products and tools.
The objective of this presentation is to
provide a comprehensive overview of the CWM standard. The primary topics covered
include:
The value proposition for CWM: How CWM
enhances return-on-investment.
A survey of CWM's foundational
technologies (e.g., UML, MOF, XML, XMI).
An architectural overview of CWM.
How to use CWM to model and
interchange meta data.
How CWM relates to other standards (OMG's
MDA, CORBA, XML, and Web-oriented interchange protocols).
Current developments within the CWM
effort (e.g., CWM Web services and meta data interchange patterns).
Closely-related efforts within the
Java Community Process (JMI, JOLAP, JDM).
Attendees will learn about:
How CWM enhances meta data ROI.
The basic concepts and components of
CWM.
How to use CWM to construct
fully-integrated data warehouses, supply chains, and analysis environments.
How CWM relates to other current
interoperability standards.
Current developments occurring within
the CWM effort.
Awareness and understanding of CWM is crucial for the data warehousing and business analysis communities, because CWM is the only industry-accepted standard for meta data integration. CWM promises to greatly enhance data warehousing and supply chain return-on-investment by lowering tool integration costs and allowing for the easy combining together of best-of-breed tools, products, and applications.
John Poole is a Distinguished Software Engineer at Hyperion Solutions Corporation. He is one of several co-authors of the Common Warehouse Metamodel (CWM) within the Object Management Group (OMG) and currently leads the Java OLAP Interface (JSR-69) technology effort within the Java Community Process. He holds a B.S. degree in Applied Mathematics from Southern Connecticut State University, and an M.S. degree in Computer Science from the Polytechnic University, New York.
Dan Chang is a member of the Database Technology Institute at IBM Silicon Valley Laboratory. He has led the CWM standardization effort within the OMG since its inception in 1998 and co-chairs the OMG's CWM Revision Task Force. Dr. Chang holds a Ph.D. degree in Computational Chemistry from the University of Chicago and is a visiting professor at San Jose State University.
Doug Tolbert is a Consulting Engineer at Unisys Corporation. He is one of several co-authors of the CWM within the OMG. Dr. Tolbert is a specialist in database management systems, application development environments and related technologies, and has written and lectured on databases and meta data at industry conferences and universities for over twenty years. Dr. Tolbert holds a Ph.D. in Genetics from the University of California, Davis.
David Mellor is a Consulting Engineer at Oracle Corporation. He has been working with Multidimensional and Relational Technologies for Oracle for over 10 years. He is one of several co-authors of CWM within the OMG. He has designed and developed a variety of products specializing in meta data and multidimensional and relational technologies. Mr. Mellor currently co-chairs the OMG's CWM Revision Task Force.
Tuesday, April 30, 2002
11:25 AM - 12:25 PM (Concurrent
Sessions)
Model "Status" for DW/BI, Business Rules and CRM Success
Henry Feinman
Data Architect
HJF
Information Solutions
"Status" is a cornerstone of business relationships and yet is rarely understood or modeled correctly. Understand and model Status to fully exploit Data Warehousing, Business Rules, and Client Relationship Management.
Attendees of this session will learn to correctly model Status; to make your database capture history accurately and derive data mart measures and facts from situations where none seem apparent. You will learn to establish a solid Status model without which it is impossible to know which business rules apply.
This is important because client and
account status are natural business concepts that are seldom modeled
effectively. The reasons for this are varied, but can be overcome at the start
saving effort and resources. Correctly modeled status gives us new, critical
information for our Decision Support environment. It ensures accuracy of
classifications needed for day to day dealing with client relationships,
enhancing effectiveness in both CRM and Business Rules contexts.
The Dimensional Model is not Normal -
Why is it successful?
What do DW facts have to do with
Status?
What do Hierarchies and Status have in
common?
Barriers to Correct Status Modeling:
-
Status Polluters
-
DBMS support for temporal data
-
Clouded Perceptions
Party Relationships and Status
Application of correct Status Models:
-
Data warehousing
-
Business rules
-
CRM
Henry Feinman is an information architect who has consulted with the top three banks in Canada as well as Canada’s largest City. Over 21 years of IT experience Henry has implemented operational and informational systems in manufacturing, finance and government sectors. He has worked with several data warehousing projects over the past 8 years, performing roles in data warehouse architecture, data architecture, and metadata management. Most recently, in the role of data warehouse architect, he has helped the City of Toronto implement their Enterprise Data Warehouse program and their first two datamarts.
The Selling and Re-selling and Re-selling of Information Management
Larry Dziedzic
Senior Information Management Architect
Johnson & Johnson
One of the critical requirements of any
Information Management (IM) group is the advertising of the unique functions
that IM group performs for the company. This presentation will look at a ways to
sell and to continue to re-sell the functions of IM.
Each IM groups always needs management support, but they also need to continue to help themselves by interviewing, surveying, training on the functions they perform. This presentation will provide details and examples of tools to help promote IM.
As Senior Information Management Architect for Johnson & Johnson, Larry Dziedzic is responsible for supporting global data standardization, as well as consulting on process and modeling standards for the worldwide Consumer group. This includes supporting data standardization of global ERP applications, defining data stewardship functions and interfacing with the worldwide Pharmaceutical and Medical Devices and Diagnostic groups. Larry is a Past President of Data Management Association (DAMA) in New Jersey USA, and is VP of Operations for DAMA International. Larry has presented papers at both DAMA International and DAMA US events, and also at the Enterprise Data Management Conference in Sydney, Australia. A former adjunct college instructor, Larry often guest lectures to information systems classes at the university level.
Real-life Success Story: First Steps
in Consolidating Data into a Single Enterprise Architecture
Mark Ouska
Information Architect
Minnesota Department of Commerce
Steve Farrell
Senior Business Analyst
Advanced Strategies, Inc.
Data standards are often difficult to
define and even harder to implement. This presentation describes the successful
data standards implementation at the MN Department of Commerce. The effort was
kicked off to address inequities in the core application suite used to manage
the agency’s information resources. It was defined as having an agency-wide
perspective to reign in the disparate “data puddles” and application
menagerie that was quickly becoming unmanageable with the goal of having a
consistent applications architecture serving a smooth flowing river of data.
This presentation will cover the critical success factors, noting the risks and
identifying the immediate and long-term benefits.
Detailing the Project Definition that
kept the project on track
Identifying the before and after data
standards
Explaining how users were kept at the
center of the effort
Discussing the integration of data
standards, project methodology and development standards
Demonstrating the value of working
with a vendor
Documenting the business impact of
data standards
There are many presentations of what could be done but few that cover the full breadth from concept to deployment and fewer yet that document a successful effort after it has been completed. This presentation details an unbroken chain between the identification of the need and realization of an IRM infrastructure and deployed applications.
Mark Ouska has a diverse background with a focus on methodology-driven application development and data management in both private and public sectors. He has extensive modeling experience focused on work product transformation; the science of carrying business requirements forward to implementation rather than interpreting what was discovered in the last phase.
Steve Farrell, a key partner on the data architecture project, is a senior consultant with a very rich data management background who has worked in a variety of industries and public sector environments. Together they have well over 30 years data management experience. Data Standards Implementation - And
You Thought Standards Development Was Hard!
Sara Hisel McCoy
Data Standards Team
U.S. Environmental Protection Agency
Years after developing an ISO/ANSI 11179 metadata registry, the Environmental Data Registry (EDR), to serve as the backbone to the Agency standards setting process, the Environmental Protection Agency is now tackling the challenges of standards implementation. Having successfully established a core set of Agency standards, and with new standards in progress, the Data Standards Team is conducting outreach and education activities to inform program system managers on standards implementation concepts such as stewardship, conformance, and data harmonization. Ongoing challenges include maintaining management commitment, policy development, approval processes, and standards integration. Join us for an informative talk on what we are learning along the way.
The challenge of conformance
assessment
Selling the concept of stewardship and
defining the role
How standards and metadata registries
can support data integration and harmonization
The need for standards integration
Measuring success in standards implementation
Sara Hisel McCoy is currently a member of the Data Standards Team in EPA's Office of Environmental Information (OEI), and has been actively involved with data standards outreach and implementation activities.
How Data Administrators Can Survive the XML Revolution
Charles Dietz
Director, Data Administration
MetLife
The Internet and World Wide Web will
fundamentally change the way companies do business. Fixed relationships between
product manufacturers to their distribution channels and their suppliers will be
replaced by dynamic relationships managed by computer systems. These systems
will conduct business on behalf of the enterprise over the Internet using real
(or near real)-time message based transactions. The focus of Data Administrators
will have to shift from fixed backend data stores to flexible front-end message
based systems. This presentation will explain a strategy for Data Administrators
so they can use their existing data models and metadata to create a model based
XML internal standard and an environment to manage and control multiple XML
vocabularies linked to back-end systems.
The presentation will illustrate:
A new B2B model showing how
horizontally organized industries will create vertical integration through
dynamic message based systems.
How the focus will shift from internal vocabularies to external standard, messaged/transaction based vocabularies
The problem with multiple message
standards (XML transaction standards) and a strategy to solve it
Some generalized infrastructure models
to support and manage XML vocabularies
The attendee will learn:
Why the future will be message
dominated
What is the multiple vocabulary
problem and how to solve it
How to use existing DA assets to
support the XML strategy
How to use XSL/XSLT mappings to link
data to backend systems
XML is an important topic for Data
Administrators because, in the future:
virtually all B2B communication will
be conducted via standards based XML transactions
the primary interface to large data
stores will be XML, either converted to or from database formats or stored as
XML
Traditional data modeling will be
replaced by a hybrid of XML Schema development along with mappings to back-end
system data stores
Charlie Dietz has been involved in Information Technology at MetLife for over 15 years, coming over from the Annuity Customer Service department at MetLife in 1985 to lead the development of one of the first on-line relational database systems at MetLife. Since then, Charlie has promoted data administration principles and practices throughout MetLife, most recently as creator and head of the first centralized Data Analysis and Design group in MetLife. Since 1999, Charlie has been the “XML Evangelist” at MetLife, raising awareness of XML and the need for standards to make XML an effective tool for MetLife.
Meta Data Lies: Data Profiling Is Your Lie Detector
John Howe
President
J.W. Howe, LLC.
The main weakness in traditional
approaches to executing data migration or data integration projects is simple.
They all assume that metadata is accurate. In reality, most metadata is not
accurate. When you have to blow the dust off the books, you know it is out of
date. The majority of traditional methods state that you start with the metadata
as your source of knowledge about the system. Are you willing to bet the success
of a one million dollar project on documentation that has not been updated since
the system was implemented twenty years ago?
This session will teach you the basics of Data Access, Profiling and Mapping, a methodology that results in a complete and accurate understanding of 1) the proper approaches to accessing legacy data, 2) the content and structure of any data source and 3) the rules by which data must cleansed and transformed. Data Access, Profiling and Mapping creates a factual body of knowledge about your data. This knowledge will provide significant reductions in the risks and costs associated with accessing, moving, cleansing and transforming data in any type of project.
John Howe has spent 20 years working in various data management capacities. He has been a Database Analyst and Administrator, Data Modeler, Data Analyst, and Director of Data Management. Mr. Howe has been actively involved with the development and use of Data Profiling and Mapping methods and technologies for over ten years. He began his interest in Data Profiling in 1991 when he worked with the development team that created the core technology for what is now Evoke Software's Axio product line. John subsequently spent the last 7 years in various consulting, training and sales roles with Evoke Software, most recently as Vice President of Customer Services.
Tuesday, April 30, 2002
1:45 PM - 2:45 PM (Concurrent Sessions)
Data Model Management: Keeping the Logical and "Real World" in Synch
Ralph Mohr
Director, Data Warehouse Architect
Covansys
Data has become a critical resource to organizations. The ability to share data across lines of business allows quick responses to ever changing business needs and opportunities. Systems based on a common data architecture require effectively managed data and process models. A well designed model management strategy can provide significant savings in time and resources in the development cycle. These models are valuable assets that should be safeguarded and made available for use across the organization.
A model management strategy provides the
processes and procedures required to ensure the maximum return from an
organization’s data architecture investment. The strategy addresses:
Model types and usage
Change control management
Model standards
Metadata
Roles and responsibilities
Model repositories
The strategy should be developed and
implemented in an iterative process. Each iteration of the strategy provides
greater detail and greater levels of standardization. The presentation reflects
approaches developed from instituting model management strategies at large
retail, financial and governmental institutions.
Attendees will learn:
How effective Data Model Management
Strategies impact the organization's ROI
Closed loop modeling approach to keep
the logical and physical models in synch
Keeping dimensional models in synch with the corporate ans data warehouse models
Ralph Mohr is a consultant with
Covansys. He specializes in data warehousing with an emphasis in data
architecture and data quality. Mohr has been involved in a variety of projects
ranging from small data marts to multi-terabyte data warehouses. Mr. Mohr's data
modeling experience has been in Finance, Insurance, Retail and Welfare.
Currently, Mr. Mohr is serving as the Data Architect for the Victoria's Secret
and has assisted The Limited in developing corporate modeling standards and
model management strategy.
An Hour Per Attribute – What Do You Get for That?
Dawn Michels
Manager Data Architecture
Fair Isaac Inc
One of the most significant challenges in the Data Management discipline today, is making quality estimates on the amount of resources required to do data analysis and design for existing as well as new databases. A well-respected industry standard on this is an hour per attribute. Well, there is one hitch! About 80% of the time, or more, you don’t know the number of attributes until you start to interrogate the data sources carefully. This is as you are beginning to define the logical data model.
For DBA’s, the estimates are clearly focused around the quantity of data to be processed and the complexity of the relationships between the data as defined in the data modeling process. To do an accurate job of estimating first we need to articulate what is to be included as deliverables.
- Data model designs include:
- Entity
Identification – ie. key subject areas
- Attribute definition
- Attribute physical characteristics (ie. char, number, date – and length)
- Grouping of attributes to Entities
- Entity
definition
- Determining Keys & Dependencies
- Row Count estimates
- Source to Target Mapping of attributes
- Placement of attributes into entities
- Identifying & Mapping to necessary reports
- Relationships between the files.
The data architect, alone in a vacuum, cannot accomplish this. It also requires the business acumen, of someone knowledgeable in the specific business vertical the data is supporting. Therefore the notion of database design is collaboration between the Data Architect, the Database Administrator and the Business Analysts and Consultants of the marketing delivery units.
Yet another variable has come into play. If a client has a base structure, but populates it with 32 different source files, can we in good faith charge them an equal number of hours to the attribute, as we would for “scratch” design?
To try to sort this out and allow us to quantify the 60 minutes consumption, I have identified those items that are purely new design separate from mapping into current structures. During our session, I plan to discuss, what I think goes into the 60 minutes per attribute estimate.
Dawn Michels is the team
manager for the DW Data Architecture Team at Fair Isaac, Inc. Arden Hills
office. She has 15 years experience in relational database design, including
DB2, Redbrick, Oracle, NT SQL Server and SAS. Dawn has modeled many databases
and guides her, as well as the refining the Data Architecture Role at Fair
Isaac.
Data Management at the Project Level
Thomas Zaborsky
Data Analyst
CNA Insurance
This presentation will focus upon how to
establish a data management presence within an organization while working at a
project level. It will do so by examining a strategic vision to construct a
common account management system/database for the customers, contracts and
products of a single business unit within a large organization. The value of key
data deliverables introduced over the course of fifteen years on both
unsuccessful and successful projects will be discussed. Among them are a
universal code table, data repository, universal product components and a tool
for quantifying the work of data management. Attendees will learn:
How the value of meta data carries
over from one project to another
How to cope with continual turnover in
business and systems personnel
How to add value via basic data
deliverables
The nature of the Business
Analyst/Data Analyst relationship
The nature of the DBA/Data Analyst
relationship
When comprise is necessary to deliver
a project
How to quantify the work of data management
Thomas Zaborsky works as a Data Analyst within the Group Benefits Strategic Business Unit at CNA Insurance, where has served for fifteen years. His responsibilities include the design and development of the SBU's databases, data models and code management. Tom holds a Bachelor of Arts degree in English Literature from the University of Illinois at Chicago and a certification from the Computer Career Program at DePaul University. Tom is active in the Chicago DAMA Chapter and is currently serving on its board in the position of Secretary.
The Generic BI Meta Data Repository
Michael Jennings
Manager, Enterprise Performance
Management
Hewitt Associates LLC
Many data warehouse projects face the
decision of purchasing or building a meta data repository for their environment.
The decision to build a repository is often made due to the lack of data
integration between the various data warehouse products or as a result of
budgetary constraints on the project. For those projects that make the decision
to implement their own meta data repository solution a generic model is often
the best choice to advance that effort.
This presentation explores the design of
generic meta data repository data model for use in a business intelligence
system project. The design will address the various base components that are
typically required in meta data repository in order to support a data warehouse
environment. The intent of the model is to offer those individuals who wish to
implement a meta data repository a generic solution that can be integrated into
an in-house implementation. Alternatively, this model design can be used to
complement a requirements checklist when evaluating meta data repository
products in the market place.
Key repository components
Documenting the transformation process
Enhanced knowledge base of technical and business meta data
User access considerations for the information consumers
Lessons learned
Michael Jennings is an architect and manager specializing in business intelligence, enterprise performance management, and web based delivery strategies & architectures at Hewitt Associates. He has more than eighteen years of information technology experience in the manufacturing, telecommunications, insurance, and human resources industries. Michael speaks frequently on business intelligence issues at major data warehousing conferences and is an instructor of information technology strategies at the University of Chicago's Graham School. He is a contributing author to the book "Building and Managing the Meta Data Repository" published by John Wiley & Sons.
Incorporating Industry XML Standards into a Corporate Meta Data Strategy
Joanne Garifo
Repository Administrator
Prudential Financial
Prudential has adopted the Acord XML
standard to be used for all XML development. Joanne Garifo will discuss the
reasons for adoption and how her organization is incorporating this standard
into their metadata strategy. This presentation will discuss:
The advantages of adoption
The current strategy for capturing and
reporting on XML metadata
The challenges we face going forward
Joanne will also provide some technical information on the environment and the extensions made to the CA-Platinum Repository that allow them to capture XML and map to legacy systems.
Joanne Garifo has been a Repository Administrator for 5 years at Prudential. Responsible for all technical aspects of the Platinum Repository for MVS including database administration.
Globalized Data for the
Web
James Bean
President and CEO
Relational Logistics Group
With the advent of the web, the
enterprise strategy "du jour" has been focused around e-commerce.
However, the web is "borderless". We tend to forget that effective
exchange of data between partners and customers needs to consider differences
in: Geography, Culture, Regulatory acts, etc. Visitors to our web pages and our
collaborative business partners may not utilize the same content, language, or
context for their data. This presentation will describe the importance of
metadata for consistent data exchange and introduce XML as one possible method
for describing global transactional data content. Participants will be
introduced to 7 common E-Commerce and Globalization mistakes as well as the
basic concepts of globalization and international data standards.
Seven common globalization mistakes
Industry motivation and metrics
supporting the need for global data standards
Introduction to recognized global data
standards
XML as a potential global e-commerce transaction solution
James Bean is the President and CEO of the Relational Logistics Group. He is a respected expert in the fields of Business and Technology, having completed numerous worldwide client engagements for XML Training, XML Industry Standards Development, Global E-Commerce Strategies, Information Architecture, and Database Design. He is the author of the books: the "Sybase Client/Server EXplorer" © 1996 Coriolis Group Books, "XML Globalization and Best Practices" © 2001, and has written numerous magazine articles for technology journals such as: "Enterprise Development Magazine", "XML Magazine", "DevX.com", "Web Builder CD", "PC Techniques Magazine", "Visual Developer Magazine", and the "Database Design Professional Newsletter". Mr. Bean is also a frequently requested speaker for regional, national and international technology conferences.
Tuesday, April 30, 2002
3:15 PM - 4:15 PM (Concurrent Sessions)
How to Estimate Data Modeling Project Efforts
Gary Flye
Manager, AVP
Wachovia Corporation
How long does it take to create logical,
physical and dimensional data models? Your success and credibility as a data
modeler not only depends on the quality of your models but also how well you
estimate the level of effort up front. Setting realistic expectations is
crucial! If you underestimate your time, the project is delayed and costs go up.
The “sticker shock” of overestimating may cast doubts on the value of your
services. This presentation shows how you can create an estimation tool that has
proven its value on dozens of modeling projects at First Union National Bank.
Attendees will learn:
Why it is so hard to estimate time and
cost of data modeling efforts
The dangers of underestimating or
overestimating
How to create their own estimation tool
How to make the estimation tool
increasingly accurate
Not to place blind trust in the tool!
Gary Flye is an IT Leader and Assistant Vice President at First Union National Bank, leading the Data Management function in the Database Management department. His team is responsible for database design and reengineering, data allocation and retention standards, meta data management, data quality, directory services and knowledge management. Mr. Flye holds a B.S. in Metallurgical Engineering and an M.S. in Computer Science and his 20 years of IT experience also include the mining and environmental industries in both the public and private sectors.
Data Quality and the Importance of Meta Data at Centrelink - A Case Study
Peter Davis
Manager, Data Management
Centrelink
Centrelink is one of the largest
organizations in Australia with 22,000 staff, 440 service centres and 23 call
centres. It has over 5.5 million customers, makes more than 230 million payments
and sends over 120 million mail items, annually. The mainframe systems cope with
12 million transactions a day. Data quality and metadata are significant issues
in such an environment.
The presentation would introduce
Centrelink, review the tools and processes we use to monitor and report on data
quality and the important role of metadata. How data management becomes more
complicated by moving to multiple service delivery channels and operating
platforms, as well as new opportunities and new challenges.
Introduction to Centrelink -
customers, business and processing environment
Implementing Data Quality procedures
and metrics, tools and processes used, operational versus warehouse and
Management Information (MI) considerations
The importance of metadata to large operational systems, MI users, and the business, introduction of the data life cycle concept
Cross platform challenges - from OS390 on the mainframe through Unix to an NT workstation somewhere in the network
Working towards a Data Management architecture
Peter Davis is the Manager of Data Management in Centrelink. He has been involved with data quality and metadata issues in Centrelink since its establishment in 1997. Peter was the project manager for Centrelink's Data Quality project. An active member of the Data Management Association (DAMA) since 1996, Peter is currently the President of the ACT chapter. He has presented Centrelink case studies on the importance of metadata, data quality and enterprise data management to DAMA and other groups.
The Grammar of Business Rules
Terry Moriarty
President
Inastrol
New data and object modelers are taught to hunt for all the business’s nouns as they that represent the most likely candidates for entities or object classes. Sentences with the pattern of “Noun – Verb – Noun” probably represent relationships while a generalization hierarchy often lurks behind sentences with an “is a” verb statement. Do other patterns exist in language that can help us in uncovering and structuring an organization’s business rules? This presentation strives to discover the grammar of business rules by drawing on the Zachman Enterprise Systems Architecture Framework and the sentence diagramming technique many of us learned in high school. Ms. Moriarty, president of Inastrol, an information resource management consulting firm, has enjoyed a diverse career in Information Systems, over the last 25 years, from application programmer to business analyst to information strategic planner. She has developed a methodology that integrates business rules analysis with the meta-data management environment to address major business concerns, such as Customer Relationship and Product information management. Her dynamic business models have been used as the basis of customer models for companies within the financial services, telecommunication, software/hardware technology manufacturing and retail consumer product industries.
Techniques for dissecting business
ramblings to form well structures business rules
How the Zachman Framework can be
used as a technique for classifying business terms
How adverbs and adjectives provide
clues in uncovering business rules
Why many nouns really represent important business states and roles
Terry Moriarty was a columnist for Database Programming and Design Magazine for over 7 years. She currently authors the "Metaprise" column in Intelligent Enterprise. She is the co-chairperson for the Business Rules Forum, as well as chairperson for the 1997 Business Rule/Database Design Summit and the 1991 International Conference for the Entity Relationship Approach. She has been active in DAMA since 1986, where she was introduced to the data driven approach to information management and has proudly worn the badge of a data bigot ever since. She is a past president of the San Francisco DAMA chapter.
Advanced BI Methods in Federated Data Warehouse Environment
Vladimir Pantic
Senior Consultant
IBM Canada Ltd.
Deborah Henderson
VP Education & Special Projects
DAMA International
Federated Data Warehouse (FDW)
Environment is used as a framework for implementation of advanced BI methods:
Data Mining, OLAP and Statistical Analysis. The presentation will show how the
FDW, with its conformed dimensions and unified definition of concepts (such as
location, asset, customer etc.) is used to implement OLAP, Stats Analysis and
Data Mining analysis in the following fields:
Supply Management Chain (specifically
price negotiation and optimal budgeting)
Customer Satisfaction (using the
Segmentation and Market Basket Analysis)
The presentation integrates the FDW with BI methods that are using it as a data foundation. The emphasis is put on data integration and data quality as an important element for the success of advanced BI methods and techniques. The attendee will see the big picture that will outline the BI environment including advanced BI tools applied to unified data structures integrated in the FDW.
Vladimir Pantic M.Sc., I.S.P. is Certified Senior Consultant with IBM Canada. He specializes in the domain of Corporate Data Architecture, Logical and Physical Data Modeling. As experienced practitioner, Vladimir is involved in training and education of Data Modelers and Data Architects. In last four years he is actively involved in Data Mining and Advanced Statistical analysis.
Deborah Henderson, B.Sc., M.L.S. is Data Architect for Hydro One. She is experienced in consulting to many different business functions in EIS/DSS, Knowledge Management, Data Warehousing, Enterprise Portal and On-line Analytical Processing design and Project Management, with an extensive background in information management (process modeling, data modeling and data dictionaries) and associated architecture development.
Practical Meta Data Solutions for the Large Data Warehouse
Tom Gransee
Principal
Knightsbridge Solutions LLC
For enterprises with large data warehouses, implementing a comprehensive meta data solution can seem like a formidable task. There are no industry standards, and no off-the-shelf tool suites that can meet all of an enterprise’s meta data objectives. However, by carefully gathering requirements, mapping them to meta data sources, and choosing a solution that achieves the right balance between standardization and customization, an enterprise can develop an approach to meta data that meets its business and technical needs. Enterprises that implement successful meta data solutions will benefit from reduced development costs, user acceptance of the data warehouse, and the ability to make faster business decisions.
The current state of meta data
knowledge, practices, and tools
The emergence of meta data standards
Developing a meta data architecture
by defining requirements and matching them to meta data sources
Alternatives for implementing a meta
data solution
Business and technical risks of not
formalizing meta data
The benefits of a formalized
approach to meta data
The basics of developing a meta data architecture and choosing a solution approach
The tools and standards that are available to facilitate the implementation of a meta data solution
Thomas Gransee is a principal at Knightsbridge Solutions with more than 17 years experience in business systems planning, analysis, design, testing, and implementation of complex state-of-the-art information systems. Mr. Gransee’s experience spans the insurance, healthcare, retail and manufacturing industries. Prior to joining Knightsbridge, Mr. Gransee was a group manager in the merchandise information department at True Value Hardware. Prior to that, he was manager of retail systems at Bridgestone/Firestone Inc. Mr. Gransee has been a speaker at industry and vendor conferences, including Riscon and SCO Forum. Mr. Gransee earned his Bachelor of Arts degree in Liberal Arts from DePaul University.
To Laugh or to Cry? Persistent Prevalent Database Fallacies
Fabian Pascal
Analyst, Editor & Publisher
DATABASE DEBUNKINGS
A lot of what is being said, written, or
done in the database management field -- or whatever is left of it -- by
vendors, the trade press and "experts" is increasingly confused,
irrelevant, misleading, or outright wrong. While this is, to a degree, true of
computing in general, in the database field the problems are so acute that,
claims to the contrary notwithstanding, knowledge, practices and technology are
actually regressing!
This presentation exposes fundamentally flawed ways in which the database industry operates and illustrates some of the prevalent fallacies and their costly practical consequences. It offers an opportunity to test yourself on your ability to see through the former and avoid the latter.
Fabian Pascal has a national and international reputation as an independent technology analyst, consultant, author and lecturer specializing in data management. He was affiliated with Codd & Date and for more than 15 years held various analytical and management positions in the private and public sectors, has taught and lectured at the business and academic levels, and advised vendor and user organizations on database technology, strategy and implementation. Clients include IBM, Census Bureau, CIA, Apple, Borland, Cognos, UCSF, IRS. He is founder and editor of DATABASE DEBUNKINGS (www.dbdebunk.com), a web site dedicated to dispelling prevailing fallacies and misconceptions in the database industry, where C.J. Date is a senior contributor. He has contributed extensively to most trade publications, including Database Programming and Design, DBMS, DataBased Advisor, Byte, Infoworld and Computerworld and is author of the contrarian column Against the Grain.
Wednesday, May 1, 2002
9:50 AM - 10:50 AM (Concurrent Sessions)
Modeling the Data Warehouse Using UML
Davor Gornik
Marketing Engineer
Rational Software
UML data modeling profile gives
database developers the opportunity to use object oriented design methods for
the design of a data warehouse. Davor will explain the Unified Modeling
Language in context of database modeling.
The session will introduce the design of
a star schema and snowflake using object oriented design and UML. Different
diagrams and the semantics of UML will be introduced using a design example for
a data warehouse. Themes of the session include:
Defining the scope using an object model
Dimensions and facts
Star schema and snowflake object model and implementation
Davor Gornik: After the study of computer science in Munich, Davor worked on software projects for database applications in retail and finance area for different companies as developer, consultant, and project manager. He joined Rational in 1997 and worked as a technical representative. He joined the Rose Business Unit as a marketing engineer for the Data Modeling product.
The Politics of Data Analysis: Working Within the Constraints of Corporate Data
Amanda McLoone
Business Process Engineering Manager
Intel Corporation
Information Quality is the latest
buzzword of the 21st century - and rightly so. The consequences of poor
information can be severe enough to impact more than just business operations.
An extreme example is the recent merger of two major banking institutions.
During the merging of the consumer information, funds in one customer account
were electronically lost causing severe personal trauma. Many corporations are recognizing the negative impact of poor information
quality and are investing in improvement. This should create jubilation since
historically, data analysis, has been perceived as low value, especially on
time-constrained projects. Excitement wears off quickly, though, as it is
apparent that in large corporations, poor information quality has roots so deep,
that in spite of best intentions, most barriers remain in tact. Ironically, even
corporate solutions intended to improve Information Quality, such as the
Enterprise Data Warehouse or Enterprise Applications also serve to broaden the
spectrum between good data management and reality. Regardless of the root cause
of poor data management practices, the need to appropriately apply theory and
practicality is critical to successful data analysis.
This presentation intends to assist data
analysts who are required to work within the corporate bounds of poor data
management practices. Using a case study from a Fortune 500 manufacturing
company, common constraints encountered in corporate environments are identified
and best known methods that mitigate the impact and propagation of these
practices are examined. The presentation is not intended to advocate eliminating
the use of Information Quality theory, but strives to create recognition of the
conflict between theoretical practices and practical application in large
corporate environments.
Common
Corporate Constraints Addressed:
The Corporate Data Foundation
(Product, Customer, Order) -- Constraint: Fixed Structure Legacy Data
The Enterprise Data Warehouse -- Constraint: Invisible Data Transformation
The Enterprise Application --
Constraint: Proprietary Data and Data Structures
The Programmer -- Constraint:
Unstructured Data
The Organizational Silo --
Constraint: Unintegratable Data
Attendees
will learn:
To recognize the situations that require practical data analysis application in lieu of theory
Strategies for dealing with commonly
encountered corporate constraints
To recognize the risks of large, centralized information quality improvement initiatives
Amanda McLoone has over 13 years experience in the Information Systems industry with an emphasis on Data and Business process analysis. She has been employed at Intel Corporation for the last 9 years in a broad range of organizations covering IT, Logistics, Factory Automation, Corporate Quality and Supplier E-Business. She currently manages the Corporate Quality Business Process Engineering and Data Analysis groups. Amanda’s career accomplishments include the original implementation and proliferation of Intel’s corporate shared data environment. She is responsible for achieving significant cost savings through the automation of a major business process. This cradle-to-grave inception of automating Intel’s Capital Equipment Forecasting process and its delivery as Intel’s first business-to-business application was a major breakthrough for Intel’s eBusiness initiatives. Her most recent accomplishment is the adoption of Business Process Quality as a core function within the Corporate Quality Network.
Building a Bridge Over Disparate Waters
Sandra Hostetter
Manager, Content Management Group
Rohm and Haas Company
The corporate world is drowning in
disparate data. Data elements, a.k.a. field names, column names, row names,
labels, metatags, etc. seem to reproduce at whim. Librarians have been battling
data disparity for over a century with tools like controlled vocabularies and
classification schemes. Data Administrators have been waging their own war using
data dictionaries and standards. Both camps have had limited success with their
strategies. Why? (1) These tools are not a common data architecture and in some
ways actually contribute to the problem. (2) Librarians and Data Administrators
are not working together to find a total solution.
Why controlled vocabularies,
classification schemes, data dictionaries, and standards cannot solve the
data disparity problem alone.
How we are cross-walking to nowhere.
The need for the unstructured data
world and the structured data world to blend.
Case Study: A joint effort, by a librarian and a data administrator, to build a common data architecture for use in a real-life document management system.
Sandy Hostetter, a professional librarian, is currently employed by the Rohm and Haas Company as manager of the Content Management Group within the company’s Knowledge Center. The Content Management Group encompasses the areas of records management, document management, and metadata management. Sandy has spent most of her career in library-related positions at Rohm and Haas, but a few years ago she went over to the “dark side,” and labored for almost 2 years as the metadata architect for a large data warehouse project. During this period she was fortunate to “discover” the writings of Mike Brackett, and since then has been actively collaborating with him on a creating a common data architecture for Rohm and Haas.
Meta Data Management in a Packaged
Environment
Van Scott
Principal Consultant
Sonata Consulting, Inc.
Today’s packaged software includes rich meta data repositories, which are used for the configuration and operation of the software. The package meta data is useful beyond the primary system, especially for those systems that share data. However, the package meta data frameworks often provide levels of abstraction that obscure the underlying semantics of the system and its data. Some shared data will likely be implemented in incompatible ways in the different systems. This presentation relates the experience of a real-word project that integrated the meta data repositories of several packaged software products, including CRM, Billing, ETL, and EAI toolsets.
Sample content and structure of packaged software meta data repositories
Levels of abstraction: business
objects, components, and base tables
Exposed APIs and the importance of
API meta data
Mediating between different
implementations of similar structures
Meta models: CIMs, CWM, and others
Some strategies for managing and
integrating packaged meta data
With the rise in packaged software and decline of custom development, meta data has been moving from custom-developed models to vendor-developed models. As always, it’s important that system models be managed appropriately. In a way this is no different from the meta data management of custom development. However, the packaged repositories provide some new challenges, which this presentation addresses.
Van Scott is a results-oriented data architect with a very strong methodological bent. He is intrigued by the enterprise, enterprise architectures, and data warehousing. Very project-focused. Published author. Speaks at business intelligence seminars, including the DAMA 2001 conference.
Deriving Value from BLM's Information Assets
Theresa Fresquez
Computer Specialist
Bureau of Land Management
Brian Campbell
System Engineer
TRW
The Corporate Metadata Repository (CMR),
is an Oracle-based, commercial, off-the-shelf (COTS) software package that
stores metadata about the Bureau of Land Managements (BLM) applications. By
creating a central, shared source of metadata, with the consistent data
definitions, CMR reduces application development and maintenance costs. The CMR
is BLM's data management tool used by data administrators, database
administrators, developers and other application users. It is the BLM's
reference for standard data elements and metadata.
BLM's repository focus areas:
- Enterprise Applications
- National Applications in the CMR
- System Profiles/Details information
- Logical and Physical metadata stored
in the CMR
- BLM is developing Common Data Elements
using Impact Analysis
- CMR centrally stores all BLM's data
standards
- Data Quality (Edits building Business
Rules, building Data Quality as in
what we can put in and what we can't,
clean-up, monitoring of data input)
How users access BLM metadata through
the Intranet
- Accessing metadata through the Data
Shopper's Applications
- Data Shopper Search
- Reports
How developers enter BLM metadata into
the Corporate Metadata Repository
- Manual metadata entry through the
Platinum Repository tool
- Automatic metadata entry using flat
files, ODBC, and Erwin into the Repository
System Architecture
- BLM Metadata Repository Data Shopper
- Brio Reporting Tool
- Oracle RDBMS
- Microsoft NT servers and clients
Theresa Fresquez has worked for
the U.S. Department of the Interior's Bureau of Land Management (BLM) for the
past 10 years. Throughout her years at BLM, Theresa has worked primarily on
database development projects and has developed several wildlife-related
national applications. Most recently, she has been involved with developing and
populating BLM's Corporate Metadata Repository. Theresa has a B.S. degree in
Computer Science from Colorado Christian University. She has received several
awards and recognition for her achievements at BLM. Theresa is a member of the
DAMA and Platinum Repository User Group.
Brian Timothy Campbell
Data Classification, Context and Meaning
Part
1:How to Organize Data and Content Across Multiple Applications and Databases
Lynn Wojcik
Director of Content Classification
Northern Light Technology, LLC
Meta data is an integral component in
organizing content seamlessly across multiple databases and applications. With
the proliferation of taxonomies, thesauri, keywords, and other organizing
schema, how can you best navigate through, evaluate, and utilize the meta data
that is most useful to you? This session will address the steps needed to
leverage legacy meta data and also create new meta data when none is available
for classification of data within a single, optimized system. Some of these
steps include:
Deciding upon a “backbone”
organizational scheme
Normalizing all meta data with the
system
Leveraging custom pre-built taxonomies
Strategies to avoid hand tagging of
documents
Lynn Wojcik is the Director of Content Classification and has worked at Northern Light Technology since 1997. She has been the Chief taxonomist at Northern Light since 1999. Before coming to Northern Light, Lynn held several positions at the Office of Smithsonian Institution Archives and the National Digital Library Project at the Library of Congress. She has a BA from Smith College and a MLS from The Catholic University of America.
Part 2: Resolving Context and Meaning in Computer-Based Communications
Chito Jovellanos
President and CEO
forward look, inc.
Significant effort is spent by enterprises to reconcile the messages and transactions exchanged between computer-based systems. The key issue rests with contextual gaps that arise when different systems (eg. front office vs. back office) transmit and receive data about the same concept using their unique vocabularies and implied meanings. Context gaps represent a significant (and hidden) recurring cost in enterprise application integration (EAI) and business-to-business (B2B) commerce. This presentation discusses existing and emerging solutions to the data context problem using case studies from the financial services and environmental science domains.
The speaker will describe real-world
deployment problems and their resolution; the successes and the failures; and
the “soft spots” to monitor in related implementations. The presentation
concludes with a practical perspective on emerging initiatives that address the
context gap problem (eg., “Semantic Web”, RDF, DAML, Agent-Based Information
Brokers, and data standardization efforts).
This presentation will engage attendees with current views of the “state of the art” in data management. More importantly, it will describe in plain English the significance and potential impact of various technologies and data standardization initiatives.
Chito Jovellanos is the President & CEO of forward look, inc., a Boston-based company that helps its clients secure recurring new revenues from their enterprise data assets. Prior to forward look, he served as the Chief Information Officer of Internet Securities, Inc (a Euromoney company). Chito was also Director of Research & Development at the Electronic Settlements Group (ESG) at Thomson Financial Services; Vice-President of Business Planning at Scotiabank; and Director of Product Development in the Transaction Products Group at Reuters plc. He is a professional member of the Association for Computing Machinery (ACM), the Data Management Association (DAMA), and the International Association of Financial Engineers (IAFE).
Wednesday, May 1, 2002
11:05 AM - 12:05 PM (Concurrent
Sessions)
Enterprise Data Integration: Development of an Enterprise Data Model
Noreen Kendle
Enterprise Architect
Delta Technology - Delta Air Lines
This presentation is focused on the
"How" to develop an Enterprise Data Model. It describes the approach
developed and used at Delta Air Lines for the creation of an Enterprise Data
Model. The Delta Air Lines Enterprise Data Model is now being used to create the
Operational or Enterprise Data Stores, integrating operational data across the
airline business. It describes a 7 step practical methodology for developing an
Enterprise Data Model that incorporates a "top Down" and "Bottom
up" approach. It incorporates
an enterprise view needed for integration to support an ODS and/or DW, as well
as the current state (work already accomplished – existing models) for
practicality and quicker development. The presentation focuses on How to build
the enterprise data model using this methodology.
Definition of what is an Enterprise
Data Model
Explanation of the methodology used,
an approach of top down and bottom up
A description of HOW to create an
Enterprise Subject Area Model with real world examples
A description of the development of
the Enterprise Conceptual Models with real world examples
A description of data rationalization
in the bottom up /top down integration resulting in the Enterprise Data Model
An explanation of the supportive
documentation and continuation of the iterative process
This is not an academic or theoretical presentation. It is taken from a real corporate successful experience of actually producing an Enterprise Data model. The model is now over 700 integrated entities and encompasses 5 of the major business subject areas. The model is being used to build the Operational Enterprise Data Stores and will eventually be used for the Enterprise Data Warehouse.
Noreen Kendle - I
have
been with Delta Technology (the IT of Delta Air Lines) for over 6 years, presently
as an Enterprise Architect. When
I developed the Enterprise Data Modeling methodology I was the Manager of the
Enterprise Modeling group which composed of 24 modelers. We have been working on
the Enterprise Data Model for nearly 3 years. We have developed extensive
modeling, data, naming, XML, review and integration standards. Prior to managing
the enterprise modeling group I worked as a data architect across the airline on
a variety of projects. I have been involved in the development of the ATA
airline model. I have worked in and around Data for
much of my over 20 year career. Prior to joining Delta I worked for AT&T as
an Oracle DBA, Unix Admin, Data Modeler and application developer. Prior to
AT&T I worked at Masco Corporation, EDS - World Computer, AT&T
Corporate/Chrysler, and Ford.
Implementing Information Stewardship: Data Definition and Beyond
C. Lwanga Yonke
Manager, Data Architecture &
Information Quality
Aera Energy LLC
When properly designed and implemented,
an Information Stewardship program can successfully create the right
accountabilities for Information Quality. This presentation describes Aera
Energy’s approach to building and nurturing an information stewardship
culture. A deliberate effort was made to move beyond data definition to include
stewardship accountabilities throughout the information value chain (create,
enter, update, apply, delete). Topics include:
Managing information as a product
A definition of the seven Information
Stewardship roles used at Aera
Stewardship as a tool for integrating
data, people, process and technology
The enabling role on an Information
Quality Policy
Specific ways to implement Information
Stewardship
Successes, pitfalls, trade-offs
C. Lwanga Yonke works as Manager of Data Architecture and Information Quality for Aera Energy LLC. He is actively involved in the implementation of an Enterprise Architecture Plan and of a dataware methodology for data warehousing and system development. Lwanga currently specializes in all aspects of information quality. In previous assignments, he led multiple development and operations projects in petroleum engineering. Lwanga earned an MBA Beta Gamma Sigma from California State University, and holds a bachelor of science in petroleum engineering from the University of California at Berkeley. An ASQ Certified Quality Engineer, he has conducted numerous workshops and seminars on TQM strategies, and has authored and presented several technical and IRM papers.
The Data Analyst's Role in Object Analysis and Object Design
Jim Goetsch
Data Architect
Schneider Logistics / IT
Discussion focuses the value of the Data
Analyst within OAOD; Issues with the Object/Relational approach (specifically
using UML-Class models to represent data); What the industry is doing from a
tool perspective; Data Analyst role in Object Oriented Analysis, Design, and
Testing as well as the benefits of data modeling throughout this process.
Attendees should walk away with a clear
understanding that with the OAOD approach, the Data Analyst helps:
Define the Classes, Attributes, and
Associations
Avoids Redundant Data
Avoids masking the business
intelligence with surrogates
Provides definition consistency across
the Analysis & Design efforts
Designs the database
Jim Goetsch is the Data Architect at Schneider Logictics, Inc. and an Adjunct Professor at St. Norbert's College in Green Bay, Wisconsin. Jim has been working in a variety of roles within Software Development using relational databases since the mid-80's. He has a B.S. in Computer Science and Engineering from the Milwaukee School of Engineering and a Masters in Business Administration from Cardinal Stritch College.
Meta Data Success = Service Based
Organization
Todd Stephens
Director of the Metadata Services Group
BellSouth
The Metadata Services Group within
BellSouth has spent the last 2 years developing Metadata based products.
However, the successful collection of metadata is only half the battle.
Organizations that develop metadata solutions must begin to transform themselves
into a services based organization. Failure to focus on services will result in
another failed metadata project. This presentation will review the basic steps
of transforming the metadata group into a Metadata Services Group.
How can you tell when you should start
the transformation
Metadata Lifecycle
Who are your customers and your
competition
What Metrics should you be measured by
What systems should you have in place
to ensure quality
How should your group market it’s
services and why
Why should your organization engage
the metadata group
Attendees will Learn the following
When should they change their focus
from product centric to service centric
What a product focus should come first
Why the future of metadata depends on this transformation
R. Todd Stephens is the Director of the Metadata Services for BellSouth in Atlanta, GA. Todd has been with BellSouth for about 4 years. His primary responsible is setting the corporate strategy and architecture for the development and implementation of Metadata Repositories, which include metadata, data transformation, component, XML, content, documentation, metrics, interfaces, and the Enterprise Information Portal using the XML technologies. Todd has developed frameworks that have earned him two patent-pending applications within the past 2 years. Todd is enrolled at Nova Southeastern University pursuing his Ph.D. in Information Systems. Todd’s area of research interest include Metadata Reuse.
PANEL: Data Management's Next Big Thing
Brett Champlin, Allstate Insurance
Karen Lopez, InfoAdvisors
Robert Seiner, TDAN.com and CIBER, Inc.
Graeme Simsion, Melbourne University
This lively and entertaining panel session will tackle all of the latest issues and technologies, as we attempt to sort between the stuff that you should be paying serious attention to, and buzzwords you can avoid wasting time on. As the conference draws nearer we will define the topics more specifically (to make sure we cover the really "hot" topics), so send us your ideas, and check on the conference web site for session updates. Just to get the ball rolling, here's a few initial issues:
- Wireless data
- Real-time data warehouse
- Zero-latency organizations
- Web services
- Privacy
- Data management outsourcing
- Message brokers
Preparing for CRM: What Data Managers Should Know
Jill Dyche
Vice President and Partner
Baseline Consulting Group
According to Information Week, 89 percent of companies are taking on Customer Relationship Management projects. All of these projects involve data management, but few of them plan for it. Many of the pervasive press reports heralding the spectacular failure rates of corporate CRM programs have as much to do with failures of implementation as they do with failures of strategy. In this presentation, author and consultant Jill Dyche will review what data administrators, DBAs, project managers, and business analysts need to know about preparing for and implementing a CRM project--the first time out. Her talk will include several real-life case studies from companies who've succeeded and failed at CRM.
Jill Dyche is Vice President of Management Consulting for Baseline Consulting Group, a firm specializing in the design and implementation of customer databases for businesses from start-up companies to the Fortune 50. She is the author of e-Data: Turning Data Into Information With Data Warehousing, which has been published in four languages. Ms. Dyche consults to both Baseline clients and to the vendor community on planning for customer-focused technologies. Ms. Dyche’s writings have been featured in Intelligent Enterprise, CIO Magazine, Information Week, Computerworld, and The Chicago Tribune, among others, and has lectured globally on the topic of managing data as a corporate asset. Her new book, The CRM Handbook, clears the haze around the different types of CRM initiatives and how companies should plan, design, and deploy them, and is a business best-seller.
Wednesday, May 1, 2002
1:15 PM - 2:15 PM (Concurrent Sessions)
Data Model Quality: What Is It?
David Hay
President
Essential Strategies, Inc.
After twenty-five years in development,
data models (and their cousins, Object Models) appear to have come into their
own in our industry. The problem is that there are many different approaches and
many different attitudes toward data modeling. It is becoming clear, however,
that some characteristics of data models are better than others. This paper is
one man's attempt to articulate just what those characteristics might be.
The first premise of this presentation
is that the quality of a data model is directly proportional to its ability to
communicate concepts to non-data modelers. The data model is a communication
tool to establish that an analyst's understanding of the nature of an enterprise
is in fact correct. If it cannot do that, it is not worth the effort. Data
models can be evaluated in terms of their graphics and the way they are
presented. This paper will discuss both, including issues of the notation to
use, care in creating models, and the way they should be organized.
This presentation describes the characteristics that should be part of any data model, if it is to be successful in supporting a requirements analysis effort. It addresses the question of how to make a data model readable to someone who normally doesn't read data models. (And yes, it is full of biases and prejudices - but they are held by someone who has been a very successful data modeler for over fifteen years.)
A veteran of the Information Industry
since the days of punched cards, paper tape, and teletype machines, Dave Hay has
been producing data models to support strategic information planning and
requirements planning for over thirteen years. He has worked in a variety of
industries, including, among others, power generation, clinical pharmaceutical
research, oil refining, forestry, and broadcast. He is President of Essential Strategies,
Inc., a consulting firm dedicated to helping clients define corporate
information architecture, identify requirements, and plan strategies for the
implementation of new systems.
What’s So Spatial About Spatial Data? Integrating Geospatial Data into the Enterprise Data Resource
Michael D. Walls
Software Engineering Manager
PlanGraphics, Inc.
Geographic Information Systems (GIS)
technology evolved separately from other information management technologies.
This was fine when GIS concentrated on computer cartography and left management
of non-graphic attributes to mainstream DBMS technologies. Now, however, improved
GIS and RDBMS data handling technologies and increasingly urgent business needs
are forcing a convergence in these two aspects of data management -- to the
consternation both of GIS staff who don’t understand the complexities of
general data administration and of IT data administrators who don’t understand
geographical data.
The fundamental challenge is that
geospatial data within a GIS adds whole new layers of complexity in addition to
those data administrators are accustomed to dealing with when incorporating more
traditional data types within the DBMS. Even the inclusion of imaged documents
or raster photography could be accommodated relatively painlessly, once we had
data types like BLOBs to handle their unique storage needs and raster viewing
tools available for their display. In contrast, GIS features have geometry and
explicit locational coordinates expressed in specialized and quite technical
units of measure. They often have topological characteristics and relationships
that further extend the bounds of data management.
Bringing the power of the “intelligent
map” that is GIS into our business operations is clearly of great benefit to
our organizations. Fortunately, despite the “spatial ness” of this data, it
can readily be accommodated in our data management activities once the few basic
concepts presented during this presentation are grasped.
Attendees will learn:
What GIS is
How GIS technologies integrate with
other data management technologies
Types of geospatial data and their
unique characteristics
Changes in data modeling techniques
required to integrate geospatial data.
Metadata requirements for documenting geospatial data
Mike Walls is Software Engineering
Manager for PlanGraphics, Inc., a world leading consulting firm specializing in
GIS and its integration into enterprise information technology and management.
He specializes in project management and data architecture issues, but still
works on complex data modeling and database design challenges as needed. Prior
to joining PlanGraphics, he worked for over 20 years in local government as a
policy analyst, city planner, applications programmer and systems administrator.
Data Warehouse Architectures in an eCommerce Age
Thomas Haughey
Chief Technology Officer
Pepsi Bottling Group
There are many different approaches or
architectures for developing data warehouses, such as centralized, functional,
federated and virtual data warehouses. For data marts, there are imbedded,
dependent and independent data marts. Each one has its pros and cons, and each
its special considerations. But they are not all equal. Some can deliver
short-term value but over time will increase total cost of ownership. Others
will flatly leave you dead-ended. Some will create more work than they are worth
over the long haul. Others are difficult to do, even though it may be the right
thing for a given customer. It is important to balance short-term gains with
long-term benefits. The choice of correct architecture depends on such factors
as: goals of the business, maturity of the organization, data and queries,
centralization of the organization, and commitment of the business sponsor. This
choice is complicated by a lot of bad or self-serving advice in current data
warehouse literature. The age of eCommerce empowers it more easily to deliver
value to the business. This presentation will present case examples of
successful and unsuccessful warehouses. The most powerful current trend will
also be discussed. The answer may surprise you.
The different data warehouse and data
mart architectures
The pros and cons of each architecture
How to choose the right architecture
The consequences of choosing the wrong
architecture
How to enable your data warehouse in
an eCommerce age
What other companies are doing with data warehousing in an eCommerce age
Thomas Haughey is one of four originators of Information Engineering in America. He is currently CTO for Pepsi Bottling Group after being Pepsico’s Director of Enterprise Data Warehousing. He was formerly President of InfoModel, Inc., a consultancy in Data Warehousing. His courses have been delivered to companies around the world. He has worked on the development of seven different CASE and wrote his own in 1984. He formerly worked for IBM for 17 years. He is the author of many articles on DW and IE. He was VP of Technology for Silverrun Technologies. He is working on a book, "Designing the Data Warehouse - The Real Deal". Tom earned a BA in English.
Meta Data Integration Tools
Attila Finta
Director
A.M. Consulting, Inc.
Marcia Rhode
Director
A.M. Consulting, Inc.
This presentation examines the major commercially available products for integrating and managing meta data from heterogeneous sources. Major features and capabilities of each tool are reviewed and compared, with their relative strengths and weaknesses.
Attila Finta and Marcia Rhode are the founders and principal consultants of A.M. Consulting, a business and IT consultancy based in Austin, Texas, specializing in data warehousing and business intelligence, systems planning, and meta data management, with experience in manufacturing, retail, airlines, utilities, telecommunications, finance, insurance, petroleum, pharmaceuticals, and other industries. Mr. Finta and Ms. Rhode have been active in the data management community for many years, are past board members of DAMA International, and are co-founders of the Heart of Texas DAMA Chapter.
A Case Study on Using XML to Collect
Data from Multiple Sources and Render Multi-Media Reports
Jim Grosso
Senior Project Manager
Kanbay, Incorporated
This presentation will describe an internal Information Technology project to create multiple financial and status reports from various, diverse data sources. The data needed for the reports resides in various depositories, including Oracle, proprietary and text databases. The desired output formats include word processing documents, spreadsheets and web pages. Both internal reports, and edited versions of the various reports for external publication are required, so the issues of confidentiality and proprietary information need to be considered and resolved. Weekly periodic reports with multiple sorts and filters are required, as well as monthly and year-to-date summaries and roll-ups.
The attendees will see how XML is truly platform and database independent, and can be used to transform data from virtually any format into any other format, including web pages and forms. Major points to be covered in the presentation include:
Analyzing Report Requirements
Analyzing Available Data
Creating a Data Dictionary
Options for Triggering the Reports
Creating an XML DTD
Designing Report Formats
Creating an XSLT processor
Web-Based Reporting – HTML, JavaScript
Jim Grosso serves as a Senior Project Manager specializing in Electronic Commerce at Kanbay, Incorporated, a global information technology consulting firm. He has more than 25 years of diversified experience in information technology and manufacturing engineering, with over 20 years in Electronic Data Interchange and Electronic Commerce, and has received certification from IBM in “XML and Related Technologies”. Mr. Grosso has given presentations on EC, EDI, Automatic Identification and other technologies at many conferences and seminars, and has written articles for various publications including ActionLINE, the EDI Forum, Logistics Information Management and Fabricator Magazine. Jim is a two-time winner of the Outstanding Achievement Award from the Automotive Industry Action Group, and has received professional certification from the Project Management Institute.
Object Storage: Past, Present, and Future
Doug Barry
Principal
Barry & Associates, Inc.
Whether or not object storage is new to
you, it's been around for quite a while. Object storage is now becoming
increasingly important as people are looking at Java application servers and
other ways for taking advantage of the Internet. Looking at it beginnings,
current state, and what the future holds will provide a broader view of object
storage and what it can do for you. Join Doug Barry as he mines his more than 14
years of work in object storage to provide a provocative look at where the
industry has been and where it is going.
What can we learn from object storage
as it was first envisioned?
What is the state of the industry now?
What distinguishes object storage when
using object DBMS, relational DBMS, and object-relational mapping products?
What will happen with object storage
in the future?
What standards will be important?
What will characterize the major players in object storage?
Doug Barry has worked in database technology for over twenty years, with an exclusive focus on the application of database technology for objects since 1987. As principal of Barry & Associates, Doug has focused on helping clients make fully informed decisions about the application of object technology. He emphasizes the need to match product feature strengths to application needs in order to ultimately field a successful product. Doug is also the author of the Object Storage Fact Book for Object DBMS and Object-Relational Mapping products, published by Barry & Associates, Inc.; the Object Database Handbook: How to Select, Implement, and Use Object-Oriented Databases, published by John Wiley & Sons; the XML Data Servers: An Infrastructure for Effectively Using XML in Electronic Commerce, published by Barry & Associates, Inc.; and was for many years the Databases columnist in Object Magazine and the ODBMS columnist in Distributed Computing Magazine. His articles have also appeared in Database Programming & Design, Intelligent Enterprise, IEEE Computer, Software Development, Component Strategies, and Data Management Review. In addition, Doug serves as the Chair of the Object Data Management Group (ODMG), a consortium of vendors and interested parties working on object storage standards.
Wednesday, May 1, 2002
2:30 PM - 3:30 PM (Concurrent Sessions)
PANEL: Comparis