Title: Department of the Interior Enterprise Architecture Overview
1Department of the Interior Enterprise
Architecture Overview
- DOI Process for Modernization Blueprints a
Take-Action Approach to Enterprise Architecture
2Take-Action Approach to Enterprise
Architecture A Methodology to transition to a
Target Architecture
Actions (Enhancements, Efficiencies, Strategies)
Vision
Assessment
DOI Enterprise Architecture - Target Application
Architecture (TAA)
Transition Plan
3How is the approach Take-Action?
- Evaluate systems for
- Which systems are old and/or costly to maintain?
- Develop recommendations on how to move forward
are rectify - Opportunities to tie systems together more
effectively. - Identify systems that need to talk but dont
- Identify business process issues that are not
currently addressed. - Opportunities to centralize information assets.
- Improve reporting, security and data integrity.
- Evaluate systems capabilities for supporting
strategic goals and objectives - Evaluate against end and intermediate strategic
outcomes and measures - Deliver short and longer-term recommendations
that can be acted upon - Which systems would need to be consolidated.
- Which systems would benefit from shared
application services. - Potential investment proposals that may need to
be considered now. - Comprehensive views of how the IT systems support
the lines of business.
4Take-Action Approach to Enterprise Architecture
Four Phases
1. Establish Methodology for Defining
Modernization Blueprint.
Modernization blueprints a related set of
tactical and strategic modernization
recommendations.
2. Determine Scope of Assessment and Collect Data
4. Develop Tactical and Strategic Modernization
Blueprints
Department Enterprise Architecture Repository (DEA
R)
3. Assess Alignment With FEA and DOI Architectures
The Department Enterprise Architecture Repository
(or DEAR) will be the system of record for
critical EA information.
51. Establish Conceptual Vision of Target
Architecture - Criteria
Business Assessment Criteria
Data Assessment Criteria
Technology Assessment Criteria
Security Assessment Criteria
Application Assessment Criteria
1. Establish
Methodology
Modernization
Blueprint
4. Develop
2. Determine
Tactical and
The criteria is derived from IEA Conceptual
Architecture Principles (CAP) Common
Requirements Vision (CRV) and is used to assess
how well a system aligns with the target state.
Scope of
Strategic
Assessment and
Modernization
Collect Data
Blueprints
3. Assess
Alignment With
FEA and DOI
Architectures
62. Determine Scope of Assessment and Collect Data
- Process
Subject Matter Expert Interviews
and Documentation Reviews
System 2
Future Project 1
System 7
System 3
Future Project 2
Models of Systems
Identified Systems Scope
System 8
System 4
Future Project 3
System 9
Future Project 4
System 5
Modernization Blueprint Interview Guide
Validation / Reports / Findings
System 10
System 1
System 6
System Grouping
Scope Document
72. Determine Scope of Assessment and Collect Data
Field Data Collection Templates are used to
collect the systems data
System Architecture Template
These data collection templates 1) standardize
the data collected about systems, and 2) ensure
uniform modeling of the systems across system
groupings.
FEA Reference Model Templates
83. Assess Alignment with FEA and DOI
Architectures - Process
Systems are assessed against established criteria
and are then classified
Extent to which the system complies with
current Security requirements and extent of
progress through the CA process.
Application Architecture
System Assessment
Technology Architecture
Security Architecture
Business Architecture
Data Architecture
- Degree of architectural compliance with the
Target Architecture. - Extent to which system design requirements are
defined and documented - Extent to which systems interfaces are defined
and documented - Extent to which high-level design or operational
concepts are defined.
- Systems capability for supporting associated
Strategic goals and objectives as defined in DOI
Strategic Plan. - Extent of stakeholders feedback for accomplishing
performance measures associated with strategic
goals, objectives and performance measures. - Lack of functional overlap with other systems as
defined by DOI BRM. - System incorporates re-engineered/streamlined
business processes (workflow) in an automated
fashion that supporting DOI Strategic goals and
objectives.
- Existence and documentation of data standards
and Protocols - Relative maturity and accessibility of system's
data storage and access methods - Relative overlap with data stored in other
Interior systems .
- Extent of maximum use of shared, existing
infrastructure components and services - Extent of compliance with Technology Reference
Model standards, protocols and best practices.
DRM
SRM / CBA
TRM
PRM / BRM
The modeling of DOI enterprise architecture
elements and their relationship to assessment
criteria facilitates line of sight analyses.
Popkin SA is used to model the relationship
between inputs, outputs, and outcomes. Model
queries and analyses support the assessment
process
9The System Grouping Analysis Template Criteria,
Scoring Against Criteria, and Visualization of
System Scoring Results
Templates for uniform system scoring
Well-defined criteria for assessing alignment
10The System Grouping Analysis Template
Assessment Quadrants
Migration (Integrate) Systems with relatively
high business fit and relatively low technology
fit where it is cost effective to upgrade the
technology architecture/infrastructure to adhere
to the TRM and conceptual TAA.
Target Systems with relatively high business
and technology fit.
Legacy - Systems still required by DOI that
should be considered for integration with other
systems or consolidation with target systems.
The systems being consolidated will essentially
be retired. These systems have relatively low
business (e.g., alignment with DOI Strategic
plan, CRV, CAP, process and data maturity) and/or
technology fit (e.g., alignment with TRM,
Conceptual TAA, etc.)
Migration (Consolidate/Retire) Systems with
relatively high technology fit however, the
business fit is relatively low. These systems
should be examined for possible retirement and/or
consolidation of required functionality and data
into Target Systems.
114. Develop Tactical and Strategic Modernization
Blueprints
Modernization blueprints (tactical and strategic
modernization recommendations) are produced and
should be managed in parallel.
Investment Proposals/ Business Cases
Recommendations
Strategic Modernization Blueprint
Decisions
Take-Action EA Approach
OM Project Management
Tactical Modernization Blueprint
DEAR
Decisions
Recommendations
12Conclusion
- Structured Enterprise Architecture Process
- Phase 1 Establish vision
- Phase 2 Critical to limit scope and constrain
data collection - Phase 3 Assess to develop relative scores
against Target - Phase 4 Develop recommendations that can be
implemented now and in a coordinated fashion to
address the future - Addresses Enterprise Architecture both from a
top-down strategic approach and a bottom-up
tactical approach - Strategic approach makes mission alignment IT
recommendations - Tactical approach makes systems improvement
recommendations that move systems incrementally
toward target architecture and can be implemented
with operations and maintenance budget dollars - Business owners prioritize recommendations for
implementation consistent with project management
governance processes - Recommend this process be used to develop
modernization blueprints across the DOI