Join us for our 9 April 2024 Chapter meeting featuring:
Main Presentation: "Risk Management and Systems Engineering: The Shaping of New and Future Activities of the INCOSE Risk Management WG", by Jack Stein and Bob Parro
Abstract:
Systems engineers as individuals, and the field of systems engineering as a whole, are faced with an enormous challenge. Increasing system complexity, and ever more rapid and unpredictable developments and changes in technology, and in the socio-technical environments in which we will engineer and use the systems of the future, are creating levels of uncertainty, risk, and opportunity never before encountered.
In response, the practice of risk (and opportunity) management, in general and specifically as related to systems engineering, are undergoing significant change.
This presentation will inform attendees of recent changes in the practice of risk (and opportunity) management, and will provide an overview of INCOSE Risk Management Working Group (RMWG) current and future planned activities. The session will include an open Q&A segment, and is intended to be engaging two-way exchange of information, thoughts and ideas, aimed at directing, prioritizing, and improving the activities and work products of the INCOSE RMWG.
Bio:
The INCOSE Risk Management Working Group (WG) was established in 1998, making it one of INCOSE’s longest running working groups. Currently, the WG has just over 120 members world-wide. The size and scope of activities of the WG are expected to increase as fundamental changes in the concepts, principals and practices of risk management defined in the 1st (2009) edition of overarching international risk standard ISO 31000, Risk Management — Principles and guidelines, are implemented in an increasing number of organizations and systems engineering projects and programs. These changes are reflected in ISO/IEC/IEEE 16085:2021, Systems and software engineering — Life cycle processes — Risk management, and in the 5th Edition of the INCOSE Systems Engineering Handbook.
Bob Parro and Jack Stein share in the chair-person duties of the Risk Management WG, making sure the WG is represented at monthly TechOps meetings and Annual International Workshops (IWs). As WG co-chairs, Jack and Bob have co-authored the Risk Management sections of both the 4th and 5th editions of the INCOSE SE Handbook. Together with WG member and standards specialist Paul Heininger, they represented INCOSE and the WG in the ISO/IEC/IEEE 16085:2021 work.
Jack Stein resides in Michigan and is a Past President of the INCOSE Michigan Chapter. Bob Parro resides in the Chicago area and is a Past President of the Chicagoland Chapter. They are both strong advocates of WG-Chapter interaction.
Systems Thinking in a Digital World: The Models are NOT the Engineering
Presenter: Christopher Stokes
Biography
Chris is a Principal Systems Engineer at Raytheon Technologies. He has worked for the Raytheon Missiles and Defense division of Raytheon Technologies in Tucson, AZ for 22 years. He studied Aerospace Engineering at Georgia Tech and obtained a Bachelor of Science in Aerospace Engineering. In addition, he Studied Systems Engineering from the University of Alabama in Huntsville where he obtained a Master of Science in Systems Engineering with a Statistical Analysis focus.
Chris has worked on many different Defense programs including the Standard Missile-3 (SM-3) Aegis LEAP Interceptor (ALI), SM-3 Block 0, SM-3 Block I, SM-3 Block Ia, SM-3 Block Ib, Terminal High Altitude Area Defense (THAAD), Kinetic Energy Interceptor (KEI), Exoatmospheric Kill Vehicle (EKV), Redesigned Kill Vehicle (RKV), Tactical Advanced Laser-guided OrdNance (TALON), and StormBreaker. Chris is currently the Lead Systems Engineer for the StormBreaker Information Security Engineer Change Program (iECP) at Raytheon Missile and Defense. He is a member of several professional organizations including INCOSE and AIAA. He enjoys cycling, Star Wars, and Dungeons and Dragons.
Abstract
The future of the Systems Engineering Discipline lies in Model Based Systems Engineering. As the complexities of the Subassembly, Assembly, Unit, Module, System, and Systems of Systems grows ever more complicated, the ability of the modern systems engineer to keep up grows more dependent on models and algorithms to ensure that the system in question meets the requirements and (more importantly) the needs of the customer. However, while the techniques of Model-Based Systems engineering can aid the systems engineer and all other disciplines, there is a caution.
The MBSE model should never be a substitute for the engineer’s thought process and decision making. This paper will discuss three such case studies where the model substituted for the knowledge and experience of the engineer. Specifically, the Kansas City Hyatt Regency walkway collapse, the Atlanta Centennial Olympic Stadium collapse, and a modern Defense System requirements model errors that lead to increased cost and schedule delays. In addition to going through each of these failures in detail, the paper will provide lessons learned applicable to future endeavors.