enterprise architecture team discussion

8
“Enterprise Architecture – Implementation Discussion” Andrew Hall

Upload: andrew-hall

Post on 05-Aug-2015

26 views

Category:

Leadership & Management


0 download

TRANSCRIPT

Page 1: Enterprise architecture team discussion

“Enterprise Architecture – Implementation Discussion”

Andrew Hall

Page 2: Enterprise architecture team discussion

Introduction

‘A partnership of technology and business value that enables the optimum realisation of investment in systemic business intelligence’

2

Conceptual envelope of iterative processes• A blueprint/vision Enterprise Architecture reference model to

strategically, tactically and operationally reflect the stated business strategy

• Comparison of current Enterprise Architecture with stated future vision to identify areas requiring development and/or improvement

• Roadmap to define, plan whilst ensuring business continuity how the future Enterprise Architecture will be realised

Page 3: Enterprise architecture team discussion

3

Architecture

Business Architecture

Technical/ServiceArchitecture

Data Architecture

‘Information must flow within health organisations and across boundaries into social care, allowing vital data to follow patients through their care pathways’

NHS England, ‘Safer Hospitals Safer Wards: Achieving an Integrated Digital Care Record’ paper in July 2013.

Page 4: Enterprise architecture team discussion

4

Implementation

Business Layer

Technical Layer

Enterprise Layer Seed Bed

Implementation

Page 5: Enterprise architecture team discussion

Principles

5

Page 6: Enterprise architecture team discussion

6

Road Map

ProjectIdentification

DeconstructPreparationCapability

Assignment Sub-project

CapabilityCompletion Requirements

MessageHarness

MessagingDetermination

DependencyDetermination

DataArchitecture

TechnicalArchitecture

BusinessArchitecture

IntegrationImplement

Page 7: Enterprise architecture team discussion

Approach

Complex Adaptive / Systems A vision of a near or distant future and a strategic plan itself are not blueprints for a future state. Rather a statement to the business of the need for change and what can and should be achieved to enable the present to enable delivery of the vision.

Interaction Control• Response and Interpretation• Changing relationships• Co-evolution• System development &

recombination• No single point of control

7

PeopleRoles, Responsibilities,

Incentives, Passion

Best PracticeIT and Business

Collaboration

PeopleRoles, Responsibilities,

Incentives, Passion

Best PracticeIT and Business

Collaboration

ProcessesPractices, workflows,

data flows

Best PracticeTrusted information,

provenance

ProcessesPractices, workflows,

data flows

Best PracticeTrusted information,

provenance

TechnologyInteroperability,

Services Oriented Architecture (SOA),

data sharing, IG

Best PracticeEnterprise wide re-use

and standards

TechnologyInteroperability,

Services Oriented Architecture (SOA),

data sharing, IG

Best PracticeEnterprise wide re-use

and standards

PoliciesData standards and

business rules

Best PracticeData and Corporate

Governance

PoliciesData standards and

business rules

Best PracticeData and Corporate

Governance

Page 8: Enterprise architecture team discussion

Benefits

8

What EA offers The benefits

Alignment of business goals

with information architecture

Ensures the ROI of all

subsequent information projects

Faster access, across the

enterprise, to crucial dataImproved and more timely decision making

Common and shared data definitionsReduction in time spent debating

the meaning and purpose of data

elements

Improved data qualityAll enterprise operations run

more effectively

Impact analysis and data lineage

across a complete information

supply chain

Aids compliance to corporate and

governmental reporting

requirements