Federal Segment Architecture Methodology FSAM Practitioners Training Version

Federal Segment Architecture Methodology (FSAM) Practitioner’s Training Version 1. 0 FSAM Version 1. 0 1

What is FSAM? FSAM Version 1. 0 2

What is Segment Architecture? Segment Architecture: Detailed results-oriented architecture (baseline and target) and a transition strategy for a portion or segment of the enterprise. o A scalable and repeatable process for architects to engage business stakeholders and deliver value to business areas o Helps to establish clear relationships between strategic goals, detailed business and information management requirements, and measurable performance improvements Source: FEA Practice Guidance FSAM Version 1. 0 3

Introduction to the new FSAM What is FSAM? • The new Federal Segment Architecture Methodology (FSAM) is a step by step process for developing and using segment architecture that leverages existing “best practice” analysis techniques and easy to use templates to expedite architecture development • FSAM includes process steps to identify and validate the business need and the scope of the architecture to be defined (e. g. , new initiative or integration / consolidation of existing initiatives). • FSAM includes the interfaces to other processes including performance / investment management, enterprise transition planning, solution architecture development, and system lifecycle management Who created FSAM? • The Federal Segment Architecture Working Group (FSAWG) is a cooperative effort with the federal architecture community formed in January 2008 as a subteam to the Architecture and Infrastructure Committee (AIC) and therefore, an element of the Federal CIO Council, at the request of the OMB Chief Architect FSAM Version 1. 0 4

Since the FSAWG was initiated, the team has made great headway. Some notable facts include… Best Practices • 13 Federal organizations, including 2 cross-agency initiatives participated o 13 people on core team o 34 people on sub-team • 10 best practice presentations delivered • 18 assessed best practices considered • 78 analytical techniques cataloged o Including 232 templates / examples • HUD - Segment Architecture Development Guidance / Work Product and Decision Templates • Do. D – Do. DAF Version 2. 0 (Draft) • DOI - Methodology for Business Transformation (MBT) • DOJ - Information Sharing Segment Architecture (ISSA) • PM-ISE - Information Sharing Environment EA Framework • PM-ISE - FEA Information Sharing Environment Profile • DHS – Information Sharing Environment • DOL - EA Quick Reference Guide • DOL - IT Investment Management Quick Reference Guide • DOL – STREAMLine Methodology • Treasury - Segment Architecture Analysis Guide • Treasury - Segment Architecture Process Guide • Treasury - Segment Architecture Roadmap • HRLOB – Segment Architecture Approach • EPA - OSWER Segment Architecture Line-of-Sight: From Architecture through Implementation • HHS - HHS Architecture Development Methodology (ADM) • FEA - Security and Privacy Profile (v 2) (Draft) • FEA - Records Management Profile FSAM Version 1. 0 5

The FSAWG team made a few observations on EA as a discipline … • No consensus on what constitutes a complete performance, business, technology, service and data architecture • Segment Architecture is often focused on populating artifacts rather than synthesis of recommendations to deliver business value • A lack of formal sharing of analytical techniques and best practices exists across the Federal government • Varying levels of maturity exist across Agency EA programs • No standard Federal-wide approach exists for defining segment architecture FSAM addresses these issues FSAM Version 1. 0 6

FSAM promotes a consistent approach to developing segment architecture • Defines the core elements and attributes that are needed for defining a complete segment architecture. • Includes process steps, activities and associated tasks to identify and validate the business need and the scope of the architecture to be defined. • Includes the development of as-is, target and transition plans for the performance, business, data, services, and technology architecture layers. • Provides an online toolkit containing analytical templates to support the architecture practitioner towards expediting their segment architectures. • Provides case examples from participating agencies to relay real life examples highlighting specific facets of the methodology. • Assures business integration between mission priorities and financial investments, particularly IT investments. FSAM Version 1. 0 7

The top level steps of FSAM start with the FEA Practice Guidance published by OMB as a launch point for use/refinement Determine Participants and Launch Project Develop the Segment Scope and Strategic Intent Define Business and Information Requirements Define the Conceptual Solution Architecture Author the Modernization Blueprint FSAM provides the Process Step decomposition of the ‘Develop Segment Architecture’ Lifecycle Phase FSAM Version 1. 0 8

FSAM includes the steps for developing a Segment Architecture as well as hand-offs to Enterprise and Solution Architecture FSAM Version 1. 0 9

FSAM supports the entire lifecycle from strategic planning to execution with a primary focus on developing actionable architecture Strategic Planning Execution Architecture Strategic Planning Architecture CPIC Budget CPIC Execution FSAM Version 1. 0 10

FSAM Overview FSAM Version 1. 0 11

FSAM features a series of touch points to other disciplines such as security. FSAM Version 1. 0 12

FSAM features a series of touch points to other disciplines such as security. NIST 800 -39 Organizational View of Risk Management NIST 800 -60 Security Categorization Process FSAM Version 1. 0 13

In addition, FSAM has identified touch points with other Federal guidance NIST 800 -39 FSAM FTF PGFSOA FSAM Version 1. 0 14

PGFSOA Integration 1 2 Task 3. 2. 2: Determine the required adjustments to the business architecture Task 3. 2. 3: Align strategic improvement opportunities to the information architecture PGFSOA, Sec. 4. 1. 6: Many of the benefits of SOA are derived from sharing – sharing information, sharing business processes, sharing reference architectures, and sharing services. PGFSOA, Sec. 4. 1. 7: Employ enterprise architecture tools and artifacts to identify significant information exchanges across domains of interest. FSAM Version 1. 0 3 Task 4. 2. 1: Review FTF for service reuse opportunities PGFSOA, 3. 2. 3: Adoption of some common services across the federal government will start with infrastructure services (e. g. , authentication, auditing) but quickly expand to business utility services (e. g. , federal employee lookup, simple approval process, calendar services, scheduling). 15

NIST 800 -39 Integration 1 Task 2. 2. 3: Identify segment risks and impacts NIST 800 -39, Sec. 3. 2: The first step in building an effective organizationwide information security program is to conduct a thorough analysis of the organization’s mission and business processes informed by the organization’s enterprise architecture… FSAM Version 1. 0 3 2 Task 3. 1. 4: Analyze processes and determine high-level information requirements including organizational relationships NIST 800 -39, Sec. 3. 2: Conducting the security categorization process as an organizationwide exercise helps ensure that the process accurately reflects the criticality, sensitivity, and priority of the information and information systems that are supporting organizational mission/business processes and is consistent with the organization’s enterprise architecture. Task 4. 1. 4: Determine adjustments necessary to the as-is conceptual solution architecture NIST 800 -39, Sec. 3. 3: Security controls should be reflected in the FEA solution architectures and should be traceable to security requirements allocated to mission/business processes defined in the FEA segment architectures. . . See also NIST 800 -53, FIPS 199, and FIPS 200. 16

FTF Integration 1 Task 1. 2. 2: Synthesize the common business challenges across the Business Owners FTF Usage Guide, Sec. 3. 1: [The] FTF Catalog includes both mandatory and informational initiatives. Mandatory initiatives must be included in agency enterprise architecture and the agency EA Transition Strategy, and agency alignment with these initiatives is assessed as part of the annual EA assessment process. FSAM Version 1. 0 2 Task 4. 2. 1: Review FTF for service reuse opportunities FTF Usage Guide, Sec. 3. 1: The FTF Catalog provides information to agency decision makers to support the implementation of cross-agency initiatives, and provides guidance to working groups with responsibility to develop cross-agency initiative architecture. The catalog supports usage scenarios for agency decision makers and cross-agency task forces, working groups or communities of practice with responsibility to develop initiative architecture. 17

The EA Segment Report (EASR) Meta-model has been integrated with the FSAM Strategic Alignment Analysis Template Strategic Element Segment Strategic Goal/Objective <name> Business and IT Modernization Initiative <name> FSAM Version 1. 0 Architecture Work Product Opportunity Rationale List Describe rationale Target work Opportunities for strategic product name alignment P&I Tiger Team Reporting Template PAR Metric Component, Bureau, Operating Division, etc PAR Performance Strategic Goal Target Actual Target Achieved/Not Achieved? 18

The FSAWG used a three-level decomposition for the new methodology 1 2 3 FSAM Version 1. 0 19

Each process step is detailed in a step guidance document • • • FSAM Version 1. 0 Step Description and Purpose Step Outcome Step At-A-Glance Activity Details Activity Short Description Activity Flow Chart with Tasks Activity Inputs Tasks Communication Considerations Activity Outputs Suggested Analytical Techniques (with examples and templates) 20

Analytical techniques have been included in the FSAM with templates from Agency best practices Each suggested analytical technique table includes: • Output name • Core – (Y, N) Outputs that support population of Segment Architecture Template in EAAF Ver. 3. 0. • Associated FEA Layers • Name of suggested analytical technique • Link to the template/example • Contributing Agency FSAM Version 1. 0 21

FSAM outputs are designed to progressively elaborate the information required to define a segment architecture. Core FSAM outputs provide the information necessary for EAAF reporting requirements Non-core FSAM outputs provide additional information that can be used to inform decision making related to the segment mission, business, and information needs. FSAM Version 1. 0 22

Walkthrough of FSAM Steps 1 -5 FSAM Version 1. 0 23

Step 1 Determine Participants and Launch the Project FSAM Version 1. 0 24

Activities for Step 1: Determine Participants and Launch Project FSAM Version 1. 0 25

Key Questions Being Answered by Step 1: Determine Participants and Launch Project • What is the governance framework for the development of the segment architecture? • Does the business owner(s) understand the process and time commitment for developing the segment architecture? • Who is the executive sponsor? • Who is on the core team? Are these the right people? • What is the specific purpose for developing this segment architecture? • Is the charter approved to develop the segment architecture in the context of the purpose statement crafted by the business owner(s)? • Is there a project plan and communications strategy for the development of the segment architecture? FSAM Version 1. 0 26

Activity 1. 1: Determine the executive sponsor FSAM Version 1. 0 27

Activity 1. 2: Develop the purpose statement for the segment FSAM Version 1. 0 28

Activity 1. 3: Solicit core team members FSAM Version 1. 0 29

Activity 1. 4: Create core team charter and project plan FSAM Version 1. 0 30

Activity 1. 5: Establish the communications strategy FSAM Version 1. 0 31

Step 1 Outputs Governance Framework Segment Architecture Development Purpose Statement Core Team Roster Core Team Formation Memorandum Core Team Charter Project Plan Communications Strategy FSAM Version 1. 0 32

Governance Framework DOJ FSAM Version 1. 0 33

Segment Architecture Development Purpose Statement – [Core] Segment Architecture Development Purpose Statement FSAWG FSAM Version 1. 0 34

Core Team Formation Memorandum FSAWG FSAM Version 1. 0 35

FSAM provides additional project management tools to support segment architecture development Communication Strategy FSAM Segment Architecture Development Project Schedule Core Team Charter Core Team Roster FSAWG FSAM Version 1. 0 36

Step 2 Define the Segment Scope and Strategic Intent FSAM Version 1. 0 37

Activities for Step 2: Develop the Segment Scope and Strategic Intent FSAM Version 1. 0 38

Key Questions Being Answered by Step 2: Develop the Segment Scope and Strategic Intent • Based on the high-level problem statement, what are the strategic improvement opportunities and gaps? • What are the major common / mission services associated with the strategic improvement opportunities? • Who are the segment stakeholders and what are their needs? • What is the scope of the segment architecture? • What are the current segment investments, systems, and resources? • What are the deficiencies within the segment or the inhibitors to success? • What is the target state vision for the segment? • What is the performance architecture through which the transition to the target state vision can be evaluated? FSAM Version 1. 0 39

Activity 2. 1: Establish segment scope and context FSAM Version 1. 0 40

Activity 2. 2: Identify and prioritize strategic improvement opportunities FSAM Version 1. 0 41

Activity 2. 3: Define segment strategic intent FSAM Version 1. 0 42

Activity 2. 4: Validate and communicate the scope and strategic intent FSAM Version 1. 0 43

Step 2 Outputs Business Drivers and Mandates Stakeholders and their Relationships Segment Scope Stakeholder Needs Risks and Impacts Segment Context Performance Gaps Strategic Improvement Opportunities Segment Performance Goals and Objectives Common / Mission Services Target Maturity Levels Segment Architecture Vision Summary Performance Scorecard Segment Scope and Strategic Intent Presentation FSAM Version 1. 0 44

Business Drivers and Mandates – [Core] Driver and Policy Map HHS FSAM Version 1. 0 45

Stakeholders and their Relationships – [Core] Stakeholder Map HHS FSAM Version 1. 0 46

Segment Scope – [Core] Segment Summary HHS FSAM Version 1. 0 47

Stakeholder Needs UID Need Description Stakeholder Name Stakeholder Type [Unique ID of Need] [Description of the need] [Name of stakeholder associated with the need] [Type of stakeholder associated with the need] FSAWG FSAM Version 1. 0 48

Risks and Impacts Risk Capture Template Segment Name / Code Document Organization: Owner: Phone: Email: Purpose of The Risk List is used to track and manage risks to the [segment name] segment. Risk List: ID Risk Label Risk Description Risk Category Severity Probability Risk Priority Unique ID Brief Provide a more tracking label for detailed number the Risk description of for each the Risk including the identified expected impact if the risk occurs Enter a category description (i. e. , type) of the risk. Examples include mission, people, process, business, cost, data, privacy, security, technology, etc. What is the severity of the risk to the project scope, schedule, and resources if it occurs (H/M/L) What is the likelihood that the risk may occur (H/M/L) Enter the overall priority of the risk (H/M/L) 1 2 3 4 5 6 7 8 Submitted by Risk List Date Identified Risk Owner Risk Status Mitigation Plan Contingency Response Plan Enter the Date the name of the Risk was person who identified the risk Name of owner of the Risk owner is responsible for tracking and reporting on the status of the risk and any associated response plans Risk Status: Inactive Risk has not occurred Active - Risk has occurred and response plan is in effect What is the overall plan to reduce the probability or effect of the risk. What is the plan responding to the risk should it occur. DOT FSAM Version 1. 0 49

Segment Context Current Operating Environment Diagram EPA FSAM Version 1. 0 50

Performance Gaps – [Core] Performance Gap Analysis HUD FSAM Version 1. 0 51

Strategic Improvement Opportunities Analysis – [Core] Strategic Improvement Opportunities Analysis Potential Opportunities Opportunity Analysis Prioritization Criteria HUD FSAM Version 1. 0 52

Strategic Improvement Opportunities Analysis – [Core] SWOT Analysis HUD FSAM Version 1. 0 53

Segment Performance Goals and Objectives – [Core] Strategic Alignment of Opportunities HUD FSAM Version 1. 0 54

Common / Mission Services Target Maturity Levels Common / Mission Services Maturity Framework DOI FSAM Version 1. 0 55

Segment Architecture Vision Summary Segment Summary HHS FSAM Version 1. 0 56

Performance Scorecard – [Core] Performance Scorecard PAR Metrics PAR Metric PART Metrics Agency, Component, Fiscal Bureau, Operating Agency Year Division, etc Code Strategic Goal Target Achieved Target Actual ? (Y/N) Agency, Component, Bureau, Operating Division, etc Program Agency Code Year Assessed Final Rating Business / Service Performance Line of Sub-function Strategic Agency IT System / Goal(s) Business Fiscal Measurement Metric Investment App / Measurement Business or or Service Actual ID Service Type Component Supported Process Year Area Category Indicator Type Name UID Program Baseline Target Results Segment Architecture Performance UID Fiscal Year Segment Architecture Development Measurement Indicator FSAM Version 1. 0 Actual Results Target Comments FSAWG 57

Step 3 Define Business and Information Requirements FSAM Version 1. 0 58

Activities for Step 3: Define Business and Information Requirements FSAM Version 1. 0 59

Key Questions Being Answered by Step 3: Define Business and Information Requirements • How well does the current (as-is) business and information environment perform? • How should the target business and information environment be designed? • Have the segment’s goals and performance objectives been translated into an actionable and realistic target business and information architecture expressed within business functions, business processes, and information requirements? • Have the business and information requirements been analyzed and documented to the lowest level of detail necessary to form actionable recommendations? • Did the business and information analysis provide a synchronized and cohesive set of recommendations? • Does the core team understand the adjustments that are required for the current business and information environments to fulfill the target performance architecture? FSAM Version 1. 0 60

Activity 3. 1: Determine current business and information environment associated with strategic improvement opportunities FSAM Version 1. 0 61

Activity 3. 2: Determine business and information improvement opportunities FSAM Version 1. 0 62

Activity 3. 3: Define target business and data architectures FSAM Version 1. 0 63

Activity 3. 4: Validate and communicate target business and data architectures FSAM Version 1. 0 64

Step 3 Outputs As-Is Business Value Chain As-Is Business Function Model Target Business Value Chain As-Is Key Business Process Models Target Business Function Model Business and Information Architecture Adjustment Profiles As-Is Key Business Process Swim Lane Diagram Target Key Business Process Models Target Information Flow Diagram As-Is Key Information Sources and Qualitative Assessment Target Business Data Mapped to Key Business Processes (CRUD) Target Business Process Swim Lane Diagrams Target Data Steward Assignments Target Information Sharing Matrix Target Conceptual Data Model Business and Information Architecture Presentation FSAM Version 1. 0 65

As-Is / Target Business Value Chain Analysis DOJ FSAM Version 1. 0 66

As-Is / Target Business Function Model – [Core] Business Function Model DOI FSAM Version 1. 0 67

As-Is / Target Key Business Process Model Business Activity Model Do. D FSAM Version 1. 0 68

As-Is / Target Business Process Swim Lane Diagram DOJ FSAM Version 1. 0 69

Business and Information Architecture Adjustment Profiles Treasury FSAM Version 1. 0 70

Target Information Flow Diagram – [Core] Target Information Flow Diagram Ste p Step Label No. 1 Observation 2 Process Description The process begins when a person or persons observe unusual behavior. Such activities could include, but are not limited to, surveillance, photography of facilities, site breach or physical intrusion, cyber attacks, possible testing of security or security response, indications of unusual public health sector activity, unauthorized attempts to obtain precursor chemical/agents or toxic materials, or other usual behavior or sector-specific incidents. Initial An official of a Federal, State, or Response and local agency with jurisdiction Investigation responds to the reported observation. This official gathers additional facts through personal observations, interviews, and other investigative activities. In the context of priority information requirements, as provided by State and major urban area fusion centers, the officer/agent may use a number of fact based systems to continue the investigation. These fact based systems provide the officer/agent with a more complete picture of the activity being investigated. Some examples of fact based systems and the information they may provide include: Notes The observer may be a private citizen, a government official, or a law enforcement officer. The event may be documented using a variety of reporting mechanisms and processes, including but not limited to, reports of investigation, event histories, field interviews (FI), citations, incident reports, and arrest reports. The record may be hard and/or soft copy and does not yet constitute an ISE -SAR. Department of Motor Vehicles provides drivers license and… ISE FSAM Version 1. 0 71

As-Is Key Information Sources and Qualitative Assessment ADS Candidate Qualitative Analysis Matrix DOI FSAM Version 1. 0 72

Target Business Data Mapped to Key Business Processes CRUD Matrix HHS FSAM Version 1. 0 73

Target Data Steward Assignments – [Core] Target Data Steward Matrix Org Unit 1 Org Unit 2 P Org Unit 3 S Org Unit 4 S Org Unit 5 P S S P P S TASK REFERENCE RECOMMENDATION PARTNER ORGANZIATION ISSUE FIRE PROGRAM PARTNER ACTION PLAN Organization LOCATION Data Concept S S Org Unit 6 Org Unit 7 S Org Unit 8 S Org Unit 9 Org Unit 10 S S P = Principle Data Steward S = Secondary Data Steward FSAM Version 1. 0 P DOI 74

Target Information Sharing Matrix – [Core] Target Information Sharing Matrix Information Class [Information Class Name] Information Provider [Name of information provider] Information Provider Data Source (Structured or Unstructured) [Type of provider’s data source. ] Information Consumer [Name of information consumer] Information Consumer Data Source (Structured or Unstructured) [Type of consumer’s data source. ] Information Sharing Service Type* [Type of Data Exchange or Data Access Service] High-Level Requirements [Identify any associated high -level requirements related to security, privacy, data standards, etc. ] *Data Sharing Service Types are either exchange services or access services as described in FEA DRM v 2. 0, Chapter 5. The type of data sharing service usually depends on the structured or unstructured nature of the provider’s data source to consumer’s structured or unstructured data source. *Types of Data Exchange Services *Types of Data Access Services Extract/Transform/Load Context Awareness Publication Structural Awareness Entity/Relationship Extraction Transactional Services Document Translation Data Query Content Search & Discovery Retrieval, Subscription and Notification Note: Access Services typically support many consumers. Generally, there is no need to identify specific consumers. FSAM Version 1. 0 DOI 75

Target Conceptual Data Model – [Core] Target Conceptual Data Model HR-LOB FSAM Version 1. 0 76

Step 4 Define the Conceptual Solution Architecture FSAM Version 1. 0 77

Activities for Step 4: Define Conceptual Solution Architecture FSAM Version 1. 0 78

Key Questions Answered by Step 4: Define the Conceptual Solution Architecture • What existing systems and services are deployed within the as-is conceptual solution architecture? • How well do the existing systems and services currently support the mission? Which systems and services should be considered for retirement and / or consolidation? • What does the target conceptual solution architecture need to include in order to fulfill the target performance architecture? • Are the selected target business functions, systems, and service components reusable? • Does the conceptual solution architecture support the target performance, business, and data architectures developed in prior steps, along with recommendations for transitioning from the as-is state to the target state? • Have the dependencies, constraints, risks, and issues associated with the transition been analyzed to identify alternatives to be considered? FSAM Version 1. 0 79

Activity 4. 1: Assess systems and technology environment for alignment with performance, business, and information requirements FSAM Version 1. 0 80

Activity 4. 2: Define the target conceptual solution architecture FSAM Version 1. 0 81

Activity 4. 3: Identify and analyze system and service transition dependencies FSAM Version 1. 0 82

Activity 4. 4: Validate and communicate the conceptual solution architecture FSAM Version 1. 0 83

Step 4 Outputs As-Is Conceptual Solution Architecture As-Is System and Services Scoring Target Conceptual Solution Architecture Target Technical Architecture Target Service Component Architecture Data Reuse Summary Integrated Service Component and Technology Model Transition Recommendation Profile Transition Recommendation Sequencing Diagram Recommendation Sequencing Milestones Conceptual Solution Architecture Presentation FSAM Version 1. 0 84

As-Is / Target Conceptual Solution Architecture – [Core] System Interface Diagram Treasury FSAM Version 1. 0 85

As-Is System and Services Scoring As-is systems and services description and scoring DOI FSAM Version 1. 0 86

Target Technical Architecture – [Core] Technology Model HRLOB FSAM Version 1. 0 87

Target Service Component Architecture – [Core] Service Component Model (SCM) HRLOB FSAM Version 1. 0 88

Data Reuse – [Core] Data Reuse Exchange Package Definition and Reused Exchange Organizational Exchange Package Owning Using Information Package Name Package Owner Data Steward Information System Description (Organization) Agency Code Information Exchange Package Reuse Information Note: Complete this list for each exchange package to identify associated reused data entities Reused Exchange Reused Data Entity Data Steward Package Name Description (Organization ) Agency Code FSAWG FSAM Version 1. 0 89

Reuse Summary – [Core] Reuse Summary Segment Reuse Segment Name Segment Code BRM Business Area System Name Service Name FSAM Version 1. 0 Segment Reuse Explanation Reused Business Capabilities List BRM Line of Business BRM Sub-Function Reused Information System List System Description System Owner Reused System Service List Service Description System Name Providing Organization Agency Code Segment System Owner FSAWG Agency Code 90

Integrated Service Component and Technology Model Information Flow Control Flow HR-LOB FSAM Version 1. 0 91

Transition Recommendation Profile Strategic, Business or Investment Improvement Opportunity: Summary of Effect on Strategic, Business or Investment Improvement Opportunity: Affected Business Function/Process, Information or Service Area(s): Summary of Transition Recommendation: (This may include transition to a target or intermediate state. Also include a transition sequencing diagram) Risks / Issues: Relationships and Dependencies: Estimate of Costs: FSAM Version 1. 0 Treasury 92

Transition Recommendation Sequencing Diagram DOI FSAM Version 1. 0 93

Recommendation Sequencing Milestones Segment Code Segment Name Segment Description Organizational Owner Agency Code Segment Type Priority Segment? (Y/N) Segment Development Phase Milestone IT Investment, ID System or Program Segment Transition Plan Target Actual Dependency Milestone Description Completion ID Date Dependencies / Constraints FSAWG FSAM Version 1. 0 94

Step 5 Author the Modernization Blueprint FSAM Version 1. 0 95

Activities for Step 5: Author the Modernization Blueprint FSAM Version 1. 0 96

Key Questions Being Answered by Step 5: Author the Modernization Blueprint • Have the findings from the previous steps been identified and categorized? • Have the transition options been analyzed for costs, benefits, and risks in order to develop recommendations for implementation? • Are the recommendations described in a detailed, actionable segment architecture blueprint supported by a holistic analysis of segment business, data, technology, and service components? • Has the blueprint and sequencing plan been reviewed and approved by the executive sponsor, business owner(s), and core team? FSAM Version 1. 0 97

Activity 5. 1: Perform cost / value / risk analysis to develop implementation recommendations FSAM Version 1. 0 98

Activity 5. 2: Develop draft blueprint and sequencing plan FSAM Version 1. 0 99

Activity 5. 3: Review and finalize the blueprint and sequencing plan FSAM Version 1. 0 100

Activity 5. 4: Brief core team and obtain approval FSAM Version 1. 0 101

Step 5 Outputs Analysis of Cost, Value and Risk for Transition Options Proposed Implementation Recommendations Strategic Systems Migration / Sequencing Overview Transition Plan Milestones Recommendation Implementation Sequencing Plan Segment Mappings Segment Architecture Blueprint Document (incl. Sequencing Plan) Document Review Log Feedback Tracking Document and Feedback Action Report Blueprint Executive Summary Presentation Approved Segment Architecture Blueprint Document (incl. Sequencing Plan) Record of Decision (ROD) FSAM Version 1. 0 102

Analysis of Cost, Value and Risk for Transition Options Value Measuring Methodology Cost to Value Matrix GSA FSAM Version 1. 0 103

Proposed Implementation Recommendations Recommendation Implementation Overview FSAWG FSAM Version 1. 0 104

Strategic Systems Migration / Sequencing Overview – [Core] Recommendation Sequencing Diagram DOI FSAM Version 1. 0 105

Transition Plan Milestones – [Core] Segment Transition Plan Milestones Segment Code Segment Name Segment Description Organizational Owner Agency Code Segment Type Priority Segment? (Y/N) Segment Development Phase Milestone IT Investment, ID System or Program Segment Transition Plan Target Actual Dependency Milestone Description Completion ID Date Dependencies / Constraints FSAWG FSAM Version 1. 0 106

Recommendation Implementation Sequencing Plan FSAWG FSAM Version 1. 0 107

Segment Mappings – [Core] Segment Mapping Current / Target BRM Business Area SRM Service Domain IT Investment Mapping IT Investment UID (from Exhibit 53 if applicable) PARTed Program Name Program ID FSAM Version 1. 0 SRM Component TRM Mapping TRM Service Category TRM Service Area BRM Sub-Function SRM Mapping SRM Service Type IT Investment Name BRM Mapping BRM Line of Business TRM Service Standard IT Investment Description PARTed Program Associated IT Investment Associated Investment UID (from Investment Mapping) FTF Initiative Use Supported FTF Initiative Name or Used by Segment? (Y/N) Recreation One-Stop Gov. Benefits. gov E-Loans USA Services IRS Free File Disaster Assistance Improvement Plan E-Rulemaking Expanding Electronic Tax Products for Businesses Federal Asset Sales International Trade Process Streamlining Business Gateway Case Management Lo. B Consolidated Health Informatics/ Federal Health Architecture Geospatial One-Stop Disaster Management SAFECOM E-Vital Grants. Gov Grants Management Lo. B Geospatial Lo. B E-Training Recruitment One-Stop Enterprise HR Integration E-Clearance E-Payroll E-Travel Integrated Acquisition Environment E-Records Management Explanation for NOT Using the FTF Inititaive (if applicable) FSAWG 108

Segment Architecture Blueprint Document (incl. Sequencing Plan) – [Core] Modernization Blueprint FSAWG FSAM Version 1. 0 109

FSAM provides additional tools to support the document review and comment process Document Review Form Feedback Tracking and Action Report Feedback Date Document / Version ID Reviewer Section and Paragraph, Comment or Page No. Figure, Table Change Request or Other Reference Rationale Reviewer Title / Name Organization Email Feedback and/or Owner Phone No: Action Date Updated Completed Document and Version FSAWG FSAM Version 1. 0 110

Blueprint Executive Summary Presentation • At the end of Step 5, a presentation is prepared as part of the review with the core team and key stakeholders • The Modernization Blueprint is reviewed and approved • A record of decision (ROD) documents the core team approval • The Modernization Blueprint is ready to move forward into other governance processes for capital planning and investment review FSAM Version 1. 0 111

Enterprise Architecture Segment Reporting (EASR) Integration with FSAM Version 1. 0 112

Purpose of the Template • The Segment Template has been created to report information generated from the FSAM to meet OMB’s EA Assessment Framework 3. 0 Criteria EAAF 3. 0 FSAM Segment Template OMB EA Submission • Four main goals for this effort: o o Ensure agency segment architectures are generating results Identify opportunities for reuse and cross-agency collaboration Provide a format for architects to engage with business owners Provide updated, standardized segment information to OMB FSAM Version 1. 0 113

Segment Report Sections/Forms Form Description Identification Provides descriptive information about the Segment and its current state. Mappings Contains mappings of the Segment to the FEA and to Investments, Programs, and Cross-Agency Initiatives Performance Creates a comprehensive line of sight for Segment performance as well as financial and non-financial success stories attributed in whole or in part to the Segment Architecture Transition Planning Provides Segment Progress Milestones that track the development of a Segment within an Agency. These milestones may different from those found in the Exhibit 300 s as they focus on the activities that will take the Segment from Notional to Complete. Collaboration & Provides information on Business, Data, and Information System/Service Reuse by the Segment and Partners or other Reuse Stakeholders related to the Segment FSAM Version 1. 0 114

Four Stages of Segment Completion Notional – • Segment is defined and reported to OMB • Exhibit 53 Investments are aligned to the Segment Planned – • FEA, FTF, PARTed Programs, and E-Gov Mappings are included • Some Performance Metrics and Transition Milestones • Some Performance Metrics for PAR and PARTed Programs In-Progress – • Performance Milestones included from the ETP • Performance Metrics provided for all four performance forms • Initial set of reusable Data Entities and Exchanges Identified • Initial set of reusable Business Capabilities Identified • Initial set of reusable Information Systems Identified Completed – • Completed Segment has been signed off on by the mission/business owner • Current scope of completed segment may be less than the target scope • Template currently includes FEA mappings for the Target state • Additional documentation may be required when submitting to OMB FSAM Version 1. 0 115

Identification & Segment Mapping Forms Basic Segment Identification Information Segment Alignment / Mapping also includes FEA Reference Models FSAM Version 1. 0 116

Performance Form * FSAM Performance Scorecard requires identical information FSAM Version 1. 0 117

Performance Form • The Performance Form is intended to capture Segment Performance at multiple levels; o o Strategic Layer – High level metrics showing support of Agency Strategic Goals Segment Layer – Segment specific metrics such as Cost Savings and Avoidance Program Layer – Program and PART specific metrics Business Layer – IT Investment and Activity metrics based on the PRM Line of Sight • Segment Performance should leverage current performance architecture activities as indicated in the diagram below FSAM Version 1. 0 118

Transition Planning Form • Transition Planning is focused on showing the activities and milestones that help mature a Segment towards Completion • Sample Segment Development Milestones may include o o o Segment Architecture Document Development Business Process Reengineering Target Architecture Development System Retirement/Implementation Business Owner Sign-Off Segment Transition Plan Milestone IT Investment/ System/ ID Program/ etc… Segment Milestone Target Completion Date Actual Completion Date Dependant on Dependencies/ Milestone X Constraints FSAM Version 1. 0 119

Collaboration and Reuse Form Business Reuse • Reuse of other Segments • Major stakeholders Sys/Service Data Reuse • Business Capability/ Activity Reuse • Data Exchanges • Data Entity Reuse • Secondary IT Investment Mappings • System Service (SOA) Reuse FSAM Version 1. 0 120

FSAM includes artifacts designed to align with the Segment Architecture Template Corresponding FSAM Artifact Segment Identification Segment identification information is created in the EA-level processes that define and prioritize segments. Segment Mapping Form Segment Mappings Segment Performance Form Performance Scorecard Enterprise Transition Plan Form Transition Plan Milestones Segment Reuse Form Segment / Business / System / Service Reuse Data Reuse Stakeholders and their relationships FSAM Version 1. 0 121

Thank You! FSAM Version 1. 0 122