EA Standards Committee

1
EA Standards Committee

• Enterprise Architecture Management
• July 16, 2004

2
Contents

• Introduction
• Enterprise Architecture Planning
• Enterprise Architecture Methodology and Framework
• Enterprise Architecture Toolset
• Lessons Learned
• Whats Next

3
Definitions of the Terms Enterprise and
Architecture

• enterprise a unit of economic organization or
  activity.1
• architecture formation or construction as or
  as if as the result of conscious act a unifying
  or coherent form or structure.1

4
What is Enterprise Architecture?

• Enterprise Architecture (EA) is a strategic
  information asset base that defines the
  business,information necessary to operate the
  business, technologies necessary to support the
  business operations, and transitional processes
  for implementing new technologies in response to
  the changing needs of the business.
• Enterprise Architecture provides
• Strategic information A valuable asset that
  should be secured
• Defines the business Information is relevant and
  scoped
• Operate the business Adequately describes the
  existing environment
• New technologies Endeavors to provide future
  guidance
• Changing needs Responsive business climate
  fluctuations

5
Agile Organizations Require Adaptable
Architectures
1980s and earlier
1990s

• Organization Focus
• Mainframe centric
• Monolithic
• Internal use

• Business Process Focus
• Client/Server
• Monolithic
• Business-to-business via EDI -file transfer

• Virtual organizations
• Distributed Functions
• Service oriented
• Componentized
• E-commerce
• Real-time

6
Enterprise Architecture Collaboration
7
Layers of the Enterprise

• Fours Layers of the Enterprise Processes
• Planning
• Management
• Implementation
• Operations

8
Enterprise Architecture in the big picture
9
Governance Boards
10
Components of a Successful Enterprise Architecture
EA Planning
EA Framework/Methodology
EA Tool Set
11
Enterprise Architecture Planning

• Executive Support and Steering
• Stakeholder Buy-in
• Validation Process
• Socialization Process
• Integration with the Governance Boards
• Supports streamlined decision-making
• Process for EA development is iterative

12
OIT Enterprise Architecture Plan Elements

• Enterprise Architecture Guiding Principles
• Enterprise Architecture Governance Model
• Enterprise Architecture Advisory Board
• Enterprise Architecture Standards Committee
• Enterprise Architecture Process Overview

13
Iterative EA Process
14
Enterprise Architecture Framework/Methodology

• Customizable to environment and needs
• Simple in approach
• Useable at all levels of the organization
• Self-sustaining
• Outcomes-based methodology

15
OIT Enterprise Architecture Framework
16
Enterprise Architecture Methodology
17
Enterprise Architecture Toolset
EA Planning

• Need for EA Repository to manage and standardize
  data
• Must support web-based outputs and multiple
  views
• Must be standards based and have an open API for
  data exchange

EA Framework/Methodology
EA Tool Set
18
Building the CoPA Meta Model

• What are the major relationships a decision-maker
  would need?
• Business function to application
• Application to product
• Application to standards
• Others..
• Why are these relationships so important?

19
EA Meta Model
20
Data from existing processes
Keystone Plan, 3 Year CoP Plan, Agency Plan
CoP Business Case Templates
e-Gov Survey, HCIS, Agency Technology Profile
21
Benefits of EA

• Aligns business and technology with mission
• Provides technology standards and new
  requirements to the enterprise
• Provides SDLC with alignment information for
  milestone reviews
• Supports effective creation and management of IT
  portfolios

22
Lessons LearnedAn Enterprise Architecture is

• Successful when there is Executive
  buy-inespecially by Agency Heads
• A collaboration process between Strategic
  Planning, Portfolio Management, Solutions
  Architecture, Project Management and other key IT
  development processes
• business process centric and provides technology
  enablement
• An iterative process because it adapts to mission
  and business needs
• Only as good as the information it relates

23
Whats nextThe EA Knowledgebase

• Publishes traceability repository to a website or
  help file
• Customizable look-and-feel using HTML templates
  and CSS and XSL stylesheets
• Built-in matrix reporting and dependency
  visualization views
• XML-based meta-language and API for developing
  custom reports and views

24
Whats nextStandards Profile

• Promote interoperability and facilitate
  information exchange
• Support IT investment decisions
• Promote cost-effective software acquisition and
  support
• Guide procurement decisions
• Guide decisions throughout the IT investment
  lifecycle

25
Whats nextProposed IT Standards lifecycle...

• Retire -- CoPA will expend funds to move away
  from technologies supported by these standards
• Contain -- No further funds will be expended on
  technologies supported by these standards they
  will be phased out
• Current -- Technologies supported by these
  standards are currently being supported and
  purchased
• Target -- Moving to technologies supported by
  these standards will best meet the requirements
  of the To Be environment.

26
EA in a Nutshell

• Understand that EA provides a structure to ensure
  IT initiatives remain continually supportive of
  managements business objectives and strategies
• Understand EAs framework
• As-Is
• To-Be
• Migration Plan
• Recognize benefits of EA
• Ensures alignment of technology with mission
• Supports development of new capabilities and
  solutions
• Eliminates redundancy and fosters integration and
  interoperability of systems

27
EA is a change in culture

• "Nothing is more difficult than to introduce a
  new order. Because the innovator has for enemies
  all those who have done well under the old
  conditions and lukewarm defenders in those who
  may do well under the new."
• Nicolai Machiavelli, 1513 A.D.

28
Thank You.