The document discusses the General Endeavor Management (GEM) approach for building and managing enterprise architectures. GEM provides a methodology for modeling all aspects of an enterprise, including locations, organizations, functions, processes, resources and requirements. It aims to create a unified view of both current and planned enterprise operations and intelligence to support strategic management and decision making. GEM can be applied at any level from individual to enterprise-wide management.

1. Using the General Endeavor Management (GEM) Approach Leveraging, Expanding, and Unifying OMB FEA and DoDAF Compliant Enterprise Architectures Orientation and Discussion Slides Roy Roebuck 703-598-2351 [email_address]

2. GEM Start Point: An Enterprise is Treated As A Single Object In a Dynamic Environment 06/08/09 Enterprise = a purposeful endeavor Value-Chains Opportunity and Competition / Threat / Risk Strength and Weakness / Vulnerability Enterprise 1 Enterprise 2 Enterprise 3

3. EA Supports Leadership with Enterprise Cohesion and Coherence B. Management (By Executives and Staffs) A. Leadership 06/08/09 Cohesion of Intention By Managing a Coherent Configuration (Endeavor Architecture) (EA): 1. Components (Subjects) 1.1. Locations 1.2. Organizations 1.3. Organization Units 1.4. Functions 1.5. Processes 1.6. Resources 2. Relations 2.1. Requirements 2.2. Questions and Answers Measured and Adjusted Progression Towards Defined Future State 1 Where we are today… (As-Is Disorder) (Management) 2 Where we want to go… (To-Be Order) (Leadership) 3 How we’ll get there (Migration) (Management) Shortfalls and deficiencies Gaps and Overlaps Transition Plans

4. A Subject’s Context and Content Context Content Context Context Content Content Container or Predecessor Subject X Component or Successor Subject Y Base Subject Child Subject Parent Subject Parentage Inheritance Descendant Inheritance Past Change Future Change Present Change

5. Direct and Indirect Subject Connections Basic Modeling Technique Subject A (Noun) is directly related to (verb) Subject B (noun) Subject C (noun) is directly related to (verb) is indirectly related to (has inferred or transitive relationship) (verb) Context Content Context Content Context Content

6. The Enterprise Object Value Chain Relationship Elements 5. Supplier (Input ) 2.1 Products 2.2 Process 2.3 Structure 2.4 Culture 2. Your Enterprise (Internal, Insource , and Outsource Activity) 1. Customer (Output, Outcome) 4. Partner (Output, Mechanism) 3. Authority (Control) 6. Public ( Output, Control) Perform, Measure, and Improve 4. Partner (Input, Mechanism) 6. Public (Input, Control) Predecessor Value-Chain Links Successor Value-Chain Links Internal Value-Chain Links a. Expectation and e. Satisfaction b. Requirement c. Production d. Provision

8. What Are The Functions and Products of GEM? 06/08/09 GEM Functions 1. Conduct operations under access control 2. Learn from operations using intelligence management functions 3. Inventory intelligence (metadata and data) 4. Organize intelligence (Knowledge Management) 5. Implement resource distribution, access control, security architecture, simulations, and virtual applications 1. Operation Management 2. Intelligence Refinement 3. Intelligence Inventory 4. Intelligence Structure 5. Resource Distribution and Access Provisioning Enterprise Operations Enterprise Intelligence GEM Products A. Operational experience B. Operational/analytical results and data C. Vulnerability/Risk Assessment D. Extracted intelligence, managed metadata and data, intelligence integration/fusion E. Management intelligence, EA, and requirements for asset access and distribution F. Vulnerability/Risk Identification G. Intelligence distribution for concurrent operations (i.e., cooperation), analysis, and decisions G A B D E C F

10. Enterprise Basic Questions And Assertion Structure 06/08/09 RESOURCE CONTEXT What goes into ___? What results from ___? What constrains ___? What enables ___? PROCESS CONTEXT How do we ___? FUNCTION CONTEXT What is done for ___? Why is ___ done? ORGANIZATION UNIT CONTEXT Who does ___? Who supplies ___? Who produces ___? Who receives ___? ORGANIZATION CONTEXT Who is responsible for ___? Who has the authority to ___? Who has the resources for ___? LOCATION CONTEXT Where is ___? REQUIREMENT LIFE CYCLE CONTEXT When is ___? How many ___? How often are ___? How much is ___? BASIC QUESTIONS IN CONTEXT (User Query of GEM Fact Table) SUBJECT Location Data Organization Data Organization Unit (Performer) Data Function Data Process Data Resource Data Requirement Life Cycle Data

11. Enterprise Management (EM) Facets 06/08/09 LOCATION FACET ORGANIZATION FACET ORGANIZATION UNIT (PERFORMER) FACET FUNCTION FACET PROCESS FACET RESOURCE FACET REQUIREMENTS (Facet Relations)

12. Interoperable Enterprise Management (EM) Through Merged Terminology (Taxonomic Facets) and Architecture 06/08/09 Unified Management Terminology and Architecture Domain B Terminology Domain A Terminology Domain C Terminology Domain D Terminology

13. Value Lattice (GEM Ontology and Ecology) Many Locations Many Organizations Many Organization Units Many Functions Many Processes Many Resources Many Requirements Increase value by knowing and optimizing the number of relationships for a given situation. to to to to to to Managed Relations and Attributes

14. GEM-EMA Value Lattice (Subjects and Linkages) 06/08/09 GEM-EMA .01 .02 .03 .04 .05 .06 LOCATION CATALOG ORGANIZATION CATALOG ORGANIZATION UNIT (OFFICE/POSITION) CATALOG FUNCTION CATALOG PROCESS CATALOG RESOURCE CATALOG MISSION CATALOG .07 1.0 ENDEAVOR CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS Location Contains Organization Organization Establishes OU OU Accomplishes Function Function Applies Process Process Produces/Consumes Resource Resource Satisfies Requirement Organization Occupies Location OU Perform Mission Function Justifies OU Process Achieves Function Resource Inputs-To/Results-From Process Requirements are Satisfied by Resource

16. Enterprise Functions (Both Reusable and Unique Processes and Content Across Peers and Subordinates) Executive / Direction / Command Functions Organization, Function, Program, and Project Mission Vision Goals Objectives (Performance Measures, Service Levels) Strategies (Policy, Process, Plan) Security Executive / Measurement / Control Functions Process Control Points Transaction with Metric Collection/Processing Data Elements Table Fields Field Entry Criteria/Security Field Values (Measured Facts) Production Functions Baseline Operations (As-Is, ABC) Products (Goods/Services) Activities/Systems Costs/Benefits Initiatives (Proposed Operations, FEA) Investment Costs Performance Impacts Operations Cost Impacts Resource Functions Human (Person/Skill) Intelligence Result/Decision/Knowledge/Information Semantics/Data/Signals/Event/Situation Finance Materiel Facilities Services (Outsourced Process) Time Space Energy Data Warehouse Data Analysis Decision Support Executive Information Enterprise Architecture Knowledge Models Executive Functions (Direction / Command) (Value-Chain Efforts) Production Functions (Efforts for External Customers) Executive Functions (Measurement / Control) (Value Stream Efforts) 80%+ Reusable (GEM Focus) 20% Reusable (80% Mission Unique) (Improve With GEM) 80%+ Reusable (GEM Focus) 80%+ Reusable (GEM Focus) Data Models Resource Control Systems Resourcing Functions (Efforts for Internal Customers) Resource Information Systems

17. Managing an Enterprise 06/08/09 5 4

18. GEM and Enterprise Management Maturity (EMM) Levels 06/08/09 EMM Level 5: Real-Time Enterprise Management EMM Level 4: Enterprise Operational Management GEM provides escalating levels for building and integrating a mature enterprise management capability. EMM Level 3: Enterprise Architecture EMM 2 EMM 1 EMM 3 EMM 4 EMM 5 Growing the Capability Tree GEM can begin in any part of the enterprise and grow outward, but starting with the whole enterprise is recommended for speedy, economic, effective, and efficient results. EMM Level 1 System Architecture A EMM Level 2: Functional Architecture X EMM Level 1 Database Architecture B EMM Level 1 Software Architecture C EMM Level 2: Program Architecture Y EMM Level 1 Project Architecture D

26. GEM Supports Enterprise Leadership and Management Functions - Progression from Current Disorder to New Order, With Cohesion Value-Lattice (Integrated Value Chains) Operating Environment Mission Vision 5. Tightening “Acceptable Performance” Operation Indicators from Lessons Learned (Intelligence Refinement) Risk and Vulnerability Assessment, Performance Measurement, And Adjustments Objective Criteria Goal Strength, Weakness, Opportunity, and Threat Awareness 4. Evolving Operation Strategy To Close Gaps and Reduce Overlaps (Adaptation Decisions) 3 How We’ll Get There Now (Transformation, Control) Leadership Provides Cohesion (i.e., Control) By Managing The Configuration Of Enterprise Architecture” 1. Enterprise Components 1.1. Location 1.2. Organization 1.3. Organization Unit 1.4. Function 1.5. Process 1.6. Resource 2. Component Relations 2.1. Categorization 2.2. Containment 2.3. Sequence 2.4. Version 2.5. Equivalence 2.6. Variation 2.7. Reference 3. Capability Requirements 3.1. Conceptual 3.2. Specified 3.3. Authorized 3.4. Funded 3.5. Implemented 3.6. Operational 3.7. Disposed Leadership Provides Measured and Adjusted Progression , Transforming Enterprise Into An Intended Future State (i.e., Command) Leadership Decision Management Leadership and Management of the “Operational Part of Architecture” Both Depend On Organization of Data (i.e., “the Intelligence Part of Architecture”) About The Enterprise and Its Environment 1 Our Status Yesterday… (As-Is Disorder) 2 Our Intended Status Tomorrow… (To-Be Order, Command)

27. Implementing GEM: Aligning Missions, Functions, and Resources (e.g., IT) Typical Basic EA Initial Efforts EA Extension Efforts Using Extended EA for Integrated Process Improvement, Business Process Modeling and Management, and Activity-Based Costing (Budgeting) Using Basic EA for Solution Architecture And Design Compliance Using Extended EA for Program / Project / System / Software Validation and Verification (V&V) and Security Certification and Accreditation (C&A)

28. GEM-EMA Subjects and Linkages, Compared to the OMB FEA and Agency IT Management 06/08/09 GEM-EMA .01 .02 .03 .04 .05 .06 LOCATION CATALOG ORGANIZATION CATALOG ORGANIZATION UNIT (OFFICE/POSITION) CATALOG FUNCTION CATALOG PROCESS CATALOG RESOURCE CATALOG REQUIREMENT CATALOG .07 1.0 ENDEAVOR CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS 1. BRM (Assigned Functional Missions + Assumed Supporting Functions) 2 and 7. PRM (Strategic Mgmt, Ops & Priorities, Portfolios, Invest. Strategies, Programs, Projects) 4. SRM (Best Practice, Re-usable Info Products and Processes) 3. DRM (Data Description, Context, and Sharing. Metadata Management, Shared Controlled Vocabulary) 5. TRM (Technology Catalog and Qualifying Products) 6.5.1 Agency Physical IT 6.5.1.1 Agency Systems 6.5.1.2 Agency Infrastructures OMB FEA Has Partial Endeavor Coverage ORGANIZATION AND FUNCTION, STAFF STRUCTURE REQUIRED FUNCTIONAL RESOURCES (As Capabilities) Basic Relations or Rules (Axioms) Categories (Data, Metadata, Taxonomies) World View (Process + Data + Rules, Ontology) Containment-Relations (Part-Of)

29. GEM-EMA Subjects and Linkages, Extending the OMB FEA to Govern All Resources 06/08/09 GEM-EMA .01 .02 .03 .04 .05 .06 LOCATION CATALOG (RM) ORGANIZATION CATALOG (RM) ORGANIZATION UNIT (OFFICE/POSITION) CATALOG (RM) FUNCTION CATALOG (RM) PROCESS CATALOG (RM) RESOURCE CATALOG (RM) REQUIREMENT CATALOG (RM) .07 1.0 ENDEAVOR CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS CONTAINS 1. Business Architecture (BRM + Extension) (Assigned Functional Missions + Assumed Supporting Functions) 2 and 7. PRM (Strategic Mgmt, Ops & Priorities, Portfolios, Invest. Strategies, Programs, Projects) 3. SRM (Best Practice, Re-usable Info Products and Processes) 4. DRM (Metadata, Controlled Vocabulary) 5. TRM (Technology Catalog and Qualifying Products) 6. Resources over their life cycle . 6.1 People 6.2 Intelligence 6.3 Funds 6.4 Skills 6.5 Materiel 6.5.1 Physical IT 6.5.1.1 Systems 6.5.1.1.1 Software Systems 6.5.1.2 Infrastructure 6.5.2 Goods 6.6 Facilities 6.7 Services 6.8 etc. FEA + Extension for Functional Context and All Budgeted Resources Basic Relations or Rules (Axioms) Categories (Data, Metadata, Taxonomies) World View (Process + Data + Rules, Ontology) Containment-Relations (Part-Of)

30. Enterprise Architecture – Main US Federal (OMB FEA and Defense) Elements 06/08/09 Technology Infrastructure, Systems, and Devices Testing, Development, and Deployment Technology Demonstrations, Prototypes, Pilots, Operation, and Maintenance Technology Architecture (TA) (Including FEA Technical Reference Model - TRM ) Data Architecture (DA) (Including FEA Data Reference Model - DRM ) Application Architecture (AA) (Including FEA Service Component Reference Model - SRM ) Business Architecture (BA) (Including FEA Performance Reference Model – PRM , and Business Reference Model - BRM ) BA- BRM Elements BA- PRM Elements Function Capability Service Components Technology Service Components Management Consulting and Resource Management Services IT Services DoDAF OV DoDAF AV DoDAF TV DoDAF SV Security Architecture, TOC, Portfolio Mgmt, Business Case

32. GEM-EMA – Recurring Procedural Flow, Overlaid with OMB FEA Reference Model Blocks, DoDAF Views, and Common Business Improvement Efforts (A Solution Development Life Cycle (SDLC), Operating Concurrently For All Enterprise Organizations, Functions , Programs, and Projects) 06/08/09 4. Function 6. Policy 15. Process 16. Procedure 17. Templates 19. Metadata 21. Data 18. Constraints, Rules, and Principles 8. Authority 26. Budgets 27. Budget Lines 22. Equipment, Supplies, and Service (IT and Others) 13. Strategies Definitions & Portfolios 14. Plans 29. Functional Programs & Projects 32. Review Performance 28. Expense Elements 5. Mission 9. Vision 10. Goals 11. Objectives 12. Performance Indicators 30. Technology Infrastructure, Systems, and Devices Testing, Development, and Deployment (TA) 31. Functional Operations and Technology Inventory, Prototyping, Operation, and Maintenance (TA) 7. Responsibility 23. Technology Catalog 24. Technology-Specification and Insertion 20. Data Dictionary Technology Architecture (Including Technical Reference Model - TRM ) Data Architecture (Including FEA Data Reference Model - DRM ) Application Architecture (Including FEA Service Component Reference Model - SRM ) Business Architecture (Including FEA Performance Reference Model – PRM, and Business Reference Model - BRM) 25. Requirements BA-BRM Elements BA-PRM Elements Enterprise Management Services IT Services 3. Organization Unit 2. Organization 1. Location 7. Performance Targets 15.1 Vocabulary 19.1 Key Words 19.2 Taxonomy 19.3 Concept Maps 19.4 Semantic Models And Data Models 19.5 Ontologies 21 Knowledge Bases 25 Functional Requirements Function Capability Service Components DoDAF OV DoDAF AV DoDAF TV DoDAF SV Security Architecture, TOC, Portfolio Mgmt, Business Case