ea landscape capabilities summary slides 2009 share
DESCRIPTION
These 15 EA Landscape Slides represent a Summary View of many other Briefings over the last decadeTRANSCRIPT
Achieving Competitive Advantage & Success Through The Corporate Blueprint
Realizing The Enterprise of The Future – Today!!!™
“Maintaining Global Standards while allowing for Local Differences.“
- SB; 2003
Copyright Boettger 2002 to present
Integrated Enterprise Architecture Capabilities EVAL
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Aligning Corporate Strategy & Goals
Aligned
Enterprise
Business
Architecture
Frameworks and methodology for
defining and improving value streams,
processes, sub-processes and activities
Metrics are tied to each layer.
Best Practices Tied to Each Specific Sub-
process or activity
BUSINESS
STRATEGY
Goals, Products,
Customers
IT
Applications
& IT InfrastructureSpecific ApplicationsIT Infrastructure Options
Organization of Value Chains and Lines of Business
given priorities through Priority Dimensions
Adapted by Boettger 2007 to present
Enterprise Architecture Landscape Capabilities Framework
Capability Portfolio MgmtProject AlignmentCapability AssessmentInitiative SynchronizationServices AssessmentCapital PlanningInvestment ManagementCapacity Analysis…
Enterprise SourceControl
(Single View)
Indexing
Intranet Enterprise Data Stores(including EDW Capability)
S/W, H
/W D
eve
lop
me
nt
Res
ult
s fr
om
P
lan
nin
g, P
erfo
rman
ce, M
arke
t, R
isk,
Req
uir
emen
ts, e
tal A
nal
yse
s
•Relationship Visibility & Traceability
•Easily Realized Alignment to any desired depthFull Traceability of Impact, Cause & Effect
Custom Queries of Configurations
•Planning Foundation for Innovation, Re-engineering…
Opportunities Analysis
•Object Oriented Management & Control
•Extensive OOTB Reporting (See Samples)Responsive to Real Business Questions
•Extensible Custom Reporting
•Predictive Analysis for Strategic Planning, etc.
•Full Integration of PPM, CMDB Capabilities
•Object Oriented Database Underpinning for EA•Management, Control, Design, Object Exploitation
•…
EA Business Driven Capability
Enterprise Architecture Models & Data
•Shared Access, •Shared Browse, •Managed Control•Reports Distribution•Dashboard Results •Real-time Asset Visibility•…
•Collaboration•Content Access•Search Capability•Report Generation•Request Mgmt•…
Business & IT
Reports, Dashboards, et al
Copyright Boettger 2002 to 2008 (except as noted)
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Business Driven Integration enabled by applying behavioralFactors (pyramid) to the Enterprise Planning Reference Model (cube)
Factors: Behavioral Dimensions to consider:
1. Business Function (up and down the functional and organizational chart, silos)
2. Cross Functional (within and across units)
Shared, common, core processes
3. Members and External Entities (suppliers, vendors) Point of View
Impact of Enterprise actions on customer satisfaction, service and relationships
4. Time to Market
Delivering new products and services to the market, to the customer
The Goal - Architect the relationships of interrelated parts
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Value of Reference Models•Define & Reconcile Capability Processes
•Clarifies our Value Chains (Competitive Advantage)
•Reveals Gaps in Enterprise Core Competencies
•Identifies gaps in Value Streams (Solution Candidates)
•Encourages true alignment between Business & IT
•Ensures versioning and configuration control of the IEA ‘known space’
•Ensures Integrity in support of the strategy and tactics responding to the Vision, Mission, Objectives, et al
•Baselines for Change/Innovation Impacts
Measure, Measure, Measure
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Copyright Boettger 2002 to present
Business & IT Transformation Ecosystem
Plan the Business
Run the Business
Strategic
Information
Operational
Information
Excellence in
IT Operations
BP
Management
BP
Analytics
Portfolio Management
ITSM
ALM & SOA Governance
Primary
Activities
Support
Activities
Value Chains & Value Streams
Copyright Boettger 2002 to present
Business & IT
Transformations
Toward Differentiation
Copyright Boettger 2002 to present
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
EBA & Zachman
BUSINESS
SCOPE
BUSINESS
MODEL
INFORMATION
SYSTEMS
MODEL
TECHNOLOGY
MODEL
TECHNOLOGY
DEFINITION
INFORMATION
SYSTEM
List of things important to the
business.
ENTITY:
class of business thing
List of processes the business
performs
PROCESS:
class of business processes.
List of locations in which the
business operates
NODE: business location.
DATA PROCESS LOCATION
Business entities & their inter-
relationships
Flows between business processes Communications links between
locations
ENTITY: business entity
REL'SHIP: business rule
PROCESS: business process
I/O: business resource
(including information)
NODE: business unit
LINK: business relationship
(org., product, information)Model of the business data
and inter-relationships
Flows between application functions Distribution network
ENTITY: data entity
RELTNSHIP: data relationship
NODE: I.S. function (processor,
storage, etc.).
LINK: line characteristicsDatabase Design System Design System Architecture
ENTITY: segment, row, record
RELTNSHP: pointer, key, index
Database Schema and
Subschema Definition
Program Code and Control Blocks Configuration Definition
ENTITY: fields, access privledge
RELTNSHP: access methods,
addresses Data Storage Structures and
Access Mechanisms
Databases, data .....
Executable Code
Programs, jobs,
transactions.....
System Configuration
Processors, networks,
switches. monitors.....
Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987.
PROCESS: application function
I/O: user views (set of data
elements).
PROCESS: computer function
I/O: screen/device formats
NODE: hardware/system software
LINK: line specifications
PROCESS: source code
I/O: control blocks
NODE: addresses
LINK: protocols
List of business responsibilities.
RESP.: class of business responsibilities
List of business events.
EVENT: class of significant business
events.
List of business goals.
ENDS: mission(s)/goal(s).
ROLE TIMING MOTIVATION
Business Organization. Business Cycles. Business Strategies
RESP: work unit/structure
WORK: business resources
EVENT: business event
CYCLE: lapse/lag
ENDS: goal(s)/mission(s)
MEANS: tactics/plans
Model of the access requirements. Model of the process control
structure.
Service Support Environment
RESP: system privilege
WORK: access requirements
Access Design Processing Environment Availability Design
RESP: access authorizations
WORK: access group
Access Definition Job Processing Definition Performance Definition
RESP: access object
WORK: access profiles
Access Privileges
User-id’s, access controls
.....
Processing Schedules
Batch jobs, transactions,
run/rerun instructions .....
System Management Facilities
Monitoring facilities, problem
management .....
EVENT: logical process event
CYCLE: precedence/timing
EVENT: physical process event
CYCLE: processing calendar
ENDS: benchmark models
MEANS: availability of windows
and measures
EVENT: transactions, job submittal
CYCLE: job & region schedules
ENDS: benchmark targets
MEANS: benchmark testing, system
monitoring/tuning
BUSINESS
SCOPE
BUSINESS
MODEL
INFORMATION
SYSTEMS
MODEL
TECHNOLOGY
MODEL
TECHNOLOGY
DEFINITION
INFORMATION
SYSTEM
ENDS: service level agreements
MEANS: I/S plans & change tactics
----------------------
.. . ..
.
Mainf rame
IBM AS/400
IBM Compatible
EBA
Modified by Boettger 2008
EBA/VCOR Overlay with Zachman
BUSINESS
SCOPE
BUSINESS
MODEL
INFORMATION
SYSTEMS
MODEL
TECHNOLOGY
MODEL
TECHNOLOGY
DEFINITION
INFORMATION
SYSTEM
List of things important to the
business.
ENTITY:
class of business thing
List of processes the business
performs
PROCESS:
class of business processes.
List of locations in which the
business operates
NODE: business location.
DATA PROCESS LOCATION
Business entities & their inter-
relationships
Flows between business processes Communications links between
locations
ENTITY: business entity
REL'SHIP: business rule
PROCESS: business process
I/O: business resource
(including information)
NODE: business unit
LINK: business relationship
(org., product, information)Model of the business data
and inter-relationshipsFlows between application
functions
Distribution network
ENTITY: data entity
RELTNSHIP: data relationship
NODE: I.S. function (processor,
storage, etc.).
LINK: line characteristicsDatabase Design System Design System Architecture
ENTITY: segment, row, record
RELTNSHP: pointer, key, index Database Schema and
Subschema Definition
Program Code and Control Blocks Configuration Definition
ENTITY: fields, access privledge
RELTNSHP: access methods,
addresses Data Storage Structures and
Access Mechanisms
Databases, data .....
Executable Code
Programs, jobs,
transactions.....
System Configuration
Processors, networks,
switches. monitors.....
Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987.
PROCESS: application function
I/O: user views (set of data
elements).
PROCESS: computer function
I/O: screen/device formats
NODE: hardware/system software
LINK: line specifications
PROCESS: source code
I/O: control blocks
NODE: addresses
LINK: protocols
List of business responsibilities.
RESP.: class of business responsibilities
List of business events.
EVENT: class of significant business
events.
List of business goals.
ENDS: mission(s)/goal(s).
ROLE TIMING MOTIVATION
Business Organization. Business Cycles. Business Strategies
RESP: work unit/structure
WORK: business resources
EVENT: business event
CYCLE: lapse/lag
ENDS: goal(s)/mission(s)
MEANS: tactics/plans
Model of the access requirements. Model of the process control
structure.
Service Support Environment
RESP: system privilege
WORK: access requirementsAccess Design Processing Environment Availability Design
RESP: access authorizations
WORK: access group Access Definition Job Processing Definition Performance Definition
RESP: access object
WORK: access profiles
Access Privileges
User-id’s, access controls
.....
Processing Schedules
Batch jobs, transactions,
run/rerun instructions .....
System Management Facilities
Monitoring facilities, problem
management .....
EVENT: logical process event
CYCLE: precedence/timing
EVENT: physical process event
CYCLE: processing calendar
ENDS: benchmark models
MEANS: availability of windows
and measures
EVENT: transactions, job submittal
CYCLE: job & region schedules
ENDS: benchmark targets
MEANS: benchmark testing, system
monitoring/tuning
BUSINESS
SCOPE
BUSINESS
MODEL
INFORMATION
SYSTEMS
MODEL
TECHNOLOGY
MODEL
TECHNOLOGY
DEFINITION
INFORMATION
SYSTEM
ENDS: service level agreements
MEANS: I/S plans & change tactics
----------------------
.. . ..
.
Mainf rame
IBM AS/400
IBM Compatible
EBA
VCOR
Modified by Boettger 2008
Business Driven Domain Stack
Value Stream Architectures, Operational Business Use Case, & Workflow References
Value Chain References
Strategy
Referential, Supportive, & Component Behavior Artifacts
IT & Infrastructure Landscape
Projects Landscape
Core Architectures: Inter-related Referential Architectures
Enterprise Business Architecture
Business Area Architecture Structure
Potential Industry Specific Business Domain (s)
Potential Industry Specific Technical Domain (s)
Copyright Boettger 2002 to present
Copyright Boettger 2002 to present
Enterprise Architecture is Iterative
Adapted by Boettger 2007 to present
Holistic Approach – Common Sense Steps
Instill Learning Circle PracticesAdapted by Boettger 2007 to present
Integrated EA Reference ModelsSteps to Get There
1. Identification and Confirmation of Enterprise Asset Capabilities
2. Identify/Clarify Value Chains, Map Core Processes to the Enterprise Asset Capabilities
3. Create Solution Candidates (Value Streams) supporting Value Chains, thereby identifying Core Processes, Common
Processes, and Shared Services
4. Create Current and Future Behavior Models
a. Enterprise Business Architecture; Business Capability Models, as well as a Meta Model of the Business
b. Create Reference Model Set
5. Iterate and Reconcile Asset Capabilities to Reference Models
6. Evaluate Strategic Prioritization Regarding Needed Business Capability(ies)
7. Evaluate and Build Plans Reflecting Prioritization
8. Build Capability(ies) From Reconciled Results Per Prioritization
a. Solution Scenario Sets (Candidate Value Streams)
9. Generate Use Cases working with IT
10. Generate IT Workflows that reflect #8 and #9
Result: Realize a „known solution space‟ that is Accountable, Measurable, Reconcilable, Most Importantly Credible
Note: Frameworks are not meant to be “templates”, but rather prescriptive guides
Copyright Boettger 2002 to present
Copyright Boettger 1999 to present
STRATEGY
Business Driven DesignProcess, Organizational, Security, Technology Architectures
Operational Excellencee.g.; workflows supporting Core Processes, etc.
CompetitiveAdvantageValue Chain(s)
Customer Centric FocusValue Streams
Leadership develops and directs the Strategy
through Vision, Mission, and Goals
Designs, Builds and Integrates the Value Streams
of the Enterprise and align with the Strategy
Engineers and Maps Enterprise Value Chains
to the Strategy, deciding on Competitive
Differentiation Initiatives
Enabling Core Architectures
Infrastructure
Designs and Builds Architectures
to support Business Strategic Initiatives
Optimization for
Effectiveness and Efficiency
Enabling Business Driven Excellence
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Thank you…•Operational Excellence
•Member/Customer Service•Better Decision Making
•Optimum Value