W7: The Intel Metadata Program: A Best Practices Case Study
Jackie Gibson
Manager - Architecture Capabilities
Intel Corporation
David Ashton
Enterprise Metadata Architect
Intel Corporation
Thiru Thangarathinam
Enterprise Solution Architect
Intel Corporation
Intel recognized the need for an enterprise metadata container and implemented a repository to support data management. This repository was beneficial to data groups at Intel, but due to inconsistencies in architecture tools and processes, the resultant work products were siloed and did not provide an integrated view across the BDATS architecture domains. Consequently, Intel kicked off an Enterprise Architecture Program to provide a structured, holistic approach to support future business, data, platform/application, techology, and solution decisions. A key deliverable of the EA program was to establish the Achitect's Toolkit. It provides Architects with a set of standardized building blocks in the form of Enterprise Architecture development tools, repository, supporting processes, and a single portal. The Architect's Toolkit enabled integrated enterprise architecture by establishing consistency in how architecture work products are created, stored, and made available to consumers. This was accomplished using metadata as the foundation.
This session answers the following questions:
- How did we determine building blocks for the Architect's Toolkit?
- How did we enable one-stop shopping for architecture work products using a federated repository approach?
- How did we determine appropriate standard work products?
- How were we able to achieve buy-in from the Architecture community?
- How did we get agreement for a centralized tools approach?
- How did we align architecture work products to Enterprise Architecture?
Comments (1)
jacque gibson said
at 12:22 pm on May 1, 2006
Take Home Points:
Metadata and Enterprise Model are Key to Reuse Value;
1. Cost Avoidance, Cost Reduction, Answering Business
Questions 2.Foundational for Enterprise Architecture and Enabling Transition to Service Oriented Architecture
Must enable Enterprise Architecture into Action;
1.Drives connections between process, data, apps, and tech 2.Establish Asset Inventory for Each Architecture View (BDATS)3.Architect Community trained on deliverables, processes, and criticality of metadata management.
Metadata must be managed to be of any value;
1.A repeatable process to identify and define metadata
2.Standard deliverables in which to capture metadata
3.Repeatable governance process to provide metadata credibility
Push versus Pull for Governance; 1.Strike a balance between Architecture driving versus self-managed actions
2.Mandate Common Tools and Governance Process - Standard Architecture Tools and Enterprise Metadata and Reuse Toolkit. Streamline Governance Processes
You don't have permission to comment on this page.