EIA Referencia Gartner
-
Upload
gabby-coello -
Category
Documents
-
view
253 -
download
5
description
Transcript of EIA Referencia Gartner
-
Notes accompany this presentation. Please select Notes Page view to examine the Notes text.
Gartner for IT Leaders Sample Presentation
EA Foundation for Enterprise Information Architecture
Approved for External Use Not for Resale. Unless otherwise marked for external use, the items in this Gartner Toolkit are for internal, noncommercial use by the licensed Gartner client. The materials contained in this Toolkit may not be repackaged or resold. Gartner makes no representations or warranties as to the suitability of this Toolkit for any particular purpose, and disclaims all liabilities for any damages, whether direct, consequential, incidental or special, arising out of the use of or inability to use this material or the information provided herein.
The instructions, intent and objective of this template are contained in the source document. Please refer back to that document for details.
-
GARTNER LEADER'S TOOLKIT 1
What Is Enterprise Information
Architecture?
Enterprise information
architecture, or the information
viewpoint of EA, describes
through a set of requirements,
principles and models the
current state, future state and
guidance necessary to flexibly
share and exchange enterprise
information to achieve effective
enterprise change.
Market
Opportunities
and Trends
SolutionArchitecture
Info
rma
tio
nV
iew
po
int
Business
Context
-
GARTNER LEADER'S TOOLKIT 2
Follow the Seven Steps to Developing EIA
Manage and Communicate
Govern
1.
Define
and
Scope
2.
Organize
3.
Future
State
4.
Current
State
5.
Gap
Analysis
6.
Migration
Plan
7.
Iterate
and
Refine
Prepare Architect Guide
-
GARTNER LEADER'S TOOLKIT 3
Run the
Business
Grow the
Business
Transform the
Business
Reduce information risks.
Increase productivity by improving data accuracy.
Improve situational awareness.
Deliver pervasive business intelligence.
Streamline processes through single versions of master data.
Support performance management to optimize growth.
Enable external information ecosystems.
Push relevant content in context.
Speed agility via data exchanges.
Communicate How EIA Contributes
to Business Value
Unlock the potential of information assets through EIA.
-
GARTNER LEADER'S TOOLKIT 4
Step 1: Define and Scope Enterprise Information Is Not All Information
1. Don't architect all information:
Avoid "boiling the ocean" data-modeling sojourns to perfection
2. Focus on enterprise information that is critical to the business strategy, as determined by:
Business impact
Decision impact
Risk impact
Organizational impact
3. Include internal and external information from suppliers, partners and customers:
Support drives toward information ecosystems
4. Examples:
Content: Master data, cross-team analytics, legal agreements (contracts), patents, product catalogs
Metadata: Locations and descriptive information
Transactions
ModelsMedia
CustomersEmployees Partners
Databases
Orgs.FinancialsProducts
WebContent
Reports
E-Mail
Enterprise
Information
Docs.
"Enterprise information" refers to diverse content that is consistently shared
across multiple business processes and capabilities.
-
GARTNER LEADER'S TOOLKIT 5
Data ArchitectApplication
Architect
Technology
Architect
Business
Architect
Solution/Project
Architecture
Data AnalystApplication
Analyst
Business
Analyst
IT Management
& Support Staff
Enterprise
Architecture
Enterprise
Information
Architect
Enterprise
Solution
Architect
Enterprise
Technology
Architect
Enterprise
Business
Architect
Chief
Enterprise
Architect
Data
Architecture
Team Member
Solution
Architecture
Team Member
Technology
Architecture
Team Member
Business
Architecture
Team Member
Project
Architect
Infrastructure
Planner
Business
Management &
Support Staff
Step 2: Organize
-
GARTNER LEADER'S TOOLKIT 6
Step 3: Develop Future-State Information
Requirements
-
GARTNER LEADER'S TOOLKIT 7
Step 3: Develop Future-State Information
Principles
Current State Future Vision
Vision:"Need to know": Sharing when
deemed necessary
"Responsibility to provide":
Sharing with appropriate security
Scope: Department-centric: Based on unit's primary function
Enterprise-centric: Ecosystem
stretching across boundaries
Collaboration:Static: Policies with little
change or flexibility
Security:
Access:
Usage:
Operational Drivers
"Self-generating": Rapidly
adapt to changing needs
Network-centric: Security
designed (DMZ, firewalls)
Information-centric: Security
built into data (XML)
Compartment-based:
Security access and controls
Attribute-based: Based on
attribute classification
"Data owner": Controls on
access and distribution
"Data steward": Shift mind-set
to facilitate sharing
Strategic
Drivers
Adapted from "Intelligence Community Information Sharing Strategy,"
U.S. Office of the Director of National Intelligence, 22 February 2008.
-
GARTNER LEADER'S TOOLKIT 8
Step 3: Develop Future-State Models
Bank XYZ Implementation Information Viewpoint Example
Customer Dimension
-
GARTNER LEADER'S TOOLKIT 9
Step 4: Conduct the Current-State
Assessment
Business Partners
Ve
nd
ors
Customers Prospects
Oth
er B
an
ks
Re
gu
lato
rs
Ad
ve
rtis
ing
Ag
en
cy
Access Points
Marketing & Sales, Call Center, Web-Based, ATM, Direct Sales, Branch, Other
PMO Corporate Affairs Legal HRMIS / IT ControllerAccounting
Sales Marketing Operation Management Customer ServiceProduct Development/
Management
Money Desk LiabilitiesAssets Investments Portfolio
ManagementFunds Management
Retail/Commercial Banking Asset Management Investment Banking
Enterprise Functions
Treasury
Support Services
Fulfillment
Legend: C CustomerP Product CR Customer RelationshipU Underwriting E External Bank RelationshipPR Policies & Rules MS Money Supply
Information
Producer
Information
Consumer
C
C
C
C
C
P
PC
P
P
PP
C
P
P CR
CR
U
U
U
U
MS
MS
MS
MS MSMS
EE
E
PR
PR PR
PR
PRPR
PR
PR
PR
PRPRPR
PRPR
PR
PR
MSMS
C
Bank XYZ Conceptual Information Pattern
To Build the Current-State
Information Flow
Use Business
Anchor Model
-
GARTNER LEADER'S TOOLKIT 10
Step 5: Gap Analysis Example: Bank XYZ
Traces Gaps With Information Value Models
Customer
Master Data
Store
Customer Value
AnalyticsMarketing
Campaigns
Core Banking
System
Insurance System
IVN models provide an
enterprisewide
overview.
Traces information producers and
consumers.
Creates context for more-detailed work
at the logical and
implementation
levels.
Card Processing
System
Data
Warehouse
Product
Details Pro
du
ct
Deta
ils
Pro
du
ct
Deta
ils
-
GARTNER LEADER'S TOOLKIT 11
Initial
Organization:
EIA charter
Staffing and organization alignments
Governance:
Data stewardship program
Data quality measures
Software development life cycle (SDLC) changes
Information infrastructure:
Data services layer
Metadata management strategy
Organization:
Resolve role gaps
Content-oriented information architects
Governance:
Data stewards
Data quality scorecards
Information infrastructure:
Customer master data store
Data mart consolidation
Data services pilot
Organization:
EIM organization build-out
External data transfer processes
Governance:
EIM gates and swim lanes
Data audits
Information infrastructure:
"Information as a service"
Operationalize remaining master data stores
Content and records management
Build the Foundation
Position forSuccess
Achieve the Future Vision
Midterm Target
Step 6: Build Migration Plan to Drive EIA
Through EIM
-
GARTNER LEADER'S TOOLKIT 12
Step 7: Iterate and Refine Interoperability
Objectives to Support Evolving Business Needs
Beyond Many-to-OneBeyond One-to-One Enable Many-to-Many
EIA
Point-to-point, complex
data integration
Multiple versions of the
truth
Lack of agility
Information Providers
Information Consumers
Rigid (one-size)
model
Vendor lock-in
Lack of independence
Less innovation
Managed diversity
Federated
independence
Simple set of
constraints
Generalized identifiers, formats and protocols to flexibly share and exchange enterprise information across multiple business process or diverse groups
Focus on "lean" and "simple" information capabilities such as master data, metadata management and common services (e.g., data cleansing)
To
Generalized
Capabilities
From
Traditional
Approaches
-
GARTNER LEADER'S TOOLKIT 13
Core
Enterprise Information: Refers to diverse content that is consistently shared across multiple business processes and capabilities
Enterprise Information Architecture: Requirements, principles and models to flexibly share and exchange enterprise information
Enterprise Information Management: Integrative discipline for structuring, describing and governing enterprise information
Master Data: Consistent and uniform set of identifiers and extended attributes that describe the core entities of the enterprise, shared across multiple business processes
Step 7: Iterate and Refine to Monitor the
Volume and Diversity of information
Diverse
Common
-
GARTNER LEADER'S TOOLKIT 14
Key Actions
First:
Educate your team on enterprise information architecture and how it is evolving.
Prepare a "talking points" document outlining how enterprise information architecture would work in your organization.
Second (during the next six months):
Establish a core team to identify which information assets qualify as enterprise-significant.
Model the uniform and consistent master data, metadata and integration services that are shared across multiple business processes.
Third (during the next 12 to 18 months):
Deliver the required levels of EIA detail to design and implementation teams.
Formalize the realization of EIA through an EIM program.