1. Version 2.2 1 System Engineering Process Improvement In Today’s Life Cycle Context Mike Bloom, Joe Duquette Organization: ESC/EN Version 2.2

2. 2 “The only source of knowledge is experience” A. Einstein We Need to Leverage Our Process Experience and Use It To Succeed

3. Version 2.2 3 P urpose D efine the life cycle and life cycle attributes that the EN CMMI System Engineering Process Improvement Program will apply to and operate in. The life-cycle for the C 2 Product Line is unique and complex

4. Version 2.2 4 Major ESC Life Cycle Challenges Acquisition Environment Acquisition Environment - Shared responsibilities Enterprise Architecture Enterprise Architecture - External requirements beyond the product function Life Cycle and Spiral Life Cycle and Spiral - Simultaneous life-cycle phases - including O&M Stakeholders Stakeholders - Many external stakeholders - continuously involved Our System Engineering Processes Need to Address These Challenges

5. Version 2.2 5 We are spending increasing effort on eachWe are spending increasing effort on each of our programs responding to daily crises and asynchronous initiatives - it is consuming We need to devote our energy on the programs to product innovation not process reinvention. EN’s CMMI based processes are built toEN’s CMMI based processes are built to meet the C 2 product line challenges ESC Life Cycle Focus

6. Version 2.2 6 Overview Architectures Life Cycle Business Model StakeholdersRelationships I II IIIIV Environment

7. Version 2.2 7

8. 8 Acquisition Operations Sustainment Contractors Independent Organizations FormalCommunications Large Defense Budgets 80s Technology Business Environment - 1980s Stovepipe Systems Time and Money Permitted Independent Organizational Processes

9. Version 2.2 9 Contractors Operations Sustainment Acquisition Smaller Defense Budgets IPTs COTS Rapid Technology Change Business Environment - Today Interdependent Organizations System of Systems Integration Shared Data and Responsibilities Organizational Processes Today Must Provide for Shared Data and Responsibilities

10. Version 2.2 10 How Do CMMI Based Processes Help With Shared Responsibilities? Both industry and government are developing processes under the same framework DoD will most likely encourage process improvement through CMMI - AFMC will be doing likewise Process Areas are envisioned to be shared or not shared - depending on the negotiated arrangement between the program office and the contractor Same Language DoD and Industry Wide Supports Process Sharing

11. Version 2.2 11 Engineering –Requirements Management –Requirements Development –Technical Solution –Enterprise Integration –Verification –Validation Process Management –Process Focus –Process Definition –Training –Process Performance –Innovation & Deployment –Quantitative Management Project Management – –Project Planning – –Monitoring & Control – –Supplier Agreements – –Integrated Management – –Risk Management Support – –Configuration Management – –Quality Assurance – –Measurement & Analysis – –Causal Analysis & Resolution – –Decision Analysis & Resolution E M S P CMMI Process Area Categories

12. Version 2.2 12 Shared Responsibilities Requires Process Sharing

13. Version 2.2 13 Shared Processes Require Shared Data Project Engineering View t Project Management View t Project Support View t User ORD(s) View t AFOTEC Testing View t SM Funding View t Shared Data Assures Accurate and Timely Information Exchange Among Stakeholders Shared Data from Shared Processes Engineering Processes Support Processes Management Processes

14. Version 2.2 14

15. Version 2.2 15 Architecture Is... Architecture is a set of tenets used to harmonize designArchitecture is a set of tenets used to harmonize design choices across multiple disciplines used to solve problems in a specified domain Architecture Imposes Requirements Beyond a Program’s Functional Capabilities Architecture is used to manage the complexity of theArchitecture is used to manage the complexity of the information system capability in a domain Architecture impacts the individual system by showingArchitecture impacts the individual system by showing the required relationship to other systems in the domain and requiring all systems to adhere to tenets to implement the relationship

16. Version 2.2 16 Program Requirements POM Cycle, Budget Cuts, Management Considerations, Support Resource Inadequacy, and Political Considerations Program Constraints Architectures and Program Constraints Both Constrain and Define the Individual Program Approach Functional Requirements plus... Enterprise Architecture Program Architecture State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “To Be” System State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation Transition State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “As Is” System State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “To Be” System State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation Transition State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “As Is” System Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “To Be” Technical Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements Transition Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “As Is” Technical Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “To Be” Technical Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements Transition Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “As Is” Technical “To Be” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model Transition Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model “As Is” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model “To Be” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model Transition Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model “As Is” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model

17. Version 2.2 17 Decision Analysis and Resolution Requirements Development SOS Integration & Delivery Project Planning Supplier Agreement Management Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Causal Analysis and Resolution Product Control Enterprise Integration Mission Shortfalls Directives, Standardization, Roadmaps Constraints, Processes Need to Address... Enterprise Integration is a “Custom” C 2 Overarching Process Area Influencing Program Requirements

18. Version 2.2 18 Key Concurrent Up Front Program Activities Decision Analysis and Resolution Requirements Development SOS Integration & Delivery Project Planning Supplier Agreement Management Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Causal Analysis and Resolution Product Control Enterprise Integration Mission Shortfalls Directives, Standardization, Roadmaps Constraints, CMMI Based Engineering Process Improvement Addresses Key Concurrent Up Front Activities Processes Need to Address...

19. Version 2.2 19 Decision Analysis and Resolution Requirements Development SOS Integration & Delivery Project Planning Supplier Agreement Management Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Causal Analysis and Resolution Product Control Enterprise Integration Mission Shortfalls Directives, Standardization, Roadmaps Constraints, Decision Analysis and Resolution Requirements Development Project Planning Technical Solution Product Integration Validation Requirements Management Configuration Management Project Monitoring and Control SoS Integration and Delivery Risk Management Integrated Project Management Enterprise Integration Architecture Impact On Our CMMI Based Engineering Process Improvement Processes Need to Address...

20. Version 2.2 20 Decision Analysis and Resolution Requirements Development SOS Integration & Delivery Project Planning Supplier Agreement Management Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Causal Analysis and Resolution Product Control Enterprise Integration Mission Shortfalls Directives, Standardization, Roadmaps Constraints, Requirements Development Project Planning Requirements Management Risk Management Enterprise Integration Chief Engineer Key Process Areas Include CMMI Based Engineering Process Improvement Processes Need to Address...

21. Version 2.2 21 CMMI Fits Our Needs ESC “Custom” Process Area for Enterprise Integration CMMI explicitly addresses key up front project processes CMMI accommodates Architecture impacts on the process implementation at ESC CMMI provides for key processes for ESC/EN execution of Chief Engineer function to include: –Requirements Development and Management –Risk Management –Enterprise Integration –Project Planning CMMI

22. Version 2.2 22 Life Cycle Business Model

23. Version 2.2 23 Systems Acquisition (Engineering and Manufacturing Development, Demonstration, LRIP & Production) Concept & Technology Development A System Development & Demonstration B Production & Deployment OT&E FRP Decision Review C Operations & Support FOC Pre - Systems Acquisition IOC Sustainment BLOCK 2 BLOCK 3 System Life Cycle Advocacy & Planning Acquisition Strategy Package Development Mission Integration Operations & Support Funding & Direction Contract Award DT&E Complete Depot Start System Disposal Program Life Cycle

24. Version 2.2 24 Program Life Cycle Definition Concept Definition Acquisition Strategy Package Development Mission Integration Operations & Support

25. Version 2.2 25 In the C 2 World Definition Concept Definition Ops Architecture Ops Architecture User Requirements User Requirements Investment Funding Investment Funding Experimentation Experimentation ATDs & ACTDs ATDs & ACTDs Transition Decisions Transition Decisions Experiment on Next Generation Sustain the Legacy System(s) In any Program All Four Phases Can Be Running Concurrently Package Development Acquisition Strategy and System Architecture System Architecture Product Requirements Product Requirements Technology Change Technology Change Design & Test Design & Test Define, Design, Define, Design, and Test New and Test New Capabilities Capabilities Fielding Fielding Decisions Decisions Mission Integration Tech Architecture Tech Architecture Interoperability Interoperability Infrastructure Infrastructure Certification Certification Previous Versions Previous Versions Other Systems Other Systems Ops Environment Ops Environment Shortfall Fixes Shortfall Fixes Operations & Support “As Is” Architectures “As Is” Architectures Operational Changes Operational Changes User Feedback User Feedback Operations Budgeting Operations Budgeting System Employment System Employment Parallel Operations Parallel Operations User Feedback User Feedback Plug and Play Plug and Play Mission Shortfall Fixes Mission Shortfall Fixes Life Cycle Detail

26. Version 2.2 26 Definition Concept Definition Acquisition Strategy Package Development Mission Integration Operations & Support Program Life Cycle - Multiple Types of Spirals ATD Experiment ACTD Program Direction Change New Contract Action Functional or Performance Baseline Change Beta or Development Only COTS Product Integration Plug & Play or Bug Fix

27. Version 2.2 27 Spiral N+1 User Priority Legacy Architecture Development Sequencing Risk/ Opportunity Technology Schedule Operational Evolution Requirements Baseline Political Climate Budget CONOPS Implied Legacy Requirements Individual Spiral Considerations Engineering Processes Must Accommodate A Complex Set of Variables

28. Version 2.2 28 System Engineering Processes Need to Have Enterprise Focus and Life Cycle Applicability Transition to Development ? Stop Concept Definition Concept Planning Budgeting Priority Concept Definition Contracting Activity Execution Assessment Experiment Planning Integration Only ? Yes No Try Again? Yes Plug & Play ? Traditional System Engineering Focus Yes Mission Integration Enterprise Planning Budgeting Priority Contracting Production/Deploy Integration Execution Assessment & Certification Shortfalls ? Operations SoS Requirements and Ops Architecture Version Planning Infrastructure Mod Application Mod Stop Operations & Support O&S Planning Maint Fix Budgeting Priority Mod Requirements Definition Contracting Mod Development Execution Assessment & Certification Mod Deployment Planning Deployment Operations Shortfalls ? Yes Stop Yes Acquisition & Development Planning Fielding Decision Budgeting Priority Requirements Definition Contracting Development Execution Assessment & Certification Package Planning Another Spiral Stop A Program’s Engineering Scope

29. Version 2.2 29 Transition to Development ? Stop Concept Definition Concept Planning Budgeting Priority Concept Definition Contracting Activity Execution Assessment Experiment Planning Integration Only ? Yes No Try Again? Yes Plug & Play ? Yes Mission Integration Enterprise Planning Budgeting Priority Contracting Production/Deploy Integration Execution Assessment & Certification Shortfalls ? Operations SoS Requirements and Ops Architecture Version Planning Infrastructure Mod Application Mod Stop Operations & Support O&S Planning Maint Fix Budgeting Priority Mod Requirements Definition Contracting Mod Development Execution Assessment & Certification Mod Deployment Planning Deployment Operations Shortfalls ? Yes Stop Yes Acquisition & Development Planning Fielding Decision Budgeting Priority Requirements Definition Contracting Development Execution Assessment & Certification Package Planning Another Spiral Stop Initial Processes Cut Across The Life Cycle

30. Version 2.2 30 Transition to Development ? Stop Concept Definition Concept Planning Budgeting Priority Concept Definition Contracting Activity Execution Assessment Experiment Planning Integration Only ? Yes No Try Again? Yes Plug & Play ? Yes Mission Integration Enterprise Planning Budgeting Priority Contracting Production/Deploy Integration Execution Assessment & Certification Shortfalls ? Operations SoS Requirements and Ops Architecture Version Planning Infrastructure Mod Application Mod Stop Operations & Support O&S Planning Maint Fix Budgeting Priority Mod Requirements Definition Contracting Mod Development Execution Assessment & Certification Mod Deployment Planning Deployment Operations Shortfalls ? Yes Stop Yes Acquisition & Development Planning Fielding Decision Budgeting Priority Requirements Definition Contracting Development Execution Assessment & Certification Package Planning Another Spiral Stop Initial Processes Cut Across The Life Cycle

31. Version 2.2 31 Decision Analysis and Resolution Requirements Development SOS Integration & Delivery Project Planning Supplier Agreement Management Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Causal Analysis and Resolution Product Control Enterprise Integration Mission Shortfalls Directives, Standardization, Roadmaps Constraints, Continuous Life Cycle Process Spiral Development Is the Cyclic Application of a Set of Standard Engineering Processes Over the Entire Life Cycle Until System Disposal

32. Version 2.2 32 StakeholdersRelationships

33. Version 2.2 33 Contractors Fewer and Bigger ID/IQ Contracts Fewer New Starts Out-sourced Work View CMMI as Imperative Operations Smaller Force Coalition Operations Interoperable Systems Increased OPSTEMPO Changing Missions Changing Threats CONUS Based Global Commitments Sustainment Lean Logistics Experience Drain Technology Pace Outsourced Work COTS vs MILSPEC Smaller Workforce Just-In-Time Supply Contractor Logistics Support Increased “Command Support” Stakeholder Considerations in Today’s Environment Acquisition System of System Demands Spiral Development & EA Constant Initiative Flow Increased ACQTEMPO Outsourced Workforce Lifecycle Management Impatient Customers Acquisition Reform “TSPR” Contracts Experience Drain Smaller SPOs Partnering & Shared Processes 2000’sInterdependentOrganizations

34. Version 2.2 34 Must be involved Certification Congress Contractor Customer Deployment DOD Policy Acquisition Agency Experimentation Industry Legal / Contracting Service HQ & JCS Safety Sustainment Test Training User May be involved Concept & Technology Development A System Development & Demonstration B Production & Deployment FRP Decision C IOC Support FOC B Production & C Stakeholders Spiral Development Involves the Same Set of Stakeholders in the Conduct of Standard Engineering Processes Over the Entire Life Cycle Until System Disposal

35. Version 2.2 35 Tailored CMMI Project Management Project Planning (G) Project Monitoring and Control (S) Supplier Agreement Management (G) Integrated Project Management (S) Risk Management (S) Engineering Requirements Management (S) Requirements Development (G) Technical Solution (S) Product Integration (S) Product Verification (S) Validation (G) Support Configuration Management (S) Process and Product Quality Assurance (C) Measurement and Analysis (S) Causal Analysis and Resolution (S) Decision Analysis and Resolution (S) Government (G) [User, SPO, Test] Contractor (C) Shared (S) Acquisition Strategy and / or Life Cycle Phase System Engineering Execution Process Allocation Notional* Allocation of Process Responsibility Organizational Process Management Process Focus (S) Process Definition (S) Innovation and Deployment (S) Training (S) Process Performance (S) Quantitative Management (S) Core Group Infrastructure Responsibilities Conscious Allocation * Can be changed depending on business model or acquisition strategy Shared Responsibilities Requires Sharing Process

36. Version 2.2 36 Transition to Development ? Stop Concept Definition Concept Planning Budgeting Priority Concept Definition Contracting Activity Execution Assessment Experiment Planning Integration Only ? Yes No Try Again? Yes Plug & Play ? Yes Mission Integration Enterprise Planning Budgeting Priority Contracting Production/Deploy Integration Execution Assessment & Certification Shortfalls ? Operations SoS Requirements and Ops Architecture Version Planning Infrastructure Mod Application Mod Stop Operations & Support O&S Planning Maint Fix Budgeting Priority Mod Requirements Definition Contracting Mod Development Execution Assessment & Certification Mod Deployment Planning Deployment Operations Shortfalls ? Yes Stop Yes Acquisition & Development Planning Fielding Decision Budgeting Priority Requirements Definition Contracting Development Execution Assessment & Certification Package Planning Another Spiral Stop Stakeholders Cut Across The Life Cycle Congress Customer DOD Policy Acquisition Agency Experimentation Service HQ & JCS Safety User Certification Congress Contractor Customer Deployment DOD Policy Experimentation Acquisition Agency Industry Legal/Contracting Service HQ & JCS Safety Sustainment Test Training User Certification Contractor Deployment Experimentation Acquisition Agency Industry Service HQ & JCS Safety Sustainment Test Training User Customer Contractor Acquisition Agency Experimentation Industry Legal/Contracting Safety Sustainment Test Training User

37. Version 2.2 37 Transition to Development ? Stop Concept Definition Concept Planning Budgeting Priority Concept Definition Contracting Activity Execution Assessment Experiment Planning Integration Only ? Yes No Try Again? Yes Plug & Play ? Yes Mission Integration Enterprise Planning Budgeting Priority Contracting Production/Deploy Integration Execution Assessment & Certification Shortfalls ? Operations SoS Requirements and Ops Architecture Version Planning Infrastructure Mod Application Mod Stop Operations & Support O&S Planning Maint Fix Budgeting Priority Mod Requirements Definition Contracting Mod Development Execution Assessment & Certification Mod Deployment Planning Deployment Operations Shortfalls ? Yes Stop Yes Acquisition & Development Planning Fielding Decision Budgeting Priority Requirements Definition Contracting Development Execution Assessment & Certification Package Planning Another Spiral Stop Stakeholders Cut Across The Life Cycle Congress Customer DOD Policy Acquisition Agency Experimentation Service HQ & JCS Safety User Congress Contractor Customer Deployment DOD Policy Experimentation Acquisition Agency Industry Legal/Contracting Service HQ & JCS Safety Sustainment Test Training User Certification Contractor Deployment Experimentation Acquisition Agency Industry Service HQ & JCS Safety Sustainment Test Training User Contractor Acquisition Agency Experimentation Industry Legal/Contracting Safety Sustainment Test Training User

38. Version 2.2 38 Conclusion Architectures Life Cycle Business Model StakeholdersRelationships I II IIIIV Environment

39. Version 2.2 39 Conclusion Acquisition Environment Environment Acquisition Environment Challenge Acquisition Environment Challenge - - Interdependent Organizations - - Shared Responsibilities - - Shared Data - - Organizational Processes Today Must Provide for Shared Data and Responsibilities How Does CMMI Help How Does CMMI Help - - Provides a Common Language - - Developed by Both DoD and Industry - - Used by Both DoD and Industry - - Supports Process Sharing EN CMMI-Based Processes Facilitate Shared Responsibilities

40. Version 2.2 40 Architectures Conclusion Enterprise Architecture Enterprise Architecture Challenge Enterprise Architecture Challenge - - Architecture Imposes Requirements Beyond a Program’s Functional Capabilities - - Architectures Constrain and Define the Individual Program Approach - - Need “Custom” C 2 Enterprise Integration Process How Does CMMI Help How Does CMMI Help - - Provides for ESC “Custom” Process Area for Enterprise Integration - - Explicitly Addresses Key up Front Project Processes - - Accommodates Architecture Impacts on ESC Process Implementation - - Provides for Key Processes for ESC/EN Execution of Chief Engineer Function EN CMMI-Based Processes Accommodates Requirements Beyond the Product Function

41. Version 2.2 41 Life Cycle Business Model Conclusion Life Cycle and Spiral Life Cycle and Spiral Challenge Life Cycle and Spiral Challenge - - Ability to Accommodate All Four Life Cycle Phases Running Concurrently - - Accommodate A Complex Set of Variables - - System Engineering Processes Need Enterprise Focus and Life Cycle Applicability How Does CMMI Help How Does CMMI Help - -Provides for a Cyclic Application of a Set of Standard Engineering Processes Over the Entire Life Cycle Until System Disposal EN CMMI-Based Processes Provide For Simultaneous Life-Cycle Phases - Including O&M

42. Version 2.2 42 StakeholdersRelationships ConclusionStakeholders Life Cycle and Spiral Challenge Life Cycle and Spiral Challenge - - Interdependent Organizations Require Shared Responsibilities - - Shared Responsibilities Require Shared Processes - - Shared Processes Require Maximum Stakeholder Involvement How Does CMMI Help How Does CMMI Help - - Provides Common Processes That Incorporate The Stakeholders Across the Life Cycle and Insures That The Appropriate Stakeholders Are Involved As Appropriate As the Program Spirals EN CMMI-Based Processes Provide For The Many External Stakeholders and Continuous Involvement

43. Version 2.2 43 Major ESC Life Cycle Challenges Acquisition Environment Acquisition Environment - Shared responsibilities Enterprise Architecture Enterprise Architecture - External requirements beyond the product function Life Cycle and Spiral Life Cycle and Spiral - Simultaneous life-cycle phases - including O&M Stakeholders Stakeholders - Many external stakeholders - continuously involved EN CMMI-Based Processes Address These Challenges

44. Version 2.2 44 “ N ot everything that can be counted counts, and not everything that counts can be counted” A. Einstein Like Today’s Life Cycle Context

45. Version 2.2 45 CMMI Process Areas

46. Version 2.2 46 CMMI Based Process Improvement Process Life Cycle Context Engineering Process Area (Part 1of 2)

47. Version 2.2 47 CMMI Based Process Improvement Process Life Cycle Context Engineering Process Area (Part 2of 2)

48. Version 2.2 48 CMMI Based Process Improvement Process Life Cycle Context Project Management Process Area (Part 1of 2)

49. Version 2.2 49 CMMI Based Process Improvement Process Life Cycle Context Project Management Process Area (Part 2of 2)

50. Version 2.2 50 CMMI Based Process Improvement Process Life Cycle Context Support Process Area

51. Version 2.2 51 CMMI Based Process Improvement Process Life Cycle Context Process Management Process Area

52. Version 2.2 52 Requirement Products Life Cycle Phase Expansions

53. Version 2.2 53 Concept Definition Transition Baseline Planning and Control CMMI Process Life Cycle Context An Enterprise Spiral Development Model Operational Baseline Planning and Control Operational Baseline Operations & Support Operational Shortfall Mission Integration Level Enterprise Shortfall Integrate and Field Enterprise Increment 1 Integrate and Field Enterprise Increment 2 Component System Baseline Planning and ControlEnterprise and Infrastructure Baseline Planning and Control COTS/Technology Insertion User Requirements Definition Process Reengineering CONOPS Subsequent Spiral No Integration Only ? Stop Yes Concept Definition Level Planning and Experimentation Transition to Development ? Yes No Plug & Play ? Yes No Experimentation Try Again ? Yes Development Increment 3 Transition ? No Beta Test or Defer Fielding Acquisition & Development Level Program Office Development Increment 1 Development Increment 2 All 4 Levels Exist Simultaneously

54. Version 2.2 54 CMMI Process Life Cycle Context Program Life Cycle Concept Definition Vision & Goals JV 2020 Experimentation EFX, ATD, ACTD Spiral Feedback Threat ChangeSTAR Mission ShiftEAF Existing Direction Process Modeling Capstone Architecture Shortfalls & Opportunities PPBS Budgeting & Tradeoffs Requirement Feasibility User Requirements Definition Program Direction Mission Area Planning Operational & Technical Architecture(s) Program Planning IPT

55. Version 2.2 55 CMMI Process Life Cycle Context Program Life Cycle Form Program Office SRD/TRD Development (1) Requirements Feasibility PMD APB Ops & Tech Architectures User Requirements Funding Acquisition Strategy Architecture Capstone RFP Preparation (2) Acquisition Strategy Development ASP Source Selection ContractAwardContractAward

56. Version 2.2 56 CMMI Process Life Cycle Context Program Life Cycle ContractAwardContractAward Post Award Conference System Architecture Development Define Post Award Work Packages and IPTs Form Working Level IPT Package Development Product Integration DT&E Partial Full Back to Development Test Ready? TestArticlesTestArticles Production Readiness Package Design & Development Package Design & Development Product Integration Requirements Refinement Package Consensus and Contract Action Spiral “n” Design Package Tradeoff and Decision Spiral “n” Development

57. Version 2.2 57 CMMI Process Life Cycle Context Program Life Cycle Mission Integration Form Test & Integration Working Group TestArticlesTestArticles Establish Test Environments Certification and Accreditation OT&E Production Decision Back to Development No OT&E System Fixes Yes Conduct Training, Connectivity, Installation, Deployment Infrastructure Readiness DepotStartDepotStart Finalize Production Readiness IOC

58. Version 2.2 58 CMMI Process Life Cycle Context Program Life Cycle Form User Group Phase Out & Disposal Begin Operations Begin Sustainment Operate and Maintain Operations & Support Spiral N+1 (e.g. TCTOs, Reprocurement, Modifications, SLEP Engineering, Mission Shift) O&M Planning DepotStartDepotStart

59. Version 2.2 59 Enterprise Architecture Expansions

60. Version 2.2 60 Enterprise Architecture Enterprise Architecture is an Information Technology Approach Enterprise Architecture is an Information Technology Approach - Our business is a mixture of IT and Weapons Systems Enterprise Architecture Addresses Systems of Systems Complexity Enterprise Architecture Addresses Systems of Systems Complexity - A common approach for IT and Weapons Systems Enterprise Architecture Models Describe Operational Behavior Enterprise Architecture Models Describe Operational Behavior - System of Systems “Business Models” Transition Plans from “As Is” to “To Be” for Enterprise Planning Transition Plans from “As Is” to “To Be” for Enterprise Planning - Powerful enterprise investment planning & management tool Enterprise Architecture is the Key to Enterprise Integration Enterprise Architecture Models Describe Required Interfaces Enterprise Architecture Models Describe Required Interfaces - Permits standardization required for interoperability

61. Version 2.2 61 Tech Sys Ops Transition Tech Sys Ops Target Architecture Cycle Tech Sys Ops Oversight and Control Baseline

62. Version 2.2 62 Operational Systems Technical “To Be” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “To Be” System Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “To Be” Technical State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation Transition State Transitions State Transitions System Evaluation System Evaluation System Tech Forecast System Tech Forecast System Rules System Rules System Info Exchange System Info Exchange Op Activity -to- System Func Op Activity -to- System Func System Event/ Trace Desc System Event/ Trace Desc System Functionality System Functionality System Performance System Performance Element Iface Element Iface Sys Node Connectivity Sys Node Connectivity Physical Data Model Physical Data Model Systems and interconnections providing for or supporting military operation “As Is” System Transition Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model “As Is” Operational Operational tasks, elements and information flows required to accomplish military operation Op Rules Op State Transition Op State Transition Command Relationships Command Relationships OpNode Connectivity OpNode Connectivity Op Concept Op Event/ Trace Op Event/ Trace Op Info Exchange Op Info Exchange Activity Model Activity Model Logical Data Model Logical Data Model Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements Transition Standards Technology Forecast Standards Technology Forecast Technology Architecture Profile Technology Architecture Profile Minimal set of rules governing the arrangement, interaction and interdependencies of system parts or elements “As Is” Technical Tech Sys Ops Tech Sys Ops Tech Sys Ops “As Is” Enterprise Program Office Transition “To Be” Tech Sys Ops Tech Sys Ops Tech Sys Ops “As Is” System Program Office Transition “To Be” Tech Sys Ops Tech Sys Ops Tech Sys Ops “As Is” System Program Office Transition “To Be” Tech Sys Ops Tech Sys Ops Tech Sys Ops “As Is” System Program Office Transition “To Be”

63. Version 2.2 63 Program Space POM Cycle, Budget Cuts, Management Considerations, Support Resource Inadequacy, and Political Considerations Program Constraints Requirements Architectures and Program Constraints Both Constrain and Define the Individual Program Approach Tech Sys Ops Tech Sys Ops Tech Sys Ops Baseline Oversight and Control Transition Target

64. Version 2.2 64 Tech Sys Ops Tech Sys Ops Tech Sys Ops Baseline Oversight and Control Transition Target A Notional Enterprise Architecture Process Develop / Revise Transition Plan Develop / Revise Target Enterprise Architecture Develop / Revise Baseline Enterprise Architecture Define / Revise Architecture Process & Approach Establish / Revise Management Structure & Control Obtain / Renew Executive Buy-In and Support Monitor & Use Enterprise Architecture

65. Version 2.2 65 A Notional Enterprise Architecture Process