Enterprise Architecture Planning (EAP) Administrative Computing Services 12/17/2002

1
Enterprise ArchitecturePlanning(EAP)Administra
tive Computing Services12/17/2002
2
Topics

• What is Enterprise Architecture Planning (EAP)?
• What is an EA used for?
• Why should we do it?

3
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?
4
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
5
Example Technical Blueprint
6
Example Organizational Data/Entities
7
Example Organizational Data Attributes
8
EAP Consists of...

• A standard methodology
• A standard framework
• A standard set of templates
• A repository
• A change management process

9
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

10
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

11
Adopted Baseline Reference Technology

• J2EE
• XML
• LDAP Directory
• Business Portal (uPortal) as application
  development and integration framework

12
Adopted Zachmans Framework for Information
Systems Architecture
13
Topics

• What is Enterprise Architecture Planning
  (EAP)?
• What is an EA used for?
• Why should we do it?

14
What is an EA used for?

• Investment decisions, vendor selection
• Modeling
• Analysis
• Requirements definition
• Planning
• Describing, understanding, and communicating

15
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.

16
Architecture Defines the Transitional Roadmap
Source Federal Conceptual Architecture model
17
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!

18
Non-optimum HRIS Situation
Staffing Management (Job Description Builder,
QuickRec, FastClass)
Payroll
Applicant Tracking
DATA
DATA
DATA
Training Mgmt.
DATA
Budgeting
DATA
Employee Evaluation
DATA
19
Optimum Situation
Staffing Management (Job Description Builder,
QuickRec, FastClass)
Payroll
DATA
Training Mgmt.
Applicant Tracking
Budgeting
Employee Evaluation
Integrated Systems and Data
20
Non-optimum Payquest
Pediatrics
AdCom Payquest
Billing Agency Info
Billing Agency Info
Gastroenterology
Billing Agency Info
21
Optimum Payquest Situation
Gastroenterology
Pediatrics
Billing Agency Info in LDAP Directory
Any LDAP compliant software (DralaWorkflow,
uPortal, Expresso)
Training Mgmt.
AdCom Payquest
Eudora
Any department
Integrated Data and Access Control
22
Present Stovepipes
Source Federal Conceptual Architecture model
23
Desired State
Source Federal Conceptual Architecture model
24
Target
Source Federal Conceptual Architecture model
25
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.

26
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.

27
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

28
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?

29
Zachman reflections on EA Planning
"You may think this is too much work Or, it
takes too long And it costs too much Or is too
theoretical Or too high risk Or too
whatever. However, if thats your assessment You
cant complain that the systems arent aligned
with the enterprise,or are inflexible, or cost
too much, or that vital information is not
available, or that the data you get isnt any
good, or too late, or you cant change anything,
or that I/S is slow and unresponsive and, I am
here to tell you Outsourcing isnt going to fix
the problem. Packages (in themselves) wont fix
the problem. Decentralization wont fix the
problem. And, the Internet isnt going to fix the
problem. No amount of money, Or technology is
going to fix the problem! It is NOT a technical
problem, it is an ENTERPRISE problem. Only
ACTUAL WORK is going to fix the problem,
and Someday, you are going to wish you had all
those models, Enterprise wide, horizontally and
vertically integrated, at excruciating level of
detail. You might as well start working on them
TODAY!!! John Zachman
30
Benefits
Facilitates information services that
provide flexibility interoperability reliability
survivability affordability sustainability portab
ility reusability adaptability compatibility
31
Business Benefits of EAP

• Focus on strategic use of technology for managing
  data as an asset
• Standard vocabulary facilitates communication and
  reduces inconsistency and data redundancy
• Documentation increases understanding of the
  business
• Models can be used to explain the business and
  assess the impact of business changes
• Decision making policies can be reviewed
• It allows for a comprehensive, objective and
  impartial approach
• The long range systems plan compliments the
  business plan
• It involves a feasible migration strategy with
  short term achievements
• It is easier to assess the benefits and impact of
  new systems and software
• It allows easier accommodation of dynamic
  business changes

32
Examples - Entities
A distinguishable - person - about which
information is kept. place, thing,
event, concept
Source U.S. Coast Guard Information Architecture
33
Work involved...

• Refine goals, objective, principles
• Establish membership
• Identify a methodology
• Identify a framework
• Identify resources
• Define deliverables
• Refine timeline

34
Definitions - Miscellaneous
Technical Reference Model - A common framework,
probably conceptual, to define a common
vocabulary so as to better develop and aquire
some level of support. It would provide you with
a representation of the domain showing commonality
and integration and interoperability. Common
Operating Environment - The set of capabilities
that would allow you to address the suite of
integration products that you need to ensure
a cohesive framework of systems for development.
Like the DII COE address architecture, standards,
software reuse, shared data, interoperability, por
tability, configuration management and
integration. Standards Roadmap - It would start
with a common set of mandatory standards and
guidelines. It would then be tailored to the
development that was being implemented. So it
would be the "building codes" that would
be reviewed and selected to facilitate the
development of the system or systems needed to be
built. (A Technical Architecture View for
a particular area (Defense Transportation System)
starting from the DOD Joint Technical
Architecture.) Dick Webb, ASD(C3I)