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.
Notes accompany this presentation. Please select
Notes Page view to examine the Notes text.

What Is Enterprise Information

Architecture?

GARTNER LEADER'S TOOLKIT

Business
Context

Information
Viewpoint

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

Solution
Architecture

Follow the Seven Steps to Developing EIA

Manage and Communicate

1.

2.

3.

4.

5.

6.

7.

Define
and
Scope

Organize

Future
State

Current
State

Gap
Analysis

Migration
Plan

Iterate
and
Refine

Prepare

Architect

Guide

Govern

GARTNER LEADER'S TOOLKIT

Communicate How EIA Contributes

to Business Value
Run the
Business

Grow the
Business

Transform the
Business

Reduce
information risks.

Deliver pervasive
business intelligence.

Increase
productivity by
improving data
accuracy.

Streamline processes
through single
versions of master
data.

Enable external
information
ecosystems.

Improve
situational
awareness.

Support performance
management to
optimize growth.

Push relevant
content in
context.

Speed agility via

data exchanges.

Unlock the potential of information assets through EIA.

GARTNER LEADER'S TOOLKIT

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:

Enterprise
Transactions
Customers Employees Partners

Business impact

Decision impact
Risk impact

Financials Orgs.

Products
Reports

Organizational impact

3.

Include internal and external information from

suppliers, partners and customers:
Support drives toward information ecosystems

4.

Examples:

Web
Content

E-Mail

Databases

Docs. Models

Media

Information

Content: Master data, cross-team analytics, legal

agreements (contracts), patents, product catalogs
Metadata: Locations and descriptive information

"Enterprise information" refers to diverse content that is consistently shared

4
GARTNER LEADER'S TOOLKIT
across multiple business processes and capabilities.

Step 2: Organize
Enterprise
Architecture

Business
Management &
Support Staff

Chief
Enterprise
Architect

Enterprise
Technology
Architect

Enterprise
Solution
Architect

Enterprise
Information
Architect

Enterprise
Business
Architect

Technology
Architecture
Team Member

Solution
Architecture
Team Member

Data
Architecture
Team Member

Business
Architecture
Team Member

IT Management
& Support Staff

Solution/Project
Architecture

GARTNER LEADER'S TOOLKIT

Project
Architect

Technology
Architect

Application
Architect

Data Architect

Business
Architect

Infrastructure
Planner

Application
Analyst

Data Analyst

Business
Analyst

Step 3: Develop Future-State Information

Requirements

GARTNER LEADER'S TOOLKIT

Step 3: Develop Future-State Information

Principles
Strategic
Drivers
Vision:
Scope:

Operational
Drivers
Collaboration:

Security:

Current State

Future Vision

"Need to know": Sharing when

deemed necessary

"Responsibility to provide":
Sharing with appropriate security

Department-centric: Based
on unit's primary function

Enterprise-centric: Ecosystem
stretching across boundaries

Static: Policies with little

change or flexibility
Network-centric: Security
designed (DMZ, firewalls)

Access: Compartment-based:

Security access and controls

Usage: "Data owner": Controls on

access and distribution

GARTNER LEADER'S TOOLKIT

"Self-generating": Rapidly
adapt to changing needs
Information-centric: Security
built into data (XML)
Attribute-based: Based on
attribute classification
"Data steward": Shift mind-set
to facilitate sharing

Adapted from "Intelligence Community Information Sharing Strategy,"

U.S. Office of the Director of National Intelligence, 22 February 2008.

Step 3: Develop Future-State Models

Bank XYZ Implementation Information Viewpoint Example
Customer Dimension

GARTNER LEADER'S TOOLKIT

Step 4: Conduct the Current-State

Assessment
Use Business
Anchor Model

To Build the Current-State

Information Flow
Bank XYZ Conceptual Information Pattern
Customers

Prospects

Access Points

CR

Marketing & Sales, Call Center, Web-Based, ATM, Direct Sales, Branch, Other

P
Retail/Commercial Banking

Investment Banking

Asset Management

PR

PR

Other Banks

Fulfillment PR

MS

MS
U
P

MS
Assets

PR Treasury
PR
PR Portfolio MS U
Money Desk
Management
M
MS
S

MS

PR
Liabilities

Enterprise Functions C

C
Sales

Advertising Agency

GARTNER LEADER'S TOOLKIT

Product Development/
Management

Marketing

P
PR

MIS / IT

Corporate Affairs

Legal

PR
Legend:
P Product
U Underwriting
PR Policies & Rules

E
Operation Management

PR

Support Services
AccountingPR

Controller

PR
C Customer
CR Customer Relationship
E External Bank Relationship
MS Money Supply

CR

Customer Service

Business Partners

PR

Investments

Vendors

MS

Funds Management

PR

Regulators

HR

PR

PMO

PR
Information
Producer

Information
Consumer

Step 5: Gap Analysis Example: Bank XYZ

Traces Gaps With Information Value Models
Core Banking
System

Creates context for

more-detailed work
at the logical and
implementation
levels.

Card Processing
System

Product Details

Traces information
producers and
consumers.

Product Details

IVN models
provide an
enterprisewide
overview.

Insurance System
Product
Details

Customer Value
Analytics

GARTNER LEADER'S TOOLKIT

Customer
Master Data
Store

Data
Warehouse

Marketing
Campaigns

10

Step 6: Build Migration Plan to Drive EIA

Through EIM
Build the
Foundation
Organization:

Position for
Success
Organization:

EIA charter

Resolve role gaps

Staffing and organization

Content-oriented

alignments
Governance:

information architects
Governance:

Data stewardship program

Data stewards

Data quality measures

Data quality scorecards

Software development life

cycle (SDLC) changes

Information infrastructure:

Information infrastructure:
Customer master data

store

Data services layer

Data mart consolidation

Metadata management

Data services pilot

strategy

Initial
GARTNER LEADER'S TOOLKIT

Midterm

Achieve the Future

Vision
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

Target
11

Step 7: Iterate and Refine Interoperability

Objectives to Support Evolving Business Needs
Beyond One-to-One

Beyond Many-to-One

Enable Many-to-Many

To
Generalized
Capabilities

From
Traditional
Approaches
Point-to-point, complex

Rigid (one-size)

data integration
Multiple versions of the
truth
Lack of agility

model
Vendor lock-in
Lack of independence
Less innovation

EIA

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)
Information Consumers
GARTNER LEADER'S TOOLKIT

Information Providers

12

Step 7: Iterate and Refine to Monitor the

Volume and Diversity of information
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

Diverse
Common

Core

Master Data: Consistent and uniform

set of identifiers and extended
attributes that describe the core
entities of the enterprise, shared
across multiple business processes
GARTNER LEADER'S TOOLKIT

13

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.

GARTNER LEADER'S TOOLKIT

14