Take the “EA” Way?

Download Report

Transcript Take the “EA” Way?

“EA is still the Way”
Rob Thomas II
DoD and Federal - Certified Enterprise Architect (CEA)
8 Dec 11
Copyright © 2011 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.
Take the “EA” Way?
Take a guess on your way?
or
Manage this through EA?
Applications
Legacy
Systems
ERPs
Cloud or
Hosted
Managed
Services
Legacy
Systems
What is your choice?
Copyright © 2011 Accenture All Rights Reserved.
2
Enterprise architecture discipline
for high performance
Any organization can achieve new successes with enterprise
architecture discipline.
1
2
3
Determine
scope of
architecture
Determine
characteristics
to be captured
Copyright © 2011 Accenture All Rights Reserved.
Determine
the intended
use of the
architecture
4
Determine
views and
products
to be built
5
Build the
requisite
products
6
Use
architecture
for intended
purpose
3
The journey to mission success
Focus on
Enterprise
Architecture
Understand
the Current
State
Develop a
Strategy
Enhance
Implementation
Sustain
Discipline
Mission
Success
1. Hiring and Finding Qualified Personnel is the largest Impediment to EA success.
2. Qualified and Certified Personnel is the single most important item to EA success.
Copyright © 2011 Accenture All Rights Reserved.
4
Defining enterprise architecture
Enterprise architectures help organizations define where they are
today—and where they plan to go tomorrow.
Baseline
Transition
Target
• Describes the current
state of the environment
• Business improvement
efforts
• Describes a planning state
of the environment
• Presents the “as-is”
picture
• Technology migration
strategies
• Presents a “to-be” picture
• Project development
initiatives
• Several targets may be
developed to phase
planning horizons over
several years
• Deployment plans
Copyright © 2011 Accenture All Rights Reserved.
5
Enterprise Architecture in Federal
The Federal Enterprise Architecture Framework (FEA)
FEA Framework
 Performance RM
 Business RM
 Systems RM
 Data RM
 Technology RM
Source: http://en.wikipedia.org/wiki/Federal_Enterprise_Architecture_Framework
Copyright © 2011 Accenture All Rights Reserved.
6
Federal Reference Models
Copyright © 2011 Accenture All Rights Reserved.
7
Enterprise Architecture in Defense
The Department of Defense Architecture Framework (DoDAF)
Capability/Operational Viewpoint
Identifies Warfighter Relationships
and Information Needs
Processing and
Inter-Nodal Levels of
Information Exchange
Requirements
Systems
Associations to
Nodes, Activities,
Needlines and
Requirements
Systems/Services
Viewpoint
Relates Capabilities and
Characteristics to
Operational Requirements
Copyright © 2011 Accenture All Rights Reserved.
Basic Technology
Supportability and
New Capabilities
Specific Capabilities Identified
to Satisfy InformationExchange Levels and Other
Operational Requirements
Processing and
Levels of Information
Exchange Requirements
Standards Viewpont
Prescribes Standards
and Conventions
Technical Criteria Governing
Interoperable Implementation/
Procurement of the Selected
System Capabilities
8
Enterprise Architecture in Defense
Copyright © 2011 Accenture All Rights Reserved.
9
Enterprise Architecture in Defense
Copyright © 2011 Accenture All Rights Reserved.
10
Challenges to success
IT Budget
Investment in a comprehensive
enterprise architecture
Reactive, non-discretionary
spending/maintenance of existing
systems
Copyright © 2011 Accenture All Rights Reserved.
11
Making a strategic investment in
enterprise architecture
Enterprise architecture works to confirm that the reality of the implemented
enterprise is aligned with management’s strategic plan intent.
Get a total technology and business picture for better decisions.
• Evaluate and compare domain architecture consistently
• Reduce overlap, conflicts and duplication
• Remove IT complexity and shrink the core
• Help increase IT return on investment
• Help increase the use of emerging technologies
• Verify system compliance with requirements as reflected in the EA
• Enable cross-department, cross-agency collaboration
• Promote communication among stakeholders
• Manage change faster with flexibility and scalability
• Take advantage of opportunities for increased efficiency
Copyright © 2011 Accenture All Rights Reserved.
12
Making a strategic investment in
enterprise architecture
Benefits
Definition
Example Drivers
Cost Displacement One time investment in one area • Promote self-service
to shave ongoing costs in another
Tangible
Direct
Benefits
(10-30% cost
reduction)
Cost Reduction
Intangible
Inferred
Benefits
• Standardize Platform
• Optimize sourcing
• Redesign Help Desk
• Implement business-driven
reporting tools
• Consolidate servers, data centers,
networks
• Outsource commodity functions
• Replace software to lower
maintenance
• Implement EAI
Same benefits advantages
reached at lower risk
• Improve system availability
• Implement redundant servers
• Improve security
• Implement common security
services
Shorten time-tomarket
Reduce cycle time from
production conception to roll-out
• Use Architecture Patterns
• Standardize on SOA
• Configurable architecture
components
• Implement Rules Engine
Earlier Benefit
Realization
Compress the timeframe at which • Rationalize IT procurement
the benefit stream will start
Productivity Gain
Improved employee productivity,
i.e., output per FTE
Cost Avoidance
Indirect
Benefits
(10-50% cost
reduction)
Cost per output unit decreases
over time
Example IT Initiatives
Risk Reduction
Opportunity costs are avoided
Copyright © 2011 Accenture All Rights Reserved.
• Migrate to newer packages
• Reduce number of IT vendors
• Productivity toolkits
• Implement collaboration engine
• Consolidate info stores
• Implement portals
13
Different circumstances mean different
approaches
Top Down
•The top-down approach: Starts at the top, assumes a comprehensive
scope across most or all of the organization, creates high-level frameworks
and architectures and decomposes those to lower levels of detail. It follows a
rigorous, agreed-upon process.
•Most relevant when: The organization needs to address significant
duplication or inefficiencies in overall business capabilities.
Capability
Driven
•The capability-driven approach: Often the deficiencies of the enterprise
architecture become apparent during a major capability improvement. In the
capability-driven approach, part of the EA is redesigned for the new capability.
•Most relevant when: The organization is largely focused on a major
implementation.
•The bottom-up approach: This approach starts with initiatives like
infrastructure standardization/consolidation and then moves upward to higherpriority areas.
Bottom Up
•Most relevant when: The organization needs bottom-line savings quickly or
when there are significant service delivery quality issues.
Copyright © 2011 Accenture All Rights Reserved.
14
The public service environment beyond
compliance
Enterprise architecture success = Mission success
Enterprise architecture can help a public service organization to address:
• The rising cost of government services coupled with limited personnel resources
• The pressing need to help increase technology ROI in a difficult economy
• The environment of change associated with new administration
• The move toward improved citizen service and a single view of the customer
• The role of enhanced data gathering, analysis and storage for total battlefield
awareness
Copyright © 2011 Accenture All Rights Reserved.
15
Understanding the current state
What do we do to initiate an enterprise architecture program?
•
•
•
•
•
•
Obtain stakeholder buy-in
Define an architecture policy
Establish roles and responsibilities
Secure a commercial collaborator
Establish a program management office
Collect information and conduct gap analysis
1. Hiring and Finding Qualified Personnel is the largest Impediment to EA success.
2. Qualified and Certified Personnel is the single most important item to EA success.
Copyright © 2011 Accenture All Rights Reserved.
16
Developing a customized strategy
How do we determine the right approach for our organization?
•
•
•
•
Define the use, scope and depth of the architecture
Select enterprise architecture products
Choose an appropriate framework
Decide on an enterprise architecture toolset
1. Hiring and Finding Qualified Personnel is the largest Impediment to EA success.
2. Qualified and Certified Personnel is the single most important item to EA success.
Copyright © 2011 Accenture All Rights Reserved.
17
Optimizing implementation and delivery
How do we move from strategy to results?
•
•
•
•
•
•
Build baseline and target architectures
Review and refine architectures
Develop and finalize sequencing plan
Understand the role of legacy, migration and new systems
Plan for an incremental migration
Solicit approvals and share with stakeholders
Copyright © 2011 Accenture All Rights Reserved.
18
Sustaining enterprise architecture discipline
What do we do to help confirm long-term success and high
performance in an enterprise architecture program?
•
•
•
•
•
•
•
Remember that enterprise architecture is an iterative process
Continue to leverage assistance from commercial teammates
Make training a priority
Put enforcement and governance procedures into place
Commit to periodic reviews
Plan for follow-on improvements
Insert enterprise architecture into the business and technology decision process
Copyright © 2011 Accenture All Rights Reserved.
19
Getting results with enterprise architecture
U.S. Customs Service Enterprise Architecture
Department of Homeland Security
U.S. Customs Service
USCS Strategic Plan
Trade
DSAM EA Framework
OIT Strategic Plan
Outbound
Passenger
Finance
Enforcement
HRM
Views/Levels
Functional
Informational
Organizational
Infrastructure
USCS Repository
Clinger-Cohen
Act
Baseline (“As Is”)
Applications
Architecture
Data
Architecture
Target (“To Be”)
Network
Architecture
Security
Architecture
Other
Architectures
Technical Reference Model
• Principles
• Guidelines
• Core Competencies
•
•
•
•
•
•
Services
Domains
Sub-Domains
Product Portfolios
Components
Platforms
Technology Foundation Domains
Middleware
Operating
Systems
Copyright © 2011 Accenture All Rights Reserved.
Database
Personal
Technologies Productivity
Infrastructure Email/
Management Messaging
Application
Development
Environment
Security
Network
Technologies Infrastructure
20
Did we Derive value from F2T2EA and C4ISR
Enterprise Architecture?
Copyright © 2009 Accenture All Rights Reserved.
21
U.S. Air Force HRM Enterprise Architecture:
Burning Platform - Transformation
Air Force Personnel Center
• HRM Transformation =
Personnel Services
Delivery Transformation
...Boundless Future
Copyright © 2011 Accenture All Rights Reserved.
22
U.S. Air Force HRM Enterprise Architecture:
Air Force HRM Foundation
•
•
•
•
•
•
•
•
•
•
•
President’s Agenda
Defense Guidance
AF Strategic Plan
AF Core Competencies
AF Distinctive Capabilities
Vision
Goals
Objectives
Initiatives
Performance Measures
Air Force Manpower, Personnel and Services Strategic Plan
Copyright © 2011 Accenture All Rights Reserved.
23
U.S. Air Force HRM Enterprise Architecture:
HRM Mission
Develop our Nation’s Airmen
• Right People
• Right Place
• Right Time
•
•
•
•
•
Air Force HRM Goals
Define
Shape
Develop
Sustain
Deliver
Execution
• Commander’s Intent, Concept of Operations and Capabilities
Copyright © 2011 Accenture All Rights Reserved.
24
U.S. Air Force HRM Enterprise Architecture:
CONOPS and MCL Capabilities
ACS: Does not CrossReference MCL 4, MCL 6
ACS: All Capabilities are
considered Functional
MCL 7, ACS, OS: Do not
fully cover “Recover” for
Full-Scale Nation-Building
ACS CONOPS
Master
Capability
Library
MCL 1:
Surveillance
&Reconnaissance
MCL 2:
Intelligence
MCL 3:
Command
& Control
MCL 4:
Communications
MCL 2+:
Business
Intelligence
MCL, ACS: Mission,
Business Intelligence
MCL 5:
Force
Application
MCL 6:
Force
Projection
MCL 7:
Protect
MCL 8:
Prepare &
Sustain
OS CONOPS
OS: All Capabilities are
considered Multi-Functional
Copyright © 2011 Accenture All Rights Reserved.
OS: Emphasis on Information
and Command & Control
MCL 9:
Create the
Force
MCL 9+:
Shape the
Force
MCL 9, ACS:
Miss:
Shape the Force
Fund the Force
•
•
•
•
Long-Range Planning:
Shape Personnel
Shape Materiel
Shape Installations
Shape Science &
Technology
•
•
•
Fiscal Aspects:
Finance the Fight
Account to the Public
Synchronize
w/Congress & DoD
Legend:
MCL Only:
ACS CONOPS:
OS CONOPS:
Required but omitted:
25
U.S. Air Force HRM Enterprise Architecture:
AV-1 Personnel Service Delivery
Airmen
1.2 million
Self-Service
Contact Center
Base Front Line
Web and Interactive Voice
Response
Phone, E-mail, Fax,
and Mail
Face-to-Face
24/7 web-based
Capability
All HRM Actions
Centralize Processes
and Reduce MPF
70%
20%
Small footprint & advocate for
customer
10%
Individual Customer Service
Copyright © 2011 Accenture All Rights Reserved.
26
U.S. Air Force HRM Enterprise Architecture:
Air Force Military Personnel OV
AETC
DFAS
Education &
Training
OV-1 MilPDS
As-Is (OV-01 High level Op.
Concept)
System Architect
Mon Jul 03, 2006 09:28
AFPC Military Personnel
Retirement &
Separation
Sustainment
Utilization
Recruiting
Service
Members
Formal Training
& PME
Accessions
AFMA
Commanders
Copyright © 2011 Accenture All Rights Reserved.
MPFs
MAJCOMs
External
Departments
& Agencies
27
U.S. Air Force HRM Enterprise Architecture:
Military PDS “As-Is” SV-1
Copyright © 2011 Accenture All Rights Reserved.
28
U.S. Air Force HRM Enterprise Architecture:
Military PDS “As-Is” SV-2
Copyright © 2011 Accenture All Rights Reserved.
29
U.S. Air Force HRM Enterprise Architecture:
Data Flow “As Is” SV-04
Copyright © 2011 Accenture All Rights Reserved.
30
U.S. Air Force HRM Enterprise Architecture:
Result
•
•
•
•
•
•
The PSD-T Plan was approved by SecAF
Funding was secured in the Air Force Corporate Process
The RFP was released in 2007
The PSD-T Strategic Partner was selected in 2008
Individual Customer Service is a reality
Self Service through CRM…Tier 0
The HRM Enterprise Architecture effort although complex and time
consuming produced the desired outcome for the warfighter (customer)!
Copyright © 2011 Accenture All Rights Reserved.
31
How Accenture Defines enterprise architecture
Business & IT
Strategies
Business Strategy
Business Imperatives
Enables
IT Strategy
Significant
Agency Event
Enterprise
Architecture
(Ongoing
Process)
Culture
Competencies
Organization
Facilities
Equipment
Processes
Information
Applications
Technology
Annual and
Quarterly Changes
IT Direction
IT Imperatives
Current Environment
•
•
•
•
•
•
•
•
•
Drives
Future Environment
Business Blueprint
Process & Information
Blueprint
DoD or FEA
Framework
•
•
•
•
Performance RM
Business RM
Systems RM
Technology RM
Solution Blueprint
Assessments
Technology Blueprint
(Current vs. Future)
Strategic Roadmap – Programs, Business Case
Annual Roadmap – Programs, Projects, Funding
Change
Projects
Project Execution – Requirements, Design, Install/Build, Operate, Realize Value
Copyright © 2011 Accenture All Rights Reserved.
32
Did We Derive Business/Mission Value with
DLA – EA?
Overview
Accenture established an Enterprise Architecture (EA) for Defense Logistics Agency’s (DLA) Enterprise
Business System (EBS) Program which provides a single point of reference for its business processes, system
functions and technical standards documentation.
Business Challenge
How Accenture helped
High performance delivered
Prior to EBS, architecture was
developed but as silo business
blueprints. The challenge on EBS
was to establish an EA that moved
away from this siloed approach,
and instead integrated and
organized all the EBS capabilities’
business processes, system
functions and technical standards
into a set of complementary and
consistent views.
Accenture helped create a more
robust EA for DLA’s EBS Program.
All the EBS business processes,
system functions and technical
standards were integrated and
organized into a common set of
operational, technical and system
views. The Accenture team used
the IDS Scheer tool called ARIS to
successfully capture and document
the EA. Moreover, the EA is in
compliance with the Department of
Defense Architecture Framework
(DoDAF) 1.5.
DLA’s EBS EA provides a single
point of reference for the
Program’s business
documentation. Furthermore, the
EBS EA enables DLA Leadership
to have an integrated and
consistent view of IT investments
for decision making purposes.
Copyright © 2011 Accenture All Rights Reserved.
33
Deriving Enterprise Architecture Value
Commercial/Industry
Enterprise Architecture
1. Hiring and Finding Qualified Personnel is the largest Impediment to EA success.
2. Qualified and Certified Personnel is the single most important item to EA success.
Copyright © 2010
2011 Accenture All Rights Reserved.
34
Questions?
Contact information
Rob Thomas II
Enterprise Transformation
Strategy Executive
Accenture
[email protected]
+1 703 947 3885
1. Hiring and Finding Qualified Personnel is the largest Impediment to EA success.
2. Qualified and Certified Personnel is the single most important item to EA success.
Copyright © 2011 Accenture All Rights Reserved.
35