as enterprise architecture overview 2014 06-19

isieadvisieadv

A practical approach to Enterprise Architecture

Raoul Schuhmacher

Advisie Services

isieadv

Introduction

• Enterprise Architecture can be a valuable to tool for establishing a foundation for achieving the company’s goals

– by facilitating a dialog between the organizations and employees within the company, and

– by creating a common understanding about the company across the company’s organizations, employees, and partners

• This presentation describes the components that should be in place to accomplish the above.

8/7/2014 © Advisie Services, 2014 – All rights reserved 1

isieadv

What is Enterprise Architecture?


isieadv

Enterprise Architecture

• “A rigorous description of the structure of an enterprise, which comprise enterprise components (business entities) and the relationships (e.g. the behavior) between them:

• Describes the terminology, the composition of enterprise components, and their relationships with the external environment,

• Describes the guiding principles for the requirements, design, and evolution of an enterprise.

• This description is comprehensive, including enterprise goals, business process, roles, organizational structures, organizational behaviors, business information, software applications, and computer systems.”

(Source: Wikipedia)


http://en.wikipedia.org/wiki/Enterprise_architecture

isieadv


“big picture” framework for addressing the

standardization and integrationof a company’s

strategies, processes, people, and technologies

Infrastructure

Application Integration

Applications

Business Information

Business Processes

Business Strategies

Enterprise Architecture provides a long-term / big picture perspective



isieadv

Critical Success Factors

• Business alignment, clear business value proposition

• Support from majority of stakeholders

• Practical/pragmatic/iterative approach, with regular stream of value delivered

• Measurable value, e.g. adoption of architecture deliverables into SDLC processes as value-add vs. barrier

• Accountability, e.g. embedding enterprise architecture objectives in employee performance management

• Incentives, e.g. architecture job descriptions and career path

• Available funding to support an EA program


isieadv

Define Domain Roadmaps

Client Example: Approach to EA

DefineEA Framework

DefineEA Reference

Model

DefineEA Domains

Architecture Processes

Current State

Target State

Investment Plan

• Domain Architects

• Domain Owners

• Tech Stack• Standards• Policies

• Tech Stack• Standards• Policies

• Projects• Project Plan

Establish Architecture Governance Structure

• EA Steering Committee• EA Core Team• EA Community• Architecture Review Board (ARB)

• Architecture Development and Review Processes• Architecture Review Checklist• Communication and Education• Innovation

• Existing tech, standards, roadmaps


DefineEA Principles

isieadv

Principles


isieadv

Enterprise Architecture Principles

Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.

Architecture principles relate to architecture work and reflect a level of consensus across the company:

• They govern the architecture process, affecting the development, maintenance, and use of architecture.

• They define the underlying general rules and guidelines for the use and deployment of all IT resources and assets across the company.

Adopted from TOGAF 9.1


isieadv

Enterprise Architecture Principles

• Primacy of principles

• Maximize the benefit for the enterprise

• Information management is everyone’s business

• Business continuity

• Common use applications

• Service orientation

• Data is an asset

• Data is shared

• Data is accessible

• Data trustee

• Common vocabulary and definitions

• Data security

Adopted from TOGAF 9.1

Business

• Technology independence

• Ease of use and availability

Applications

• Requirements based change

• Responsive change management

• Control technical diversity

• Interoperability

TechnologyData


isieadv

Framework


isieadv

Enterprise Architecture Framework

The Enterprise Architecture Framework creates a high level representation of the company, and shows the products and services the company develops and markets as a combination of components and capabilities from Business, Data, and Technology to enable business goals and priorities.

Business goals, and operating model of the company decide which components of the architecture to integrate for differentiation, and which to standardize for efficiency,


isieadv

Client EA Framework

Business

Architecture

Information

Architecture

Technology

Architecture

Business Priorities

Solution / Service

Architectures

Envir

onm

enta

l T

rends

Solution / Service

Architectures

Solution / Service

Architectures

Enterprise Vision, Mission

Business Strategies


isieadv

Client Reference Model

BusinessProcesses

Business Goals& Strategies

BusinessInformation

EnterpriseApplications

EnterpriseIntegration

EnterpriseInfrastructure

GameLifecycle

(GLM)

Customer RelationshipMgt (CRM)

Order toCash (O2C)

Plan toFulfill (P2F)

Hire toRetire (H2R)

Plan toReport (P2R)

Procureto Pay (P2P)

BusinessIntelligence

(BI)

COA Products Customers People Vendors Contracts

Studio,GLM

CRM

O2C

P2F

H2R

P2R

P2P

BI

Serv

ice

Man

agem

ent

& M

on

ito

rin

g

Web Portals(B2E, B2B, B2C)

ApplicationIntegration

(B2B, EAI, ETL, SOA)

Goals Priorities Strategies

Computing Storage Database

Network Voice

Mobility

Business ProcessIntegration

(BPM, BAM, BPA)

Security &

Risk M

anagem

ent

GOPlatform

Data Integration(Meta Data, Data

Quality, DW, MDM )

VideoCollaboration,

Messaging

KPIs

UCC

Cloud (Virtualization)

DirectoryServices


isieadv

Operating Model - Process


isieadv

PLAN BUILD RUN

Architecture in the SDLC

Collect & manage demand High-level solutioning Kick-Off project

Advise on overall technology strategy on incoming demand (capability, capacity)

Advise Business IT, Service Management, and Service Delivery on overall technology analysis and solution architecture

Participate in project kick-off

PLAN BUILD RUN

Plan projects Execute projects Track status

Provide inputs to detailed estimation and planning process, ensure that architecture activities are included in plan

• Provide architecture stewardship (business process, information, and technology)

• Maintain and enforce architecture principles and technology standards

• Provide approval during phase gate reviews• Respond to architecture-related issues and

escalations

PLAN BUILD RUN

Support services Performance management Enhance services

No involvement No involvement • Work with Service Line Operations, Business IT, and Service Management teams to identify architecture improvements (e.g. quarterly MIR reviews)

• Monitor alignment of application and infrastructure architectures, and pro-actively suggest enhancements as needed


isieadv

Architecture in Phase GatesPlanning Initiation Analysis & Definition Design

• Aligned to business capability roadmap

• Assessed against IT capacity and capability

• High level conceptual solution architecture

• Aligned to solutions roadmap• Scope defined,

communicated, agreed• Project charter in place and

signed off

• Requirements document and signed off

• Architecture documented, reviewed and signed off

• Architecture diagrams updated, and in place, reviewed and signed off

• Integration dependencies known and coordination in place

Development Test Deployment Stabilization

• Adherence to development principles and standards

• IT system, integration, and performance tests complete and signed off

• UAT complete and signed off

• Go-live readiness checklist in place

• Detailed deployment plan in place

• Final support plan published, including SLA metrics, communication and escalation plans

• Updated architecture documentation


isieadv

Structure


isieadv

Architecture Governance

Executive Steering Committee

EA Steering Committee

ITFunctionsR&D

ARB (Chair: rotating)

• Open to all • Open to all • Open to all

• Develop and own standards and policies• Review proposed investments• Manage issue resolution• Foster innovation

• Provide business and technology direction• Ratify standards, and policies• Resolve issues• Own roadmap

• Provide business direction• Monitor roadmap

• Participate in standards and policies development

• Provide insights into technologies, best practices

EA Team (Enterprise Architects, Lab/R&D) • Program Management, Facilitation, Education

EA C

om

mu

nit

yEA

Co

re T

eam

/ A

RB

• Architecture reviews, decisions


isieadv

Metrics


isieadv

Client Metrics: Business BenefitThe metrics below measure the effectiveness of the architecture content itself. They measure reduction in time and money spent in the design phase of change projects, and the reduction in total number of technologies supported in the environment.

Objective Metric Cycle Information Required Process to Collect

Speed to market:Reduce effort and cost by end of year 1

Time / resource effort for solution design

Quarterly Design phase resource and time-scale actuals PMO to collect, EA Core Team to report to EA-SC and Executive SC

Reduce IT run cost by reducing # of applications and associated infrastructure

# of applications (application roadmap)

Quarterly Application inventory and roadmap (application retirement schedule) and infrastructure support cost, maintenance cost

EA Core Team to report to EA-SC, and Executive-SC

Reduction in IT run cost for maintenance, licenses

Number of supported technologies

Quarterly Number of technologies supported by domain EA Core Team to collect, EA-SC to present to Executive-SC

Standardization of Information Architecture

# of services / processes using standard BI capabilities

Quarterly Maintained information architecture, aligned to service/tool catalog and BI Roadmap

EA Core Team to collect, EA-SC to present to the Executive SC

Maintenance/ Relevance of Business Architecture

Adherence to design phase gates

Quarterly # of projects adhering to phase gates for design

(Dependent on Business Architecture

maintenance being embedded in SDLC)

GPMO to collect, EA Core Team to report to EA-SC and Executive SC

Reduction of post-implementation run cost

Run cost / department

Quarterly Need to understand run cost and cost reduction as result of standardizing processes, technologies, etc

TBD


isieadv

Client Metrics: Effectiveness


90% by end of year 1

% domains *) governed by EA

Quarterly Total # of domains and # of domains excepted from Enterprise Architecture governance – differentiate strategic vs. tactical

EA Core Team to report to EA-SC, and Executive SC


% of invest projects governed by EA

Quarterly Total # of invest projects (and $) and # of invest projects (and $) excepted from EA governance



% of staff with architecture objectives

Quarterly Ensure appropriate performance objectives in place


95% by end of year

% of IT staff who have received Enterprise Architecture training

Quarterly Total # of IT staff and trained in Enterprise Architecture


8/7/2014

The most important issue for Enterprise Architecture effectiveness is its impact on the organization as a whole. The metrics defined below show the percentage of domains governed by the Enterprise Architecture, the percentage of change projects governed by the Enterprise Architecture, and the percentage of key staff who have received Enterprise Architecture training.


isieadv

Client Metrics: EA PerformanceThe metrics defined below show performance in the work of creation and refresh of the Enterprise Architecture, impact of the Enterprise Architecture assurance process on change initiatives, and the percentage of changes receiving exceptions to the Enterprise Architecture.


Creation in year 1, and refresh annually

Enterprise Architecture create/refresh

Annually Enterprise Architecture documentation (leverage work that is going on in the domains, create a single repository/portal, create application inventory, have process triggers to ensure documentation is refreshed)

Responsibility of EA Core Team to prepare for presentation to the EA-SC, and Executive-SC

Assurance turn time less than two weeks

Architecture project assurance process cycle time (EA-SC)

Quarterly EA Core Team, and EA-SC scheduling request date, schedule date

Responsibility of EAS Core Team to prepare for presentation to the EA-SC, and Executive-SC. Dependency and input from PMO

80% approval, 20% exceptions by end of year 1

Number of exceptions granted

Quarterly EA Core Team, EA-SC exceptions Responsibility of EAS Core Team, to prepare for presentation to the EA-SC, and Executive-SC


isieadv

Roadmaps


isieadv

Technology Roadmap

The Enterprise Architecture Reference Model defines the business process, data, and technology layers within the Enterprise Architecture framework. A layer consists of multiple domains, each domain must identify

• Current state (what we have, i.e. asset inventory)

• Future state (what we want to have, i.e. target architecture)

• Roadmap (how we get there, i.e. transformational projects)

• Constraints (things we cannot change and must avoid)

Domain roadmaps will inform and in turn be influenced by business priorities to achieve an overall capability roadmap for the company.


isieadv

Client Example: Roadmap Scope

• Network • Compute• Storage• Database (RDMS)• NoSQL• Mobility• Directory Services• Operating Systems• Remote Access• End-user compute• Voice• Video• Collaboration, Messaging

• Engineering Productivity Management

• Application Containers• User authentication, authorization• Parallel computing• Application integration• User interface/User experience• Data management

• Client Solutions• E-Mails and SMS/MSS Distribution• Workforce productivity• Enterprise Applications

Applications

Service Management & Monitoring

Security & Risk Management

Application Infrastructure

Infrastructure


isieadv

Example Deliverables


isieadv

Deliverable: Application Inventory

• Approach• Utilize existing efforts to capture/collect current application inventory and continue to expand/augment

• Attributes:• Application; Description; L0,1,2 Business process; Region; Architecture Domain; Business owner, IT owner, EA

owner, Status (Go Forward, Replace), Vendor, Product, Integration


isieadv

Deliverable: Technology Standards

• Approach• Consolidate vendor/technology inventory and create a common repository• Name technology and executive owners for all technologies

• Attributes:• Architecture Domain; Technology Category; EA Owner; Vendor, Product, EA Status (In production, Sunset, Evaluation),

Version, License Agreement, EA Preference (Preferred, Approved, Prohibited)


isieadv

Deliverable: Community

•Approach• Setting up and moderating/maintaining EA Community site and/or Architecture Portal


isieadv

Deliverable: Maturity AssessmentConsider performing a maturity assessment to baseline the organization and capability, perform annual refresh to determine process in gaining maturity


isieadv

Conclusions


isieadv

Conclusions

• Enterprise Architecture can be a valuable tool to facilitate a dialog in the company for creating a common understanding about the company’s goals and structure, and thereby creating the foundation for business success.

• The components reviewed in this presentation are necessary, however, change management combined with measurable value are the most important ingredients for success.

• An approach to Enterprise Architecture should be chosen based on the culture of the company


isieadv

Advisie Services

• Provides advisory and delivery services across the Information Technology life cycle, using a network approach to match the best skills to clients’ requirements and provide the leadership to ensure successful outcomes.

• Has helped companies successfully establish Enterprise Architecture programs and functions.

• For more information, please contact Raoul Schuhmacher at [email protected]


isieadvisieadv

Thank you

as enterprise architecture overview 2014 06-19

Leadership & Management

architecture work

enterprise goals

business goals

isieadv principles

architecture job descriptions

ea principles

isieadv framework

ea program