This presentation recounts work done at General
Motors in the area of data pattern identification and use. GM has developed
an extensive catalog of data patterns to facilitate work effort in integrating
data across the GM enterprise. The patterns help drive semantic reasoning
and determine information appropriateness for integration. In addition,
the data patterns are also used to derive work effort and costing associated
with information integration initiatives.
- The IT integration imperative
- Fact, fiction, and reality
- Semantic disintegrity propagation
- Data pattern examples
Have you read or seen much on the next evolution of
the web called Web 2.0? Web 2.0 is a collection of technologies and
frameworks that enable collaboration from a social perspective. We can
see this transformation from Web 1.0 to the more collaborative Web 2.0
all around us. Products like Microsoft’s SharePoint, IBM’s WorkSpace,
and many others are transforming the corporate landscape for knowledge
and information collections. Outside the corporation, the success of
Wikipedia, Folksonomies, RSS, and weblogs are undeniably changing every
aspect of our lives. The Internet and associated technologies are under
constant evolution. Within the world of metadata, we have seen three
such transformations. After studying the Web 2.0 environment, I believe
the next transformation is clear.
Attendees will learn the following:
- An overview of Web 2.0 technologies
- Review one organizations implementation of collaboration technologies
- Review the next iteration of metadata value for the enterprise
About This Tutorial
Almost every large government agency or Global 2000 company is struggling
to properly manage their enterprise's data and its architecture. This difficulty
is the direct result of the highly distributed, disjoined and overly expensive
IT environments which currently exist throughout our industry. This situation
has triggered the reemergence of corporations looking to establish truly
proactive Enterprise Data Architecture organizations.
This course will look to move enterprise data architecture theory into a
practical set of steps (roadmap) to achieving true value from your enterprise
data architecture initiative. Moreover, it will present the specific meta
data inputs and outputs that are required for each of the most common enterprise
data architecture focus areas. In addition, data governance and stewardship
approaches and structures will be presented for each of these areas.
What You Will Learn
- Enterprise Data Architecture Defined
- Enterprise Data Architecture ROI
- Foundational Components of Enterprise Data Architecture
- Meta Data Management
- Data Governance and Stewardship
- Focus Areas of Enterprise Data Architecture
- Enterprise Data Model
- Common Objectives
- Value to the Organization
- Roadmap for Implementation
- Meta Data Management Inputs/Outputs
- Data Governance & Stewardship Structure
- Master Data Management
- Common Objectives
- Value to the Organization
- Roadmap for Implementation
- Meta Data Management Inputs/Outputs
- Data Governance & Stewardship Structure
- Data Quality
- Common Objectives
- Value to the Organization
- Roadmap for Implementation
- Meta Data Management Inputs/Outputs
- Data Governance & Stewardship Structure
- IT Portfolio Management
- Common Objectives
- Value to the Organization
- Roadmap for Implementation
- Meta Data Management Inputs/Outputs
- Data Governance & Stewardship Structure
- Enterprise Data Warehousing
- Common Objectives
- Value to the Organization
- Roadmap for Implementation
- Meta Data Management Inputs/Outputs
- Data Governance & Stewardship Structure
- Enterprise Data Architecture Best Practices
- Enterprise Data Architecture Real-World Case Studies
Much has been said about the ISO 11179 Standard.
It is deceptively easy to conceive, but difficult to implement. Sophisticated
data modeling is needed to fully implement the standard. Supporting the
standard must be sophisticated software that implements industrial-class
database processing techniques. Ambiguity is inherent in ISO 11179 that
must be carefully avoided through software.
Just implementing the ISO 11179 standard is not enough. It must be supplemented
with semantic hierarchies and word/phrase lists so that data item naming,
definitions, and abbreviations are automatic. Finally, the ISO 11179 standard
must manage value sets, and the sophisticated mapping among value sets so
that diverse sources of legacy and ERP data can be brought together in data
warehouses and operational data stores.
Successfully designed, implemented and deployed ISO 11179 environment leads
to increased semantic harmonization and integration, and provides great
assists in impact analysis and change management.
Is metadata management the heart of your development
lifecycle or is it just a hairpiece? In order to make meta data initiatives
relevant you need to integrate metadata management into the development
lifecycle and avoid projects that leave you with a glorified glossary or
a second hand metadata junkyard.
Learn about a metadata management initiative that integrates metadata from
analysis through implementation in a continuous lifecycle.
This encompasses
- Screen Design
- Service Oriented Architecture
- ETL
- XML Schema
- Data Dictionary
- Compliance Management
- Database Design
Creating a multi environment repository which is the focal point for the
Development effort. This presentation will outline the approach and discuss
implementation details along with the successes and lessons learned from
this project.
How does a federal executive’s field visits arrive
at a revelation, lead to a Presidential Executive Order, and to a decade
old federal program that spans the country and influences the World? The
journey had ups and downs and encountered curves and rocky roads. Obstructionists
and “nay-sayers” were plentiful. How does a small program overcome the inertia
to covet, protect, and internalize data. This presentation shares the progression
of the program from duckling to fledgling stage and focuses on the program’s
activities that result in successes in the federal, state, local, academic,
and Tribal sectors.
- The why of and what is the Executive Order?
- “Corporate” metadata support
- “Don’t duck Metadata” - the program
- Stumbling blocks
- Program successes
- Performance strategies
The data management practitioners have recognized
the use of metadata for a while now, but serious efforts to develop applications
show casing its real value to businesses are still not readily found. There
are practical problems in the Data Architect's tool kit to present the cost-benefits
to his business partner for active investment decisioning. Often, its reasons
are generally deemed elitist and its benefits are justifiably pale in the
face of stiffer competition from projects in the CRM, Risk, Fraud or CDI
areas.
However, some success can be achieved in carefully orchestrating meta data
based application designs embedding its virtues; some examples of which
may include-
- "Know your data" expeditions that validate the effectiveness of the
data and the knowledge used, in say Marketing Campaign planning or Risk
underwriting processes
- Articulating the purpose and methodology to employ the Meta Data 'on'
business rules and transformations in profiling of converted data from
legacy warehouses and new acquisitions.
- ' Till such time the rigor of meta data based application development
becomes significantly easy, competition for business funding must be
met by creative means- there is no substitute for hard work! This presentation
will share some successful approaches to win partners and investment
dollars.
EXTREME METADATA MAKEOVER WORKSHOP APPLYING TV'S
REALITY GAME SHOW'S APPROACH TO METADATA MANAGEMENT'S REALITIES The challenges
that face Data Resource Professionals parallel those seen on today's popular
TV reality show, Extreme Makeover: Home Edition. Each week a deserving family
is chosen based upon their particularly challenging circumstances to have
their home completely made over by the show's "Design Team" with only seven
days to complete the entire project. The nature, conditions, players, environment
and potential outcomes vary, but the team incorporates an innate ability
to rapidly customize a strategy and plan to take a previously unacceptable
habitat and create a home exceeds the owner's expectations. The "Reality
Show" situations are similar to our "Real World" myriad of metadata challenges:
Objectives vary from establishing a metadata environment where none previously
existed through to those with an intermediate level of metadata maturity,
and beyond to those more unique (and rare) advanced organizations which
want to even further escalate their metadata environment and processes.
Compounding the challenges are situations ranging from struggling grassroot
efforts through funded initiatives. In every case, just as the TV show's
Design Team adopts and delivers, the data resource management professional
must also have the same "toolkit" and innovative creativity to solutionize
and deliver a measurable, improved outcome. In this pragmatic and entertaining
workshop, attendees will learn how to develop techniques which deliver value
under conditions ranging from the establishing a simple metadata inventory
through the more advanced topics of taxonomies/ontology development, information
integration and beyond. Attendees will become active participants in a workshop
which traces the history of TV shows from the 1950's "Truth or Consequences",
"Beat The Clock", "Concentration") to today's "Survivor", "Deal or No Deal",
and "The Weakest Link", and interactively draws upon their strategies and
expertise to demonstrate how to more effectively manage metadata, and, when
necessary, perform those Extreme Metadata Makeovers. Attendees will enjoy
and learn from an experienced and entertaining metadata practitioner with
over 20 years of expertise, and will be able to walk away with a new-found
ability to support their organizational needs!
OMG’s Common Warehouse Metamodel (CWM) is mature
and stable, with widespread and still-increasing adoption by vendors and
customers for metadata interchange: most widely in the area of relational
database information.
OMG is now in the process of adopting a replacement standard called the
Information Management Metamodel (IMM) that broadens the applicability of
the standard and its integration with a number of other OMG standards to
address many other areas including UML, Ontology Modeling, XML Schemas and
Service Oriented Architectures; and the automated transformation and management
of development through OMG’s Model Driven Architecture approach.
Another key aim of IMM is to increase take-up and tool support in the data
management community. At the time of the DAMA conference the submission
will be at initial revision stage and one aim of the presentation is to
solicit feedback and involvement.
This presentation will cover the following aspects of IMM:
- Background
- Requirements
- Usage scenarios
- Overview of initial submission
Bigger picture of OMG standards:
- Technology support including Eclipse
- Roadmap
- How to contribute
Metadata has proliferated so much that it needs ITS
OWN metadata in order to be useful and accessible. Most existing metadata
solution implementations have partially addressed one or more of the following:
- Content Management, keeping the pieces away from the wholes
- Metadata which clarifies whatever was within scope at the time
- Taxonomies, used to categorize and access whatever has been
deemed to be accessible
Today’s metadata needs a rebirth. This discussion will overview a new environment
and discuss the way to get there.
We have entered a transformational era in software development that uses metadata to drive development and puts the business need at the center of the process. Those who can translate business needs into concise, accurate and complete models have a critical role to play. There is an emerging importance to modeling which grays the line between analysis and development. If modelers are enabled to be rigorous enough, then using metadata driven techniques can create a high percentage of the code in many types of applications. These techniques often reduce the development effort to fit and finish kinds of tasks, roughly 30% of what businesses are used to spending. This is dramatically shortening development cycles and enabling business agility with metadata getting the ROI credit. We will share the vision of software manufacturing and code patterns, the challenges and the realities, while maintaining a focus on the contribution of the modeler.
SoX and BASEL II have made painfully obvious that there is no "single version of the truth" to describe lineage for an organization, nor to correctly identify impacts due to change. At its core, lineage (impact) analysis is multi-concurrent development milestone infested and requires configuration managed support for change. This session goes beyond the usual "single" "enterprise architecture" "version of the truth" to analyze the soft underbelly of metadata management in the post-modern metadata world: a world with a wide array metadata sources and targets, gaggles of formats and APIs for exchange, a myriad of versions of systems being concurrently "tweaked" (and out-right modified), and an army of one (or a few good)
data administrator trying to merely get accurate lineage reports
One of the major challenges in implementing and promoting
a business meta-data repository is keeping it up to date. One of the
areas in keeping the business meta-data up-to date includes managing
changes to the existing content integrated from diverse business divisions
of the organizations. This presentation will build upon last years presentation
- business metadata repository a starting point - and will discuss change
management processes and tool features that should be considered before
implementing or buying a meta-data solution.
Some of the key areas of discussions will be:
- Business Meta-data – A Starting point : Quick review (from 2006 presentation)
- Meta-data change management committee structure
- Sample change management process
- Practical issues in tracking certain content changes
- Features to be considered before implementing a business metadata repository to support change management
- Change Management - Versioning and Archival
- Change Management - Role-Based Security/
This case study explores the issues associated with
developing a data standards program for establishing consensus and coordinating
data exchange across an extended, multi-jurisdictional enterprise. One of
the major challenges was the variation and disparity of data element formats,
data types, and most importantly, definitions. The institution of a community-wide
data standards governance program addressed these challenges, and in combination
with an ISO/IEC 11179-based data standards registry, provides a single repository
for managing the data standards process.
Thursday, March 8th
9:50 am - 10:50 am
The
Metadata Debate - M. David
Allen, Booz Allen Hamilton; David Rafner, Data Blueprint
How should we approach the practice of metadata?
IT strategists with visions of SOA and unifying ERP systems are maneuvering
for control of data assets. They bring grand designs for a centralized metadata
approach that promises to add value to data management and improve agility.
Down in the trenches, data architects and managers are understandably wary
of policy-heavy, impractical efforts that siphon off resources. What happens
when these two different perspectives collide? Come find out in an unconventional
metadata debate between an Enterprise Planner and an Application Manager.
How does the Enterprise Planner's vision for data strategy, standards, agility,
and compliance conflict with the Application Manager's operational priorities,
customer service, and requirements analysis? Is the Application Manager
missing the forest for the trees? Will the Enterprise Planner help, or hinder
operations?
As companies react to the rapidly changing regulatory
environment and work to mitigate risk, audits have become a frequent
tactic for monitoring compliance. Internal and external audits, as well
as regulatory investigations, regardless of purpose, ask similar questions.
Whether for SAS 70, Sarbanes-Oxley, or legal investigation, nearly every
auditor within your organization seeks the same thing – metadata. But
do those companies who spend thousands on audits place the same monetary
value on metadata management? Drawing on nearly a decade of experience
in the healthcare and financial sectors, Bill will not only help you
learn ways to educate your organization about the value of metadata
in an audit, but also how to find metadata that is already in the budget
(one clue: it won’t be called metadata) and align your IT objectives
with the organization’s business in an effective and mutual beneficial
way.
Attendees will learn:
- How auditors’ investigations relate to metadata management
- Ways to demonstrate metadata’s cost-benefit to the audit process
- Ways to adapt to the language and goals of the business without losing focus on metadata
- How to learn from your executives what they already know about metadata
- How to find hidden metadata initiatives in the budget and corporate initiatives
|
