Enterprise Architecture

Planning
(EAP)
Administrative Computing Services
12/17/2002
 Topics

What is Enterprise Architecture Planning (EAP)?

What is an EA used for?

Why should we do it?

Dec 17, 2002 2

 What is an Enterprise Architecture?

A comprehensive blueprint of an organization by which we

analyze and plan changes and make additions.

The structure of (Enterprise) components and their

relationships, as well as principles and guidelines governing
their evolution over time.

A common understanding, of the names and definitions of our

organizations entities.

MOST IMPORTANTLY: THE MODELS

... We need to build a new application

What do we have already in place? Impact?

Dec 17, 2002 3

 What is an Enterprise Architecture?

The EA is a strategic asset repository which defines the current

and target architecture environments, including:

the business (processes),

the information (data or entities),

the technology, and

the transitional processes that keeps all aligned.

Emphasis on Logical, not Technological

Technology will always change
Beware of Protocol Gas!
Source: Federal Conceptual Architecture model

Dec 17, 2002 4

 Example: Technical Blueprint

Dec 17, 2002 5

 Example: Organizational Data/Entities

Dec 17, 2002 6

 Example: Organizational Data Attributes

Dec 17, 2002 7

 EAP Consists of...

A standard methodology

A standard framework

A standard set of templates

A repository

A change management process

Dec 17, 2002 8

 Methodology adopted: Guiding Principles

Conceptual Guiding Principles for all Architecture Domains

Specific Domain Architecture Guiding Principles

Commercial-Off-The-Shelf Solutions
Developed Applications
Middleware
Network
Platforms
Security
Databases
Operations Management

Dec 17, 2002 9

Adopted Sliding Window Technology Change
Management Methodology

Matrix for a 4-year, 16-quarter sliding window within

which the various recommendations for the Specific
Domain Architectures are documented.

Document which components should be researched,

piloted, invested in, maintained but not upgraded,
disinvested, obsoleted, and rejected.

Planning Architecture Governance and Change

Management Procedures

Dec 17, 2002 10

 Adopted Baseline Reference Technology

J2EE

XML

LDAP Directory

Business Portal (uPortal) as application

development and integration framework

Dec 17, 2002 11

Adopted Zachmans Framework for Information Systems Architecture

Dec 17, 2002 12

 Topics

What is Enterprise Architecture Planning (EAP)?

What is an EA used for?

Why should we do it?

Dec 17, 2002 13

 What is an EA used for?

Investment decisions, vendor selection

Modeling

Analysis

Requirements definition

Planning

Describing, understanding, and communicating

Dec 17, 2002 14

 What is an EA used for?

Promote interoperable and cost-effective systems

Provide the rules, guidance and governance for buying or

developing systems and managing change

Ensure a common denominator for understanding, describing,

comparing, and integrating systems

Provide a mechanism for managing complexity.

Dec 17, 2002 15

Architecture Defines the Transitional Roadmap

Source: Federal Conceptual Architecture model

Dec 17, 2002 16

 Topics

What is Enterprise Architecture

Planning (EAP)?

What is an EA used for?

Why should we do it?

Too much work!

Too difficult!

Too many deadlines!

Dec 17, 2002 17
 Non-optimum HRIS Situation

Payroll Staffing
Management (Job
Description Builder,
Applicant QuickRec,
Tracking FastClass)
DATA
DATA

DATA
Training
Mgmt.
Budgeting
DATA
DATA
Employee
Evaluation
DATA

Dec 17, 2002 18

 Optimum Situation
Staffing
Payroll
Management (Job
Description
Builder, QuickRec,
FastClass)

DATA
Applicant Training
Tracking Mgmt.

Competency
Budgeting
Modeling Employee
Evaluation

Integrated Systems and Data

Dec 17, 2002 19
 Non-optimum Payquest

AdCom Pediatrics
Payquest

Billing
Billing Agency
Agency Info
Info

Gastroenterol
ogy

Billing Agency

Info

Dec 17, 2002 20

 Optimum Payquest Situation

Pediatrics Gastroenterolo
gy

Billing Any LDAP compliant

AdCom Training
Payquest Agency Info software (DralaWorkflow,
Mgmt.
uPortal, Expresso)
in LDAP
Competency
Modeling
Directory Eudora
Any department

Integrated Data and Access Control

Dec 17, 2002 21
 Present Stovepipes

Source: Federal Conceptual Architecture model

Dec 17, 2002 22

 Desired State

Source: Federal Conceptual Architecture model

Dec 17, 2002 23

 Target

Source: Federal Conceptual Architecture model

Dec 17, 2002 24

 How do we get to the Target?
Understand our challenges, goals and Guiding Principles.

Apply and maintain 16-quarter Sliding Window technology

management Matrix for Domain Architectures (Security, COTS, etc).

Build in Reference Technology (J2EE, XML, LDAP, Portal)

Populate Zachman Framework Row 1 - the Planners perspective.

Work with our business units to populate Zachman Framework

Row 2 - the Stakeholders perspective (business models).

Understand where we take shortcuts, why, and for how long.

Plan, organize and commit.

Communicate.

Dec 17, 2002 25

 Why? Too much work! Impossible!
Applications in different technologies
Redundant code, redundant data with multiple uses
Redundant security, user/group management
30 year old systems
Alignment with business needs not timely
Data quality issues
Costly integration
Customized development of application instead of
assembly from parts
Funding (State Budgets depend on explicit EAP )
Projects done without architecture planning cost
significantly more in long term (John Zachman)
Without it, we cant understand impact of change.

Dec 17, 2002 26

Benefits to the Business of planned systems

More responsive to customers needs

Reduced data-entry costs

Efficient systems maintenance means improved service.

Architectures eliminate complex costly interfaces between incongruent systems

Management decisions in all functional areas will be based on more accurate and timely
data, leading to various improvements and cost-saving measures

New systems are developed faster and at less cost due to common data, common
code, and a shortened requirements phase

Easier to evaluate and select vendor SW packages

Source: Enterprise Architecture Planning

Steven Spewak

Dec 17, 2002 27

 Conclusion

What is Enterprise Architecture Planning?

What is an EA used for?

Why should we do it?

MOST IMPORTANTLY: THE MODELS

... We need to build a new application

What do we have already in place? Impact?

Dec 17, 2002 28