1. Enterprise Architecture Planning
Steven H. Spewak

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 organization’s entities.
MOST IMPORTANTLY: THE MODELS
... We need to build a new application… What do we have already in place? Impact?
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
When we say Enterprise Architecture Planning, the Architecture part is a comprehensive blueprint of an organization.
The planning part is the definition, development and most importantly the implementation and configuration management of the architecture.

3. EAP Purpose Emphasizes
Organizing and directing EA projects
Obtaining management commitment
Presenting the plan to management
Leading the organization from plan to implement
No attention is given to technical design or implementation

4. EAP Major Principles
Enterprise data accessible whenever and wherever needed
Information Systems should adapt to meet changing business needs
High data integrity and standards should exist across the enterprise
All enterprise data systems should be integrated

5. EAP Consists of... What is an EA used for? A standard methodology
A standard framework
A standard set of templates
A repository
A change management process
What is an EA used for?
Investment decisions, vendor selection
Modeling
Analysis
Requirements definition
Planning
Describing, understanding, and communicating
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.

6. 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
Management participation provides a business prospective, credibility, confidence

7. Non-optimum HRIS Situation
Payroll
Staffing Management (Job Description Builder, QuickRec, FastClass)
Applicant
Tracking
DATA
DATA
DATA
Training
Mgmt.
DATA
Budgeting
DATA
Employee
Evaluation
DATA
Figure 1

8. Optimum Situation DATA Integrated Systems and Data
Staffing Management (Job Description Builder, QuickRec, FastClass)
Payroll
Competency
Modeling
DATA
Applicant
Tracking
Training
Mgmt.
Budgeting
Employee
Evaluation
Figure 2
Integrated Systems and Data

9. Implementation/Migration Plans
Components of EAP
Planning Initiation
Layer 1
Layer 2
Business Modeling
Current Systems &
Technology
Layer 3
Data Architecture
Application
Architecture
Technology
Architecture
Implementation/Migration Plans
Layer 4
Figure 3

10. Planning Initiation
There are three contributing reasons for never completed EAP project:
the EAP projects may begin on the wrong track by having unreasonable objectives or unrelistic expectations
Selecting an approach that will not achieve the desired result in the time alloted
The participants are unfamiliar and inexperienced with EAP
There are two major deliverables resulting from the Planning Initiation phase:
Tangible  the EAP project workplan that specifies the phases and steps necessary to accomplish the goals of EAP (to develop the architectures and implementation plans)
Intangible  the support and commitment of executives and management throughout the enterprise for successfully completing EAP
Seven Steps of Planning Initiation:
Determine scope and objectives for EAP
Create a vision
Adapt a planning methodology
Arrange for computer resources
Assemble the planning team
Prepare EAP workplane
Obtain/confirm commitment and funding

11. Business Model
Business Modeling is the process of defining the business. The purpose of the business model is to provide a complete, comprehensive, consistent knowledge base that can be used to define the architectures and implementation plans
Three Steps to Business Modelling:
Document the organization structure
Identify and define the business functions
Document the preliminary business model and distribute and present it back to the business community for comments
Strategic business Planning is the process of defining the mission and long-range objectives for conducting the business, and developing the strategies for achieving them.
Strategic business Planning defines what the business is, what the business wants to be, and how the business wil get there. It is essentially have the same concept with the EAP layers (the wedding cake showed in figure 3)

12. Strategic Business Planning
Based on the mission of the company, the current situation, and factors external to the company (Strengths, Weaknesses, Opportunities, Threats) business objectives are formed. Functions are established in support of those objectives, and each business area may produce a plan for achieving the objectives.
Mission
Functions
Objectives
External Factors (SWOT)
Product (CSF)
Organization (Structure /Charters)
Financial (Statements /Models)
Systems (Architecture /EAP)
Figure 4
Basically, there are four different kinds of formal strategic plan (product, organization, financial, systems), each plan serves a specific and useful function. Product plans are programs and critical success factors that generally focus on the value chain of the organization.
Organization plan, typically produced by the human resources area and consists of items such as organization charts, department charters, responsibility and job descriptions.
Financial plan generally consists of financial statements and various economic and econometric models.
System (information system) plan includes architectures for data, applications, and technology and the associated implementation plans.

13. Current System And Technology Architecture
The purpose of this phase is to document and define all of the systems and technology platforms in use within the enterprise. The result of this phase is Information Resource Catalog (IRC) or Systems Encyclopedia. There are at least 8 reasonswhy every enterprise should have an IRC:
The IRC provide a reference to all information resources.
The IRC shows the distribution of information resources throughout the enterprise.
The IRC can be used ad an information locator for management throughout the enterprise.
The IRC can be used to orient new personnel to the IS department.
The IRC is used by the EAP team as a baseline for long-range planning.
Budgeting and cost control decisions can be directly linked with the IRC.
The IRC is a quick success at reasonable cost.
The IRC represents an internal use of documentation tools.
Eight Steps for Building An IRC:
Determine the scope, objectives, and IRC workplan.
Prepare for data collection.
Collect the IRC data.
Enter the data.
Validate and review the draft of the IRC.
Draw schematics.
Distribute the IRC.
Administer and maintain the IRC.

14. Data Architecture
The Data Architecture identifies and defines the major kinds of data that support the business functions defined in the business model (row 1 and 2 of the data architecture in The Zachman Framework). The data architecture definitions become the standards to be used as the basic for the systems design phase, from the logical database design, to the physical database design, to the database creation (row 3, 4, and 5 in The Zachman Framework). The data architecture consists of data entities, each of which have attributes and relationships with other data entities.
Four Steps for The Data Architecture Phase:
List candidate data entities.
Define the entities, attributes, and relationships.
Relate the entities to hte business functions.
Distribute the data architecture.

15. Applications Architecture
The purpose of The Applications Architecture is to define the major kinds of applications needed to manage the data and support the business functions of the enterprise. The applications architecture is not a design for system. It is also not a detailed requirements analysis. It is a definition of what applications will do to manage data and provide information to people in performing business functions. Applications are the mecanisms for managing the data of the enterprise, includes activities such as entering, editing, sorting, changing, summerizing, archiving, analyzing, and referencing data.
Five Steps to Apllications Architecture:
List candidate applications.
Define the applications.
Relate applications to functions.
Analyze impact to current applications.
Distribute the applications architecture.

16. Technology Architecture
The purpose of The Technology Architecture is to define the major kinds of technologies needed to provide an environment for the applications that are managing data. The applications architecture is not a detailed requirements analysis or a design of enterprise computing networks and software. It is a definition of the kinds of technologies – called platforms – that will support the business with a shared data environment. Technology platforms are the pipeline and physical fasilities of a data utility.
Four Steps to Technology Architecture:
Identify technology principles and platforms
Define the platforms and distribution.
Relate the technology platforms to apllications and business functions.
Distribute the technology architecture

17. Implementation Plan
The purpose of this phase is to formulate and prepare a plan for the implementation of the architectures. An architectures without implementation plans usually end up on a shelf with little benefit to the business
Four Step in Creating The Implementation Plan:
Sequence the applications (applications that create data should be implemented before applications that use data).
Estimate the effort, resources, and produce a schedule.
Estimate the costs and benefits of the plan.
Determine the success factors and make recommedations.