1. Department of the Interior Enterprise Architecture Overview DOI Process for Modernization Blueprints a Take-Action Approach to Enterprise Architecture

2. A Take-Action Approach to Enterprise Architecture was developed and deployed at the BLM that can be effectively adapted for the Department. BLM Enterprise Architecture - Target Application Architecture (TAA) Transition Plan Assessment Actions (Enhancements,Efficiencies, Strategies) Vision Current Architecture Target Architecture 3. How was the approach Take-Action?

Evaluated systems for:

• Which systems wereold and/or costlyto maintain?

• • Developed recommendations on how to move forward quickly.

• Opportunities totie systems togethermore effectively.

• • Identified systems that need to talk that didnt.

• • Identified business process issues that are not currently addressed.

• Ways tocentralize informationassets.

• • Improved reporting, security and data integrity.

• Ways toimprove accessto information.

• • Introduce current technologies to broaden accessibility.

Delivered short and longer-term recommendations that can be acted upon:

• Which systems may need to beconsolidated .

• Which systems would benefit fromshared application services .

• Potentialinvestment proposalsthat may need to be considered now.

• Comprehensive views of how the IT systemssupport the lines of business .

4. Take-Action Approach to Enterprise Architecture Four Phases 1. Establish Conceptual Vision of Target Architecture 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. 5. 1. Establish Conceptual Vision of Target Architecture - Process Sample Conceptual Target Application Architecture FEA-PMO Guidance Technical Standards Industry Best Practices Document Target Architecture DEAR 6. 1. Establish Conceptual Vision of Target Architecture - Criteria Business Assessment CriteriaData Assessment CriteriaTechnology Assessment CriteriaService Assessment CriteriaThe criteria is derived from the target state and is used to assess how well a system aligns with the target state. Target Architecture DEAR 7. Initial efforts are focused on the 1,000 foot and the 10,000 foot levels for sets of related systems, then moved to the 30,000 foot level and higher for larger groupings of systems. OMB Federal Focus Enterprise Focus Systems Grouping Focus Related Systems Focus Individual Systems Focus 0 20 40 60 80 100 Breadth Meter 0 20 40 60 80 100 Depth Meter 0 20 40 60 80 100 Breadth Meter 0 20 40 60 80 100 Depth Meter Data Collection / Validation Related Systems Systems Grouping Enterprise Target OMB Linkages and Alignment 1000 10000 30000 50000 100000 0 20 40 60 80 100 Breadth Meter 0 20 40 60 80 100 Depth Meter 0 20 40 60 80 100 Breadth Meter 0 20 40 60 80 100 Depth Meter 0 20 40 60 80 100 Breadth Meter 0 20 40 60 80 100 Depth Meter 8. 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 Target Architecture Interview Guide Validation / Reports / Findings System 6 Future Project 1 Future Project 3 Scope Document System Grouping Models of Systems Identified Systems Scope DEAR 9. 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, and2) ensure uniform modeling of the systems across system groupings. System Architecture Template FEA Reference Model Templates DEAR 10. 3. Assess Alignment with FEA and DOI Architectures - Process SystemAssessmentBusiness Architecture Data Architecture Technology Architecture ServiceArchitecture Classification

Business processes supported by the system

System support of DOI and BLM strategies, goals, and objectives

Stakeholders feedback on performance

Functional overlap with other systems

System training and support opportunities addressed.

PRM / BRM DRM SRM / CBA TRM

Existence and documentation of data standards and protocols

Data storage / access method maturity

Data entity access / modification overlap with other systems.

Target Application Architecture compliance

Extent system design requirements are defined and documented.

Extent systems interfaces are defined and documented.

Extent to which high-level design or operational concepts are defined.

Compliance with TRM technology architecture components

Extent of use of shared, existing infrastructure components and services

Extent of compliance with TRM standards, protocols and best practices.

Legacy Architecture

Consolidate Low Data Maturity Systems

Re-engineer Low Systems Architectures

Target

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 DEAR 11. Our analysis template is reuseable and ensures uniform analysis across system groupings The System Grouping Analysis Template Analysis and Assessment Introduction Worksheet Provides background, takes user throughassessment step by step with automated links torelated information at summary and detailed levels DEAR 12. Well-defined criteria for assessing alignment Templates for uniform system scoring Visualization of assessment results The System Grouping Analysis Template Criteria, Scoring Against Criteria, and Visualization of System Scoring Results 13. 4. Develop Tactical and Strategic Modernization Blueprints DEAR Modernization blueprints (tactical and strategic modernization recommendations) are produced and should be managedin parallel .Take-Action EA Approach Strategic Modernization Blueprint Tactical Modernization Blueprint Recommendations Recommendations Decisions O&M Project Management Decisions Investment Proposals/ Business Cases 14. 4. DevelopTacticalModernization Blueprints Process Sample Conceptual Target Application Architecture Current System Issues Assessment Analysis Analyst Experience Tactical Improvement Candidate List DEAR 15. 4. DevelopTacticalModernization 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 16. 4. DevelopTactical and StrategicModernization 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 BeArchitecture Diagrams DEAR 17. 4. DevelopTacticalModernization 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 18. 4. DevelopTacticalModernization Blueprints Plan to roll out modernization blueprint improvements in context with other systems The tactical sequencing plan provides a modernization blueprint to implement improvements and allows the DOI to track progress towards improvement targets. Start Date Target andDurations Dependencies Among Recommendations Candidate Tactical Recommendations DEAR 19. 4. DevelopStrategicModernization Blueprints Process Mission Goals Tactical Plans / TAA Overlap Analysis E-Gov FEA Guidance 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 Strategic Modernization Blueprint Sequencing Plan Identified system groupingplusother related enterprise systems or initiatives DEAR Overall DOI Direction 20. 4. DevelopStrategicModernization 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 21. 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 Phase 1 Deliverable: TAA Document Phase 3 & 4 Deliverables: Modernization Blueprints Architecture Presentations Phase 2 Deliverables: Scoping Document Data Collection Documentation Assessment Actions (Enhancements,Efficiencies, Strategies) Vision Current Architecture Target Architecture 22. 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 TAA

• 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

23. Document Abstract Revision History doi_take_action_taa_031022.ppt QA Lockwood 10.28.2003 Final DOI Take-Action Approach Presentation V2.1.ppt Presented to John Broderick T. Fries 10.22.2003 Final Filename/lineage Description of edit Author/Editor Rev. Date Doc Status Key Words: Application Technology Architecture TAA DOI Tack Action Approach TAA take action approach overview briefing provided to John Broderick on 22 October 2003. Contract #:NBD020221 Task Number: 4 1230 FEAF Area: Subject Function Code: