No abstract

No abstract

Abstract. Systems thinking is commonly accepted as the backbone of a successful systems engineering approach. As such, the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) team chose to leverage a systems thinking based tool, called Systemitool, to describe our project to the vast audience that would potentially become involved directly or indirectly in the success of the project. This paper describes the process and steps used by the authors and the BKCASE team to develop the project's systemic diagram, or Systemigram TM , and the story behind the project, the products, and the vision of the BKCASE project. The goal of the paper is to provide guidance so that readers can leverage the lessons learned from this effort to successfully develop their own project definitions and stories.

No abstract

Cumulative sum (CUSUM) control charts are very effective at detecting persisting special causes. The most common CUSUM chart assumes that the process measurement being monitored follows the normal distribution. Many industrial problems yield measures with skewed, positive distributionsÐexamples are component reliabilities, times to completion of tasks and insurance claims. Non-normal measures such as these should not be monitored using procedures based on the normal distribution. The inverse Gaussian distribution provides a¯exible distribution that can be used to model positive skew quantities, and therefore provides an effective framework for statistical process control on processes producing such measures. This paper de®nes the optimal CUSUM control chart schemes for location and shape of the inverse Gaussian distribution and evaluates its performance in detecting step changes in each of these parameters. The inverse Gaussian distribution has been shown to be a good ®t to a long record of task completion times on a General Motors assembly line. We extend this application, showing how our CUSUMS may be used to detect changes in the distribution of these task completion times.

Abstract. Systems thinking is commonly accepted as the backbone of a successful systems engineering approach. As such, the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) team chose to leverage a systems thinking based tool, called Systemitool, to describe our project to the vast audience that would potentially become involved directly or indirectly in the success of the project. This paper describes the process and steps used by the authors and the BKCASE team to develop the project's systemic diagram, or Systemigram TM , and the story behind the project, the products, and the vision of the BKCASE project. The goal of the paper is to provide guidance so that readers can leverage the lessons learned from this effort to successfully develop their own project definitions and stories.

Abstract. The boundaries of systems engineering are evolving as system related needs evolve. These 'fuzzy' boundaries result in gaps between what users in the systems engineering community need and what the body of knowledge of systems engineering provides. This paper covers various use cases of the body of knowledge of systems engineering and explores gaps in the existing knowledge base in two areas: 1) related disciplines, and 2) emerging systems engineering topics.

Version 1.0 of the Guide to the Systems Engineering Body of Knowledge (SEBoK) was released in September 2012. Seventy authors from around the world working for three years created the SEBoK. This paper discusses twelve factors that were critical to the successful development and on-time release of the SEBoK. The approach taken is elaborated, and lessons learned along the way are highlighted. These experiences and recommendations based on them would be useful to any collaborative research effort that shares one or more of the characteristics of SEBoK development.