Team discussion - Implementing Enterprise Architecture - Basic concepts / principles / approach / change

1. “Enterprise Architecture –
Implementation Discussion”
Andrew Hall

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

3. Architecture
3
Business Architecture
Technical/Service
Architecture
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.

4. Implementation
4
Business
Layer
Technical
Layer
Enterprise
Layer Seed Bed
Implementation

5. Principles
5

6. Road Map
6
Project
Identification
DeconstructPreparation
Capability
Assignment Sub-project
Capability
Completion
Requirements
Message
Harness
Messaging
Determination
Dependency
Determination
Data
Architecture
Technical
Architecture
Business
Architecture
IntegrationImplement

7. 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
People
Roles, Responsibilities,
Incentives, Passion
Best Practice
IT and Business
Collaboration
Processes
Practices, workflows,
data flows
Best Practice
Trusted information,
provenance
Technology
Interoperability,
Services Oriented
Architecture (SOA),
data sharing, IG
Best Practice
Enterprise wide re-use
and standards
Policies
Data standards and
business rules
Best Practice
Data and Corporate
Governance

8. 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 data
Improved and more timely decision
making
Common and shared data definitions
Reduction in time spent debating
the meaning and purpose of data
elements
Improved data quality
All enterprise operations run
more effectively
Impact analysis and data lineage
across a complete information
supply chain
Aids compliance to corporate and
governmental reporting
requirements