Managing Change Using Enterprise Architecture

Managing Change

Using Enterprise

Architecture

Abdallah El Kadi,

Managing Director, Open Group Arabia

Email: [email protected]

Agenda

The Changing Business Context

Enterprise Architecture Uses

Implementing Enterprise Architecture

Introduction to Enterprise Architecture

3



Organizations are

constantly having to

manage the external forces

that condition their

ecosystem



The pace of change has

accelerated extensively

over the last two decades.



Managing change has

become essential to

survival and vital to

growth.



Understanding the factors

that drive change and the

implication of change are

key to understanding the

architecture components

that the organization need

to focus on.

Customers

Customers

Suppliers

Suppliers EmployeesEmployees

Partners

Partners SuppliersSuppliers

Customers

Customers

Partners

Partners PartnersPartners

Ad Hoc Evolution Architecture

Strategic Realignment Process

SWOT & PESTL

Implications

Change In

Competitive

Landscape

Short Planning

Cycles

Change In

Organizational

Strategy

Strategic Direction

Adaptive Processes &

Enabling Technology

Change In

Operating

Model

Adaptable Architectures

1980’s and earlier



Organization

Focus



Mainframe centric



Monolithic



Internal use

1990’s



Business Process

Focus



Client/Server



Monolithic



Business-to-business

via EDI -

file transfer



Virtual organizations



Distributed Functions



Service oriented



Componentized



E-commerce



Real-time

New Millennium

Extranet

Internet

Customers

Problem Statement

•

Lack of strategic direction implication clarity

•

Lack of clear alignment between strategic direction and strategic

initiatives

•

Inappropriate performance results understanding

•

Lack of strategic and operational connect

•

Lack of cross functional alignment - Silo organization

•

Unnecessary complexity resulting from unplanned technology

acquisition

•

Poor understanding of the organization operation leading to poor

implementations

•

Failure to deliver on time to business change

•

Point solutions duplicating functionality

•

Lack of Business – IT integration

•

Lack of proper investment analysis for IT projects

Expectations of Enterprise Architecture

Key expectations from EA are:



business agility

–

‘…

is the ability of a business to adapt rapidly and cost

efficiently in response to changes in the business

environment’

•

Improve Strategic Planning



IT-business alignment

–

‘…correspondence between business objectives and IT

requirements of an enterprise’

•

Accelerate Implementation of Solutions



portfolio simplification

–

Technology standardization

•

Rationalize Technology Adoption

Agenda

The Changing Business Context

Enterprise Architecture Uses

Implementing Enterprise Architecture

Introduction to Enterprise Architecture

EA Defined – by law!

The E-Government Act of 2002 (Public Law (PL) 107-347) states that

Enterprise Architecture

–

Means:

•

a strategic information asset base, which defines the mission;

•

the information necessary to perform the mission;

•

the technologies necessary to perform the mission; and

•

the transitional processes for implementing new technologies

in response to changing needs; and

–

Includes:

•

A baseline architecture

•

A target architecture

•

A sequencing plan

The Building Analogy

Consider A Building…



Would you construct a building without any plans?



Inadequate construction materials, no quality standards, no defined

methods, may not meet building regulations, no safety guarantees, no

definite road to successful completion of the building, etc



To extend an existing building without a blueprint you would use:

–

Trial and error to implement the solution

–

Conduct a discovery exercise first – reverse engineer the

As-Is

–

Knock down current building and rebuild from scratch



The same should be the case for an organization!

Blueprints provide different view points

General Architect

Plumbing Architect

The Importance of Architecture

The Winchester “Mystery

House”

 160 Rooms  47 Fireplaces  6 Kitchens

 10,000 Windows

 65 Doors to Blank Walls  13 Staircases Abandoned  24 Skylights in Floors



147 Builders



0 Architects

16

“$5.5 Million Total Cost Over 38 Years

Vision of a state-of-the-art abode…

…built without a “blueprint”…”

The Composite View

In order to pro-actively adapt to change in the short term while

building a cohesive & integrated Architecture in the long term, you

need to see the BIG PICTURE of the WHOLE to improve planning

while having the capability to ZOOM into the DETAILS of the

Enterprise Architecture Definition

•

EA is

an emerging practice devoted to improving the performance of the

enterprises

by enabling them to see themselves in terms of the holistic and

integrated view.

•

EA is a

strategy and business-driven activity that supports management

planning and decision making

by providing coordinated views of an entire

enterprise.

•

By developing current and future versions of its integrated views,

organizations

can better manage change and the transition

to the target operating environment.

•

EA is the

explicit description and documentation of the current and desired

relationships among business processes, information, Applications &

technology.

•

EA is the

blueprint of an organization to analyze and plan changes

.

•

EA helps in identifying the

relationship between strategic initiatives and their

supporting technology components.

•

EA

reflects the structure of (Enterprise) components, relationships, and

principles and guidelines

governing their evolution over time.

Vision _Strategic Objectives Initiatives Process Groups Process Maps Challenges & Opportunities Policies Technology Departments Roles Responsibilities Network Data Applications Hardware Drives Mission

Translates into Executed through To overcome Or take advantage of Executed by Responsible for Composed of

Executed by Based on

Belong to Use Run on Use Linked to Abide by Uses Plan Execute Manage Enable

Perspectives

Visualize the Enterprise Entities

SLA’s _Services Issues

Visualized, Structured, Linked and

Traced,

Business Strategy Organization & Process IT Services, Applications and Infrastructure Service Level Manager IT Service Manager Produce performance reports for IT Services and IT SM Processes Analyse performance and identify mngt action required Distribute performance reports to relevant stakeholders Perform immediate management activities required

Manage SLM Staff Performance Monitor

performance of SLM infrastructure

SLM Mngt reports produced and distributed SLM Performance analysed and immediate response completed Start reporting period (month)

Network Topologies

Behavior (UML Support)

Organizational Charts

Matrix Views

Application Models

Data Models ObjectivesGoals Process Models

SDLC

Enterprise Architecture Holds:

•

Enterprise Strategic Information

•

Enterprise Process Information

•

Enterprise Data / Application

Information

•

Enterprise Technology

Information

•

The relationships between all the

above information types across

all organization units.

Breadth

Span

D

ep

th

Agenda

The Changing Business Context

Enterprise Architecture Uses

Implementing Enterprise Architecture

Introduction to Enterprise Architecture

Agenda

Organizational Integrated Model

A Business Strategy is implemented…

By offering business Services…

Which are delivered through business processes… Organized into a set of

activities…

That process information…

Automated by an application

functionality… Composed from

application services…

EFQM

EFQM

Excellence Building Blocks

Corporate Strategy Enterprise Leadership Operational Plans Performance Management Business Value Chain Business Services Business Processes Information Architecture Technology Architecture Application Architecture Organization Operating Model Environment & Trends Human Capabilities Service Capabilities Suppliers Customers

Agenda

IT Value Chain

Strategic Planning

Project Management

Operations Management

IT Strategic Planning

Enterprise Architecture

Portfolio Management

Program Management

Service Management

Security Management

Business Priorities

Strategic Value

Agenda

The Changing Business Context

Enterprise Architecture Uses & Benefits

Implementing Enterprise Architecture

Introduction to Enterprise Architecture

Enterprise Architecture Framework



A glossary of modeling standards to be used for EA communication



Each model type enables the representation of a specific set of

information from a specific view point



Provides the foundation for consistent modeling and communication



Enables a structured approach for resolving issues by enabling

effective representation of the problem and the envisioned solution

and the roadmap required to achieve it



The selection of the model type should take into account all the

information necessary to address the needs of the stakeholders



Each information object will have a set of attributes and relationships

to connect it to the rest of the models.



Several standard frameworks exist: TOGAF, Zachman, FEAF,

MODAF, DODAF…



Some frameworks are industry specific and others are generic

TOGAF 9 – Meta Model

The META MODEL holds • The information objects • The attributes and their meta

data

• The relationships wit each other

• The structure that links all the framework elements together • The rules that govern how

information is captured • The basis for the impact

analysis

Enterprise Architecture Lifecycle



A problem solving methodology



It is a step by step process that analyzes business and IT problems

and help define the appropriate solution and its associated roadmap



Use the modeling language defined in the enterprise architecture

framework to represent the problem and design the proposed solution



Has associated roles, responsibilities and templates



Enables more effective and faster decision making while providing

solid foundation for implementation



Many enterprise architecture lifecycles exist one of the most

commonly used ones being the TOGAF Architecture Development

Method (ADM)

Enterprise Architecture Lifecycle - TOGAF

Prepare the organization for a

successful architecture project

Ensure that very stage of a

TOGAF project is based on and

validates business requirements

Set the scope, constraints and

expectations for a TOGAF project;

create the Architecture Vision;

validate the business context; create

the Statement of Architecture Work

Develop Business

Architecture

Develop baseline and target

architectures and

analyze the gaps

Develop Information

Systems Architectures

Develop baseline and

target architectures and

analyze the gaps

Develop Technology

Architecture

Develop baseline and target

architectures and

analyze the gaps

Perform initial implementation

planning; identify major

implementation projects

Analyze costs, benefits and

risks; develop detailed

Implementation and

Migration Plan

Provide architectural oversight

for the implementation; ensure

that the implementation

project conforms to the

architecture

Provide continual monitoring and a

change management process to

ensure that the architecture

responds to the needs of the

Segment Architecture Partitioning

Allows for management of costs and complexity by dividing up the Enterprise and assigning appropriate roles and responsibilities to each partition

Allows for management of costs and complexity by dividing up the Enterprise and assigning appropriate roles and responsibilities to each partition

•

Managing

Complexity

•

Managing Conflicts

•

Managing Parallel

developments

•

Managing Re-use

•

Enable on-demand

Characteristics of Architectures

•

Subject Matter

–

Architectures describe specific

solutions and inherit objective

characteristics of the solution

•

Viewpoints

–

These are based on the needs of

the stakeholders

•

Level of Detail

–

The level of detail used to represent

a solution has a strong influence on

how an architecture can be used

•

Level of Abstraction

–

How abstracted the architecture is

from the solution

•

Accuracy

–

Any architecture is a model and not

intended to completely accurate

Agenda

The Changing Business Context

Enterprise Architecture Uses & Benefits

Implementing Enterprise Architecture

Introduction to Enterprise Architecture

Government Organizations that adopted the philosophy and

practice of enterprise architecture include:

EA Local Implementations

• Dubai Police

• Dubai Municipality

• Dubai Roads & Transport Authority

• Dubai Customs

• Dubai Civil Defense

• Abu Dhabi Judicial Department

• Ajman Government (Ruler’s Court)

Local Governments

• Ministry of Education

• Ministry of Economy

• Ministry of Labor

• General Authority of Youth & Sports Welfare

Federal Governments

•Business Excellence Only

•Technology Excellence Only













processes/information across business units









EA Benefits









upgrades/conversions





technology)







infrastructure requirements

























management



International EA Survey Findings



Key findings:

–

EA is emerging as a

strategic tool at the corporate level

•

EA playing an active role in strategic planning

•

EA playing role in the business transformation and

organizational development

•

In more cases EA reporting to non-IT functions (20%)

•

An important tool for Risk management & Business &

IT Governance

–

EA is becoming more

professional

through the use of

standardized, well-defined methods, processes and tools;

–

EA Governance, in particular its

marketing and

communications

approach,

needs to be improved

Objectives & Benefits of EA

45

Number of respondents

Adoption Of Frameworks (EA + IT)