Systems Engineering and Acquisition Logistics Brief to the ACQ LOG FIPT Jan, 28 2005

1. Systems Engineering andAcquisition LogisticsBrief to the ACQ LOG FIPTJan, 28 2005

2. USD(AT&L) Imperatives • “Provide a context within which I can make decisions about individual programs.” • “Achieve credibility and effectiveness in the acquisition and logistics support processes.” • “Help drive good systems engineering practice back into the way we do business.”

3. Underway Completed SE Revitalization Elements of SE Revitalization Policy / Guidance Training / Education Assessment & Support SE Framework & SEP Policy (memos) SE Specific Courses Assessment Methodology DoDI 5000.2 Enabling Courses (PM, ACQ, LOG…) Program Support & Outreach Acquisition Guidebook Systemic Analysis SEP Prep Guide Continuous Learning Courses

4. SE in the System Life Cycle“The Wall Chart”

5. Important Design Considerations“The Fishbone”

6. SE Education & Training • DAU (DAWIA) courses under review, with plan to address broader E&T community (e.g., undergraduate and graduate courses) • Courses for decision makers (i.e., PMs, PEOs) • Core, certification courses before assignment specific • Career fields with large populations (viz., SPRDE) • Courses mandated for all Corps members (e.g., ACQ) • Prioritized, focused continuous learning courses (e.g., R&M, Technical Reviews, System Safety, SEP Preparation) • Courseware review • First tier: ACQ, PMT 2XX/4XX, SAM 301, SYS, TST 301 • Second tier: LOG, other PMT, other SAM, other TST, and selected BCF, CON, PQM

7. LOG Career Field Linkages • LOG career field is intimately linked to SPRDE and overall systems engineering revitalization efforts. • SEP impacts technical management, technical planning, risk • Policy addendum (22 Oct) impacts technical reviews logistician participation in same • Implementation of sound SE depends on “upfront and early”, TLCSM • Defense Acquisition Guide, Chapter 4 (SE) emphasizes supportability as an integrated design consideration, and has extensive discussion of SE in sustainment • Lead Logistician and Lead Systems Engineer need to team early in process and throughout the life cycle

8. Key Linkage Points • Planning • Systems engineering as basis for program plan and acquisition strategy • Risk Management • Systems engineering as underlying process for technical risk assessment, including design for supportability • Technical Management • Systems engineering as basis for IPT staffing, technical baseline management, technical reviews as basis for management of end item and support system designs • Systems engineering as basis for technical trades • SE with T&E with Supportability • Systems engineering as the integrating mechanism for requirements definition, design realization, V&V planning/execution, and multitude of design considerations

9. Approach • 1 – Obtain and review overarching LOG Course Student Assessment Plans (CSAP) or other available course guidance material • 2 – Assess versus SE revitalization policy, guidance, education and training; develop suggested edits • 3 – Coordinate with the LOG FIPT to implement “SE revitalization mods” into LOG career field training • Flow down to training modules, “PDR/CDR” on course revisions.

10. LOG Course Documents Reviewed • Course Student Assessment Plan (CSAP) for • LOG 101, Acquisition Logistics Fundamentals • LOG 201A, Intermediate Acquisition Logistics • LOG 201B, Intermediate Acquisition Logistics • LOG 203, Reliability and Maintainability • LOG 235, Performance Based Logistics • LOG 304, Executive Life-Cycle Logistics Management • Course Outline for LOG 304, Executive Life-Cycle Logistics Management Course

11. Essence of Recommended Course Changes • Updated Systems Engineering Lesson/Module to address 8 technical and 8 technical management (SE) system engineering processes, systems engineering “V” model as applied across the total life cycle, and SEP • Updated selected lessons/modules to identify SE technical or technical management processes used by acquisition logisticians for: • Decision making • Design for supportability • Risk management • Sustainment engineering • Etc.

12. LOG-101 Lessons Updates • General: Change to SE processes vice process • Lesson 2, Systems Engineering: Student to identify 8 technical and 8 technical management processes of SE, SE “V” model and SEP • Lesson 3, Supportability Analyses: Connect supportability analyses to SE • Lesson 4, Life Cycle Cost Management: Connect to SE role in program cost estimate development • Lesson 5 Sustainment Practices: Identify role of SE processes and SE “V” model in selecting sustainment practices • Lesson 8, Computer Resources Support: Software development is part of SE processes • Lesson 10, Support Equipment Acquisition: SE applied to support equipment acquisition • Lesson 12,Technical Data: Recognize that Data management is SE technical management process

13. LOG-201A Updates • General: Changed SE process to 8 technical and 8 technical management processes and added SE “V” model • Systems Engineering Lesson: Added systems engineering technical reviews, SE “V” model, and SEP (Systems Engineering Plan) • Modeling and Simulation Lesson: M&S input to SE process, Decision Analysis • Open Systems and Interoperability: Interface Management, an SE process, important to achieving • Test and Evaluation: Recognize relation to Risk Management, Verification, and Validation processes of SE • Life Cycle Costing: Connect to SE role in program cost estimate development

14. LOG-201B Updates • General: Changed SE process to 8 technical and 8 technical management processes and added SE “V” model and SEP • Systems Engineering Lesson: Identified specific SE processes to be applied during class and selection of appropriate SE technical reviews • Modeling and Simulation Lesson: M&S input to SE process, Decision Analysis and is included in SEP • Test and Evaluation: Recognize relation to Risk Management, Verification, and Validation processes of SE • Life Cycle Costing: connect to SE role in program cost estimate development by applying SE processes, Design Analysis and Design Solution • Support Strategy Planning: Use Technical Management and Risk Management SE processes

15. LOG 203, Reliability and Maintainability • Impacts of R&M on Missions: Identify which SE processes use R&M as inputs • Operational and Contractual R&M Requirements: Identify which SE processes translate R&M requirements into contracts • R&M and Risk Reduction: SE process, Risk Management, used

16. LOG 235, Performance Based Logistics • Student to recognize 8 technical and 8 technical management processes of SE, SE “V” model and SEP and how they contribute to logistics and sustainment planning • Recognize that Configuration Management is one of 8 SE technical management processes

17. LOG 304, Executive Life-Cycle Logistics Management • System Engineering: Change SE process to 8 SE technical management and 8 management processes and added SE “V” model and SEP

18. BACKUP

19. SE Education and Training Summit (October 2003) • Brainstorming session • What’s working • What needs to be fixed • Significant barriers • Required actions • Participants • Services • Academia • Industry • Associations (NDIA, AIA, EIA, GEIA, INCOSE) • Formed five working groups, assigned leads • Policy • Processes • Tools and guides • Resources • Education and training

20. What We Found: Lack of Uniform Understanding of SE at Department Level • Lack of coherent SE policy • Lack of effective SE implementation - no “forcing function” for PM or contractor SE activities • Program teams incentivized by cost and schedule, not execution of disciplined SE • Products and processes not in balance (emphasis on speed; fix it in the next spiral) • Inconsistent focus across life cycle, particularly prior to Milestone B • SE inadequately considered in program life cycle decisions

21. What We Found: Lack of Uniform Understanding of SE in Community-at-Large • No single definition or agreement on the scope of SE • Lack of common understanding of how SE is implemented on programs • Is SE done by the systems engineer? • Does the systems engineer lead the SE effort? • No uniform understanding of what makes a good systems engineer • No consistent set of metrics/measures to quantify the value of SE • Cost and schedule estimation and risk management processes inconsistently aligned with SE processes • Resistance to harmonization of multiple standards and models • Multiple practitioner communities not aligned: • Hardware - Aircraft vs. Rocket Developers • Software - Telecommunications • Information Technology - Program Management

22. What We Found: System Complexity • System complexity is ever increasing – Moore’s Law at the system scale – Family of Systems/System of Systems interdependencies • Integrated systems (software with embedded hardware) versus platforms (hardware with embedded software) • Network centric, spiral development, and extension of system applications are driving higher levels of integration

23. What We Found: The Resource Picture • Degreed workforce is a shrinking pool • Many graduates are not US citizens • Total engineering enrollments continue to decrease • Ability to attract and retain young engineers in the aerospace industry is directly associated with the commercial marketplace • The aerospace and defense industry is seen as being overly bureaucratic and lacking in exciting technical challenges by engineering students • 5 year itch • Existing university/industry partnerships are not having enough impact. • SE is not a standard discipline (EE, ChemE, ME, etc.) • More focus at undergraduate level • Do we have critical mass in terms of SE graduate level training in the U.S.? • Need new ways to attract and develop system engineers • Additional learning • On-the-job experience We need a better approach Adapted from G. Shelton (Raytheon)

24. Policy and Guidance • DUSD(AT&L) SE Policy Memo • Director, DS, SEP Interim Guidance Memo • DUSD(AT&L) SE Policy Addendum • Defense Acquisition Guidebook, Chapter 4 • SEP Preparation Guide

25. Systems Engineering Policy in DoDSigned by the Honorable Mike Wynne, USD(AT&L) (Acting) Feb 20, 2004 • All programs, regardless of ACAT shall: • Apply an SE approach • Develop a Systems Engineering Plan (SEP) • Describe technical approach, including processes, resources, and metrics • Detail timing and conduct of SE technical reviews • Director, DS tasked to provide SEP guidance for DoDI 5000.2 • Recommend changes in Defense SE • Establish a senior-level SE forum • Assess SEP and program readiness to proceed before each DAB and other USD(AT&L)-led acquisition reviews

26. SEP Implementation GuidancePer OUSD(AT&L) Defense Systems Memo signed Mar 30, 2004 • Submitted to MDA at each Milestone, SEP describes: • Systems engineering approach • Specific processes and their tailoring by phase • Both PMO and Contractor processes • Systems technical baseline approach • Use as control mechanism, including TPMs and metrics • Technical review criteria and outcomes • Event driven • Mechanism for assessing technical maturity and risk • Integration of SE with IPTs and schedules • Organization, tools, resources, staffing, metrics, mechanisms • Integrated schedules (e.g., IMP and IMS)

27. SE Policy AddendumSigned by the Honorable Mike Wynne, USD(AT&L) (Acting) Oct 22, 2004 • Each Program Executive Officer (PEO) shall have a lead or chief systems engineer • The PEO lead or chief systems engineer shall: • Review assigned programs’ SEPs and oversee their implementation • Assess the performance of subordinate lead or chief systems engineers • Technical reviews shall: • Be event driven (vice schedule driven) • Conducted when the system under review meets review entrance criteria as documented in the SEP • Include participation by subject matter experts independent of the program, unless waived by SEP approval authority in the SEP

28. SE in Defense Acquisition Guidebook • New SE guidance to acquisition community—Chapter 4 • Best practices for “applied” SE • SE process • Guide for each acquisition phase, concept refinement through disposal • Linkage of SE products and processes to acquisition objectives and decision points