# Presentation: 223683

## Department of the Interior Enterprise Architecture Overview

- DOI Process for Modernization Blueprints – a “Take-Action” Approach to Enterprise Architecture

## “Take-Action” Approach to Enterprise Architecture: 	A Methodology to transition to a Target Architecture

- DOI Enterprise Architecture - Target Application Architecture (TAA)

- Transition
- Plan

**Assessment**

**Actions**
**(Enhancements, **
**Efficiencies, Strategies)**

**Vision**

**Notes:**
Take out all reference to BLM.  Target should be to right not left.  Reverse graphic.

## How 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 don’t
- Identify business process issues that are not currently addressed.
- Opportunities to _centralize information_ assets.
- Improve reporting, security and data integrity.
- Evaluate system’s 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_.

**Notes:**
Change Slide to Future versus past tense.

## Take-Action Approach to Enterprise Architecture – Four Phases

- 1. Establish Methodology for Defining  Modernization Blueprint.

- 2. Determine Scope of Assessment and Collect Data

- 3. Assess Alignment With FEA and DOI Architectures

- 4. Develop Tactical and Strategic Modernization Blueprints

**Department**
**Enterprise**
**Architecture**
**Repository**
**(DEAR)**

**The Department Enterprise Architecture Repository (or DEAR)**
**will be the system of record for critical EA information.**

**Modernization blueprints – a related set of tactical and strategic modernization recommendations.**

**Notes:**
I changed # 1 since we don’t have a conceptual TAA to start out with.  We do have base IEA documents that we can leverage CRV, CAP (see narrative).  Refer to these as the basis for developing the criteria.

## 1. Establish Conceptual Vision of Target Architecture - Criteria

**Business Assessment Criteria **

**Data Assessment Criteria **

**Technology Assessment Criteria **

**Application Assessment Criteria **

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

- 1. Establish

- Methodology

- Modernization

- Blueprint

- 2. Determine

- Scope of

- Assessment and

- Collect Data

- 3. Assess

- Alignment With

- FEA and DOI

- Architectures

- 4. Develop

- Tactical and

- Strategic

- Modernization

- Blueprints

**Security Assessment Criteria **

**Notes:**
Changed “Service” to “Application”

## 2. Determine Scope of Assessment and Collect Data - Process

**Future Project 4**

**System 10**

**System 1**

**System 4**

**System 5**

**System 2**

**System 3**

**Future Project 2**

**System 7**

**System 8**

**System 9**

**Subject Matter**
**Expert**
** ****Interviews and**
**Documentation**
**Reviews**

- Modernization Blueprint
- Interview Guide

- Validation / Reports / Findings

**System 6**

**Future Project 1**

**Future Project 3**

- Scope Document

- System
- Grouping

- Models of Systems

- Identified
- Systems
- Scope

## 2. Determine Scope of Assessment and Collect Data

**2. Determine Scope of Assessment and Collect Data**

**Field Data Collection Templates are used to collect the systems data**

**These data collection templates:**
**1) standardize the data collected about systems, and **
**2) ensure uniform modeling of the systems across system groupings.**

**System**
**Architecture**
**Template**

**FEA Reference Model**
**Templates**

## 3. Assess Alignment with FEA and DOI Architectures - Process

**3. Assess Alignment with FEA and DOI Architectures - Process**

**    ****System  Assessment    **

**Business**
**Architecture**

**Data**
**Architecture**

**Technology**
**Architecture**

**Application**
**Architecture**

*** ******System’s 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.***

- PRM / BRM

- DRM

- SRM / CBA

- TRM

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

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

***Extent of maximum use of shared, existing infrastructure components and services***
*** ******Extent of compliance with Technology Reference Model standards, protocols and best practices.***

- 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

**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 C&A**
** ****process.**

**Security**
**Architecture**

**Notes:**
CHANGE CRITERIA TO MATCH NARRATIVE DOCUMENT.  CHANGE CLASSIFICATION

## The System Grouping Analysis Template – Analysis and Assessment

**Our analysis template is reusable and ensures uniform analysis across system groupings**

**The System Grouping Analysis Template – Analysis and Assessment**

**Introduction Worksheet –**
**Provides background,**
**takes user through **
**assessment step by step**
**with automated links to **
**related information at summary and detailed levels**

## The System Grouping Analysis Template – Criteria, Scoring Against Criteria, and Visualization of System Scoring Results

**Well-defined criteria for assessing alignment**

**Templates for uniform system scoring**

**The System Grouping Analysis Template – Criteria, Scoring Against Criteria, and Visualization of System Scoring Results**

**Notes:**
CHANGE CLASSIFICATION DIAGRAM.

Develop sub-categories in Narrative for RED, YELLOW AND GREEN.

## The System Grouping Analysis Template – Assessment Quadrants

**The 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.

## 4. Develop Tactical and Strategic Modernization Blueprints

**DEAR**

**Modernization blueprints (tactical and strategic modernization recommendations) are produced and should be managed **_***in parallel***_**. **

**Take-Action**
**EA**
**Approach**

**Strategic**
**Modernization**
**Blueprint**

**Tactical**
**Modernization**
**Blueprint**

**Recommendations**

**Recommendations**

**Decisions**

- O&M
- Project
- Management

**Decisions**

- Investment
- Proposals/
- Business
- Cases

**Notes:**
Excellent Slide

## 4. Develop Tactical Modernization Blueprints – Documentation of Selected Tactical Improvements, Identify Magnitude of Effort, Develop Recommendation

**4. Develop **_***Tactical***_** Modernization Blueprints – Documentation of Selected Tactical Improvements, Identify Magnitude of Effort, Develop Recommendation**

- Conduct baseline analyses
- Set improvement targets
- Identify, select, and propose improvements
- Maximize investment across entire system grouping

- Recommendations can be prioritized to yield maximum benefits across the system grouping within budget constraints

**DEAR**

## 4. Develop Tactical and Strategic Modernization Blueprints – Support Recommendations with “As-Is”, “To-Be” Architectures

- Tactical recommendations include short-term improvements in alignment with strategic architecture goals within constraints of existing O&M budgets.  Recommendations include “As Is” and “To Be”
- Architecture Diagrams

**DEAR**

## 4. Develop Tactical Modernization Blueprints – Process

**4. Develop **_***Tactical***_** Modernization Blueprints – Process**

**Future Project 4**

**System 10**

**System 1**

**System 4**

**System 5**

**System 2**

**System 3**

**Future Project 2**

**System 7**

**System 8**

**System 9**

**System 6**

**Future Project 1**

**Future Project 3**

- Identified
- Improvement
- Candidates

- Duration/
- Cost
- Estimates

- Dependencies

- Tactical
- Modernization
- Blueprint
- Sequencing
- Plan

**Identified system grouping only**

**DEAR**

**Notes:**
Are we SURE WE CAN DO TACTICAL BLUEPRINTS FOR FIVE LOB in ONE YEAR?

## 4. Develop Strategic Modernization Blueprints – Blueprint Plan

-  Enables progress towards target application architecture
-  Provides conceptual roadmap to target architecture
-  Identifies systems to be retired, consolidated, and re-engineered
-  Informs project, program, and portfolio management
-  Identifies investment proposals to be worked now to enable the future state

**Horizontal “Services”**

**Conceptual**
**Target**
**Architecture**

**E-Gov Linkages**

**Investment**
**Cycle**
**Phase**

**DEAR**

**Recommended**
**System**
**Transitions**

## The Vision, Data Collection, and Assessment Phase Deliverables provide the basis for the delivery of the Modernization Blueprints

- Enterprise Architecture - Target Application Architecture (TAA)

- Transition
- Plan

**Assessment**

**Actions**
**(Enhancements, **
**Efficiencies, Strategies)**

**Vision**

## Conclusion

- 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