Federal Segment Architecture Methodology (FSAM): An Overview

Transcription

1 Information Resources Management College Federal Segment Architecture Methodology (FSAM): An Overview Dr. Stan Boddie & Prof. Matt Newman 1 a global learning community for government s most promising information leaders

2 Agenda Segment Definition OMB s EA Segment Reporting Requirements (EASR): Overview Federal Architecture Segment Methodology (FSAM): Overview Implications for DoD New EA Certificate Program Slide Content Sources 2

3 OMB FEAPMO s Segment Approach 3 Source: FEAPMO, FEA Practice Guidance, Dec 2006, pg 1-4

4 OMB Segment Architecture Definitions Enterprise Architecture: a management practice for aligning resources to improve business performance and help agencies better execute their core missions. An EA describes the current and future state of the agency, and lays out a plan for transitioning from the current state to the desired future state. Segment: Segments are individual elements of the enterprise describing core mission areas, and common or shared business services and enterprise services. Solutions Architecture: An architecture for an individual IT system that is part of a segment. A solution architecture is reconciled to the segment architecture above it. (DoD s definition is different) 4

5 What is a Segment? Pizza -- mmmmmm Enterprise People, Processes (LoBs), Technologies, etc combined, form the Enterprise Segment - a whole new meaning to slice Segment Segment is composed People, process, etc that support a Line of Business generally 5

6 Segment Architecture Definitions Core Mission Areas: Unique service areas that define the mission or purpose of the agency. Core mission areas are defined by the agency business model (e.g., tactical defense, air transportation, energy supply, pollution prevention and control, and emergency response). Common Business Services: Defined by the agency business model, business services include the foundational mechanisms and back office services used to achieve the purpose of the agency, e.g., inspections and auditing, direct loans, program monitoring, and financial management. Common Enterprise Services: Common or shared IT services that support core mission areas and business services. Enterprise services are defined by the agency service component model and include the applications and service components used to achieve the purpose of the agency (e.g., knowledge management, records management, mapping/gis, business intelligence, and reporting). 6 Source: FEAPMO, FEA Practical Guidance, Dec 2006, pg A-1

7 DoD s Interpretation of Segment DoDAF V2.0 Pre-decisional, Volume I identifies four types of architectures Capability Architecture are those types of architectures that define and describe specific capabilities required by the Department for business, procurement, and tactical operations. The capability architecture is considered segment architecture (pg 10) 7

8 Segment Identification Segment definition is a work in progress DoD segment submission totaled four (4) in contrast to non-dod cabinet-level agencies which ranged as high as 72. There are eight (8) Tier 1 Joint Capability Areas Observation based on DoD students course assignments, segments are viewed as: Part of a federated structure (quasiautonomous) Tend to be Service or Command centric 8

9 Purpose of the EA Segment Report The Segment Report 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 Report OMB EA Submission Four main goals for this effort: 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 * The FSAM Logical Data Model Supporting EA Reporting Requirements 9

10 EASR v1.1 Reporting Criteria 4 times per year, Agencies provide an EA Segment Report (EASR) for each segment identified within their Segment Portfolio Required reporting (worksheets) depends on maturity of each segment Notional, Planned, In-Progress, Complete February Initial May Completion August Use November Results EASR for all Segments Must complete only the first two forms EASR for all Segments EASR must be completed based on Segment Maturity Segment Documents uploaded to MAX EASR Updates based on Ex. 53 and Ex. 300 Submissions Segment Milestones Updated EASR Updates based on end of the year performance results Segment Milestones Updated Segment Milestones Updated

11 EASR v1.1 Reporting Sections 11

12 EASR v1.0 Reporting Criteria Segment Maturity Section Notional Planned In-Progress Complete Identification Segment Name Segment Description Agency OMB Segment Code Segment Type Segment Phase Segment Priority Segment Name Segment Description Agency OMB Segment Code Segment Type Segment Phase Segment Priority Segment Name Segment Description Agency OMB Segment Code Segment Type Segment Phase Segment Priority Segment Name Segment Description Agency OMB Segment Code Segment Type Segment Phase Segment Priority Mappings Investments (Exhibit 53/ITBRS) Programs (PART program inventory) Cross-Agency Initiatives (E-Gov/FTF) Investments (Exhibit 53/ITBRS) Programs (PART program inventory) Cross-Agency Initiatives (E-Gov/FTF) Investments (Exhibit 53/ITBRS) Programs (PART program inventory) Cross-Agency Initiatives (E- Gov/FTF) FEA RM Alignment o BRM o SRM o TRM Investments (Exhibit 53/ITBRS) Programs (PART program inventory) Cross-Agency Initiatives (E- Gov/FTF) FEA RM Alignment o BRM o SRM o TRM Performance Business Performance Strategic Performance (PAR) Program Performance (PART) Business Performance Strategic Performance (PAR) Segment Performance Program Performance (PART) Business Performance Transition Planning Segment Progress Milestones Segment Progress Milestones Collaboration & Reuse 12 Collaboration / Partners Business Reuse Data Reuse Info System / Service Reuse

13 Federal Segment Architecture Methodology: Background 13 Federal organizations, including 2 cross-agency initiatives participated 13 people on core team 34 people on sub-team 10 best practice presentations delivered 18 assessed best practices considered 78 analytical techniques cataloged Including 232 templates / examples Best Practices HUD - Segment Architecture Development Guidance / Work Product and Decision Templates DoD DoDAF 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 (v2) (Draft) FEA - Records Management Profile 13 13

14 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 14 14

15 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 15 15

16 Federal Segment Architecture Methodology 16

17 FSAM includes the steps for developing a Segment Architecture as well as hand-offs to Enterprise and Solution Architecture 17 17

18 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 Architecture CPIC Architecture CPIC Budget CPIC Execution 18 18

19 Walkthrough of FSAM Steps

20 Activities for Step 1: Determine Participants and Launch Project

21 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?

22 Activities for Step 2: Develop the Segment Scope and Strategic Intent

23 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?

24 Activities for Step 3: Define Business and Information Requirements

25 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?

26 Activities for Step 4: Define Conceptual Solution Architecture

27 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?

28 Activities for Step 5: Author the Modernization Blueprint

29 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?

30 Implications for DoD DoDAF Architectural Process 30

31 Implications for DoD DoD and OMB guidance methodologies are not the targeted at the same scope DoDAF Architectural process) Federal Enterprise Architecture Levels Scope? FSAM is focused at the segment level DoDAF Architectural process is more focused on the Enterprise 31

32 Implications for DoD Direct alignment? Direct alignment? 32

33 Implications for DoD Determine scope of architecture initiative Segment definition and reporting needs to be resolved and reconciled with the definition of Capability Architecture When selecting a work-product (model) for a DoDAF view consider the FSAM workproducts, in particular core work-products (fit-for-purpose OMB) In lieu of a specific or tactical EA methodology, consider the FSAM 33

34 New EA Certificate Program 34

35 Need for Change 35 Align certificates with three job tiers established in September 2008 by OPM s Job Standard for Information Technology Management (Architect, Enterprise Architect, Chief or Senior Enterprise Architect) and DoD s white-paper on Architect Competencies, Responds to maturation of EA discipline Addresses customer demand to educate and certify competency at each level more quickly One Tier > Three Tier

36 Architect Levels 36 Architect (Level I) Enterprise Architect (Level II) Chief Architect (Level III) Level I - Architects focus on the development of architectures. Their primary function is to develop architectures based on user requirements and input from subject matter experts. As Level I Architects mature, their experience should include the use of various modeling techniques and tools and experience with program or enterprise-level architecture development. Level II - Architects focus on the analysis and management of architectures. Their primary function is to analyze architectures for the purposes of integration, interoperability, gap analysis, risk assessment, leveragability, compliance, and business decision making. In addition to the analytics, manage the architecture program. As Level II Architects mature, their experience should include the use of various analysis techniques and programs or enterprise-level analysis and to lead areas within EA programs. Level III - Architects focus on leading organizational transformation through the discipline of EA. Their primary function is to lead an architecture effort through its entire lifecycle, from initiation to development to execution & implementation. As Level III Architects mature, their experience should include strategic analysis, transformation efforts, communication, and leadership of an enterprise-level architecture.

37 EA Certificate Program 37

38 Questions, Observations, Comments 38

39 Exhibit 53/300 Reporting FEA PMO Reporting Requirements Q2 Q3 Q4 Q1 Jan Feb Mar Apr May Jun July Aug Sep Oct Nov Dec Prep. of President s Budget EA Segment Reporting All Segments Identification & Mapping OMB develop initial draft Guidance (Circular A-11) All Segments Based on Maturity Agencies Select Upcoming Portfolio Using EA Agencies submit budget request to OMB All Segments Updates/Additions OMB Passback All Segments Updates/Additions Agency EA Self Assessment and EA Submission Success Stories and/or Case Studies OMB Review & Assessment of Agency EA Agencies Submit 1-2, OMB Shares w/ USG Completion Use Results OMB Feedback to Agency on EA Assessment Citizen-Centered, Results Driven Government 39