Difference between revisions of "Editor's Corner"

From SEBoK
Jump to navigation Jump to search
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:Rob_cloutier_bio_photo.jpg|right|200px]]
+
[[File:Hutchison,Nicole Profile.jpeg|right|200px]]
  
 
{|
 
{|
 
|-
 
|-
−
|<center>''The “Editor’s Corner” provides perspective from the Editor in Chief on critical topics for systems engineering, either through their own words or by inviting a guest writer.''</center>
+
|<center>''The ''Editor’s Corner'' provides perspective from the Editor in Chief on critical topics for systems engineering, either through their own words or by inviting a guest writer.''</center>
 
|}
 
|}
  
 +
<div style="text-align:right">'''20 November 2023'''</div>
  
−
<div style="text-align:right">'''30 October 2022'''</div>
+
The formal discipline of systems engineering emerged in the first half of the 20th century. Over the last 80+ years, it has evolved from first principles to a process-focused field that generally operates in the defense and aerospace domains to a transdisciplinary one focusing on the integration and interaction between technology and people across a variety of domains. In its ''Vision 2035'', the International Council on Systems Engineering (INCOSE), states that “the practice of systems engineering will further evolve to support the demands of ever-increasing system complexity and enterprise competitiveness. By 2035, systems engineering will leverage the digital transformation in its tools and methods and will be largely model-based using integrated descriptive and analytical digital representations of the systems. Systems design, analysis, and simulation models, immersive technologies, and an analytic framework will enable broad trade-space exploration, rapid design evolution, and provide a shared understanding of the system throughout its life cycle.”
  
 +
The Systems Engineering Research Center [http://www.sercuarc.org (SERC)] led the initial creation of the ''Guide to the Systems Engineering Body of Knowledge'' (SEBoK, pronounced “see-bach”). In 2009, the SERC began the three-year process of developing the SEBoK with a team of over 70 authors from around the world. Version 1.0 was published in 2012 and inpast 11 years the SEBoK has evolved in many ways: new topics, the inclusion of videos, a major rearrangement of the discussion, and perhaps most importantly, the addition of an area dedicated to the emerging topics of systems engineering.
  
−
<div style="text-align:justify">Let me point out before you begin reading, this is not an inditement of any organization or organizations – I am simply making an observation of the systems engineering community. I feel it is important for individuals and organizations to reflect on the past, and see if we can learn anything to help us move forward as professionals. So, here goes …
+
Over the years, the SEBoK has been led by several Editors in Chief:
 +
*Art Pyster and Dave Olwell led the development of SEBoK through version 1.0, including the decision to implement the SEBoK as a wiki.
 +
*Rick Adcock, appointed the first Editor in Chief after the transition of SEBoK from a research task to a community-led effort, helped identify new members of the editorial board and oversaw the addition of the first domain-focused knowledge area, [[Healthcare Systems Engineering]].
 +
*Rob Cloutier added the first new part to the SEBoK since its initial release: [[Emerging Knowledge]], which captures topics that are critical for systems engineers but for which the knowledge is not yet settled (e.g. artificial intelligence applications to systems engineering). Rob also fostered the addition of multi-media to the SEBoK and created and built upon articles about the discipline, including [[A Brief History of Systems Engineering]].
  
−
Resistance to change – have we as a systems engineering community become slow and lethargic in responding to change. A quick scan of the Internet shows that INCOSE has produced three vision documents since 2007. These vision documents represented the systems engineering vision for the years 2020, 2025, and the latest, for 2035. So let me ask – as a community, do we go back and look at those projections, determine what was correct, and what missed the mark? Do companies that support professional societies, or government agencies, go back and review these?
+
I am honored to have been asked to be the newest Editor in Chief of the SEBoK. And like every Editor in Chief before me, I am extremely lucky to work with a group of editors and authors from around the world that have consistently supported the SEBoK. These people are critical representatives of the global systems engineering community, and the SEBoK would not be possible without their tireless efforts.
  
−
It is interesting that in 2007, INCOSE published a document titled Systems Engineering Vision 2020 (INCOSE-TP-2004-004-02). In the Executive Summary, it was stated that “In many respects, the future of systems engineering can be said to be model-based.”
+
Looking forward as the discipline of systems engineering evolves, the SEBoK will need to evolve with it. At my first INCOSE International Symposium in 2008, I heard about something called "model-based systems engineering". The last 5 years have seen a tremendous push toward "digital engineering". Both of these are currently reflected in the SEBoK, but we need to do more. Digital transformation is a critical topic for systems engineers and will continue to be for at least the next decade. But the true end state is not that we as a discipline create new pockets of practice but that instead we move as a community toward a data- and model-enabled way of working. My sincere hope is that in 2033, we will talk not about MBSE or DE but about systems engineering with models and data a standard part of practice. To that end, I'm pleased to share that we have assembled a team whose mission is to integrate the discussion of using models and data throughout the SEBoK and that Rob Cloutier has agreed to spearhead this effort.
  
−
As I write this missive in September 2022, that original vision document was published 15 years ago. Yet, as the program director of a medium-sized systems engineering program, I am approached regularly by companies, government agencies, and others looking for systems engineering talent. The number one skill these representatives are seeking is experience with model-based systems engineering (MBSE). The second is some exposure to modeling and simulation at the systems level.
+
Finally, I encourage anyone with an interest to reach out to the SEBoK team [mailto:sebok@incose.net sebok@incose.net]. We welcome your feedback and insights and look forward to partnering with you as we move toward the SEBoK of the future.  
  
−
<blockquote>In the INCOSE ''Vision 2025'', released in 2014, one of the imperatives was cited as “Advancing the '''tools''' and '''methods''' to address complexity.” (Emphasis added.) Today we are only 2+ years away from 2025. If I look at that vision document, and cherry-pick some of the statements from the 2025 vision around modeling, the authors of that document believed that by 2025 …
+
Sincerely,
−
 
+
[[File:Hutchison_Signature.png|200px|left]]
−
*Modeling and simulation is widely used to support integrated planning for a better representation of real-world constraints and solutions
 
−
*Systems engineering tools will facilitate systems engineering practices as part of a fully integrated engineering environment. Systems engineering tools will support high fidelity simulation, immersive technologies to support data visualization, semantic web technologies to support data integration, search, and reasoning, and communication technologies to support collaboration.
 
−
*Model-based approaches will move engineering and management from paper documentation as a communications medium to a paperless environment, by permitting the capture and review of systems design and performance in digital form.</blockquote>
 
−
 
 
−
As I walked around talking to DoD and industry folks at a University hosted job fair this September, every company hiring systems engineers was begging for graduates that are familiar with MBSE, SysML, modeling, and simulation. It is obvious there is an overwhelming need. One student, a mechanical engineer, that took my Fundamentals of SE course, and then applied SysML in his thesis, was hired within 20 minutes of talking to a DoD agency. So, the prognostication was correct, but it seems there are still not enough individuals with the necessary skills. Did the universities fall short of preparing our students? Did the companies and agencies fall short of providing the requisite training?
 
−
 
 
−
Another interesting projection in that vision document stated that, “Use of technologies such as simulation, visualization, and gaming will lead to innovations in systems engineering education.” This is consistent with the [[Acknowledgements and Release History|Editor’s Corner musing from the last two releases]] of the SEBoK that addressed a/the metaverse.
 
−
 
 
−
As I look forward to retirement, allow me to reflect on my time as a young engineer working on the V-22 Osprey in the mid 80’s. The Boeing Corporation had decided to move from paper drawings to CADCAM. They tried to convince the aerospace engineers to give up their drafting board and tools and move to CATIA. The response was “you can have my drafting tools when you pull them from my cold, dead fingers”. So, Boeing hired a large number of college graduate engineers and trained them in CATIA. Drawings would come off the senior design engineers drafting boards, and these new CADCAM engineers would recreate the drawings in CATIA to go down to the factory to produce the parts using numerical control machines. Resistance to change. Fast forward to today – the only place you will find a drafting board in Boeing is in the Boeing Museum in Seattle. All of the senior engineers use CATIA (because they were the junior engineers in the 1980’s. It took a generation or two to transition from paper-based to computer driven modeling.
 
−
 
 
−
I can tell a similar story for the software engineering community of which I was also a part of… Even into the 90’s, mainframe and Unix programming was performed using Vi and EMACS, or even using command line. Then, Borland introduced Turbo Pascal and their IDE (Integrated Development Environment) in 1983 where one could program, compile, link, and execute a program all in one environment. For a decade or more, these IDE’s were considered toys or crutches, and “real programmers” used Vi (or EMACS or command line, you get the idea). Resistance to change. Today, most software is written using IDE’s… again, it took a generation or two.
 
−
I began this article stating that maybe the systems engineering community has become too lethargic and resistant to change – much like the aero engineers and software engineer were in the 80’s/90’s.
 
−
 
 
−
Let’s reflect on that claim - In 2007 it was identified by the INCOSE TechOps community that by 2020 our discipline would be “model-based”. Yet, today, industry cannot find enough systems engineers with experience in model-based systems engineering. We had 15 years to prepare. Let’s reflect on the other projection from that 2007 vision document that was identified earlier- “Use of technologies such as simulation, visualization, and gaming will lead to innovations in systems engineering education.” This brings me back to the previous two Editor Corners – the metaverse. Has anyone in systems engineering taken this seriously and identified the requirements for such a system?
 
−
 
 
−
I feel like this has been a random walk. So, what is really at my destination? How do I wrap this up? Let me look at my industry – graduate level education. I have been told that there are very few graduate SE programs right now that have integrated MBSE, digital engineering, and/or digital twin concepts woven into their curriculum. I am not talking about courses dedicated to these topics, but these topics simply integrated into the curriculum. In those programs that have done this, their students are being swept up months before they graduate with near six figure offers because they have used MBSE in several classes and maybe on a research project, not to mention their thesis or dissertation.
 
−
 
 
−
Many hundreds of hours went into the creation of these Vision documents by leaders in our field from all over the world. It is my opinion that we should take more time to consider, reflect, and act on those vision documents. We should also take a look at them retrospectively and determine where they were right, and where they missed the mark. Then, we need to ask ourselves as a community, what do we need to do moving forward.</div>
 
−
 
 
−
[[File:RobSignature2.jpeg|200px|left]]
 

Latest revision as of 20:12, 19 November 2023

Error creating thumbnail: File missing
The Editor’s Corner provides perspective from the Editor in Chief on critical topics for systems engineering, either through their own words or by inviting a guest writer.
20 November 2023

The formal discipline of systems engineering emerged in the first half of the 20th century. Over the last 80+ years, it has evolved from first principles to a process-focused field that generally operates in the defense and aerospace domains to a transdisciplinary one focusing on the integration and interaction between technology and people across a variety of domains. In its Vision 2035, the International Council on Systems Engineering (INCOSE), states that “the practice of systems engineering will further evolve to support the demands of ever-increasing system complexity and enterprise competitiveness. By 2035, systems engineering will leverage the digital transformation in its tools and methods and will be largely model-based using integrated descriptive and analytical digital representations of the systems. Systems design, analysis, and simulation models, immersive technologies, and an analytic framework will enable broad trade-space exploration, rapid design evolution, and provide a shared understanding of the system throughout its life cycle.”

The Systems Engineering Research Center (SERC) led the initial creation of the Guide to the Systems Engineering Body of Knowledge (SEBoK, pronounced “see-bach”). In 2009, the SERC began the three-year process of developing the SEBoK with a team of over 70 authors from around the world. Version 1.0 was published in 2012 and inpast 11 years the SEBoK has evolved in many ways: new topics, the inclusion of videos, a major rearrangement of the discussion, and perhaps most importantly, the addition of an area dedicated to the emerging topics of systems engineering.

Over the years, the SEBoK has been led by several Editors in Chief:

  • Art Pyster and Dave Olwell led the development of SEBoK through version 1.0, including the decision to implement the SEBoK as a wiki.
  • Rick Adcock, appointed the first Editor in Chief after the transition of SEBoK from a research task to a community-led effort, helped identify new members of the editorial board and oversaw the addition of the first domain-focused knowledge area, Healthcare Systems Engineering.
  • Rob Cloutier added the first new part to the SEBoK since its initial release: Emerging Knowledge, which captures topics that are critical for systems engineers but for which the knowledge is not yet settled (e.g. artificial intelligence applications to systems engineering). Rob also fostered the addition of multi-media to the SEBoK and created and built upon articles about the discipline, including A Brief History of Systems Engineering.

I am honored to have been asked to be the newest Editor in Chief of the SEBoK. And like every Editor in Chief before me, I am extremely lucky to work with a group of editors and authors from around the world that have consistently supported the SEBoK. These people are critical representatives of the global systems engineering community, and the SEBoK would not be possible without their tireless efforts.

Looking forward as the discipline of systems engineering evolves, the SEBoK will need to evolve with it. At my first INCOSE International Symposium in 2008, I heard about something called "model-based systems engineering". The last 5 years have seen a tremendous push toward "digital engineering". Both of these are currently reflected in the SEBoK, but we need to do more. Digital transformation is a critical topic for systems engineers and will continue to be for at least the next decade. But the true end state is not that we as a discipline create new pockets of practice but that instead we move as a community toward a data- and model-enabled way of working. My sincere hope is that in 2033, we will talk not about MBSE or DE but about systems engineering with models and data a standard part of practice. To that end, I'm pleased to share that we have assembled a team whose mission is to integrate the discussion of using models and data throughout the SEBoK and that Rob Cloutier has agreed to spearhead this effort.

Finally, I encourage anyone with an interest to reach out to the SEBoK team sebok@incose.net. We welcome your feedback and insights and look forward to partnering with you as we move toward the SEBoK of the future.

Sincerely,

Error creating thumbnail: File missing
Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Editor%27s_Corner&oldid=70348"