1 / 19

Systems Engineering From a Life Cycle Perspective

Systems Engineering From a Life Cycle Perspective. John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007. Outline. The Acquisition Life Cycle – A Refresher Systems Engineering – The Function As Applied Across the Life Cycle. FRP Decision Review.

satin
Download Presentation

Systems Engineering From a Life Cycle Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Systems Engineering From a Life Cycle Perspective John GroenenboomDirector Engineering – MesaBoeing RotorcraftDec 12, 2007

  2. Outline • The Acquisition Life Cycle – A Refresher • Systems Engineering – The Function • As Applied Across the Life Cycle

  3. FRP Decision Review System Engineering Across the Life Cycle The Current 5000 Model A B C IOC Concept Exploration Component Advanced Development System Integration System Demo LRIP Full-Rate Production & Deployment Operations & Support Concept Decision Critical Design Review System Dev & Demonstration Production & Deployment Concept & Tech Development Sustainment Pre-Systems Acquisition Systems Acquisition (Engineering & manufacturing development, demonstration, LRIP & production) BLOCK II Continuous communication with users BLOCK III Early & continuous testing BLOCK IV BLOCK V ITR ASR SRR PDR CDR FRR PCR ECPR SFR TRR SVR/PRR Design Reviews

  4. Block III Block II Block I Evolutionary (Spiral) Development Adds the Forth View of Time An architecture is: “the structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time.” Source:  DoD Integrated Architecture Panel, 1995 Based on IEEE STD 610.12 Systems View Operational View What systems to bring together and how to organize them to provide capability What the warfighter wants to do and how Technical View How to put the pieces together Build-In Capability to Grow Upfront

  5. Systems Engineering Functions • System Architecture and Definition • Operations and Systems Analysis • Affordability • Measurement and Control • System Modeling and Simulation • System Integration, Verification and Validation • Reliability, Maintainability and Systems Health • Human Systems Integration • Systems Safety • Systems Security • Certification and Qualification • Communication and Networks • Customer Engineering

  6. Systems Engineering Responsibilities • Concept(s) of Operation • Customer/User Relationships • Use Case(s) • Modeling, Simulation and Analysis • Requirements • Functional Analysis • Requirements Allocations • Verification/Validation • KPPs/TPMs • Risk Management • Readiness Level; Technology, Integration and Manufacturing • Verification/Validation Progress

  7. Systems Engineering Responsibilities • Configuration (Baseline) Management • Requirements • KPP/TPM Margins (Growth) • Product Definition • Integrated Master Plan / Integrated Master Schedule • Entrance and Exit Criteria • Interface Control • Trade-Offs • Affordability • Design for Manufacturing and Maintenance • Product Effectiveness and Value • Growth Capabilities and Relevance

  8. Systems Engineering - Execution • Culture • Propensity to Understand the System Solution • Understood as a Behavior by Entire Team • Organization • Defined Responsibility/Authority/Accountability • SEP/SEMP • Defined Plan of Execution

  9. Systems Engineering: Where Industry Is Coming From: Industry: Program Management Production Engineering Product Support T&E Finance SM&P Training Bus.Dev. Quality New Bus

  10. Systems Engineering: Where Industry and Government Need to Be: Product Support Program Management Training Production Engineering Quality T&E Bus.Dev. Finance New Bus SM&P System Engineering Is…… ….Integration Equally Across The Entire Program

  11. Points to Ponder • Has System Complexity Changed the Fundamentals of Systems Engineering? • Has System Complexity Highlighted the need for Effective Application of Systems Engineering?

  12. FRP Decision Review Disciplined Systems Engineeringat Every Stage A B C IOC Concept Exploration Component Advanced Development System Integration System Demo LRIP Full-Rate Production & Deployment Operations & Support Concept Decision Critical Design Review System Dev & Demonstration Production & Deployment Concept & Tech Development Sustainment Pre-Systems Acquisition Systems Acquisition (Engineering & manufacturing development, demonstration, LRIP & production) BLOCK II Continuous communication with users BLOCK III Early & continuous testing BLOCK IV BLOCK V

  13. Concept and Technology Development What: • Starts with the Customer Requirements Group • Applying Future Technology Solutions • To Anticipated Future Scenarios • Based Upon Past and Current User Experiences How: • Participation in the JROC • Development of Concept(s) of Operation • Identification of Technologies • Determination of Risk Reduction, Technology Maturation Requirements

  14. System Development and Demonstration What: • Flows from the Concept Stage • Ranging from Risk Reduction Activities • To Detail Design • Tracing Requirements from the Concept to an Operational Demonstration How: • Defined Set of Requirements with Growth for Future Needs • A Functional Analysis to Determine Allocations • Traceability between Requirements and Ver/Val • Continual Review of Risks, Issues and Opportunities to Identify and Resolve • Full Engagement with Customer and Suppliers in Execution and Control

  15. Production and Deployment What: • Initiates with LRIP Before SDD Complete • Spans Annual Lot upgrades and Major Block Improvements • Proving the Effectiveness of SDD Relative to DFMA and Lean • Providing a Foundation for People, Technologies and Capabilities How: • Baseline Control of the Configuration, and KPP/TPM Margins • Identification and Resolutions of Risks, Issues and Opportunities • Tracking of Obsolescence, and –ilities to Ensure Quality • Engagement with User Community for Emerging Needs • Identifying Technologies to Keep the System Relevant

  16. Operations and Support What: • Begins by Influencing the Concept and Technology Stage • Lessons Learned • Spiral Development • Impacts the Design • A Partnership with the User Community; on Their Terms • Ends by in Influencing the Next Lot/Block Upgrade How: • Engagement with User Community Documenting Experiences • Identification and Resolution of Issues • Capturing Opportunities to Upgrade the Product

  17. The Customer Expects a Quality Product through Effective Execution of System Engineering and Program Management The Triple Constraint TECHNICAL PERFORMANCE Scope BUDGET SCHEDULE SE Fundamentals are the Same for Complex Systems, Just more Essential

  18. Questions?

More Related