bluuebunny/crossref_metadata_2025_split huggingface dataset:
4.1.1 Diogenes, a Process for Finding Unintended Consequences
Authors: Bahill A. Terry 
Published: November 2014

AbstractCompanies, governments and individuals often create products, processes and procedures that solve a particular problem, only to discover that their solution has created a second problem, worse than the first. These secondary problems are often unintended consequences. Finding unintended consequences, as a part of the development process, will likely increase safety, reduce financial risk and improve customer satisfaction. This paper contains the design for a new process, named Diogenes, that will help systems engineers predict unintended, but foreseeable, consequences of a new system that is being designed. This paper contains the use cases, design diagrams, test procedure, validation and verification for Diogenes.
4.3.1 Satellites to Supply Chains, Energy to Finance —SLIM for Model‐Based Systems Engineering
Authors: Bajaj Manas , Zwemer Dirk , Peak Russell , Phung Alex , Scott Andrew , Wilson Miyako 
Published: November 2014

AbstractDevelopment of complex systems is a collaborative effort spanning disciplines, teams, processes, software tools, and modeling formalisms. Increasing system complexity, reduction in available resources, globalized and competitive supply chains, and volatile market forces necessitate that a unified model‐based systems engineering environment replace ad‐hoc, document‐centric and point‐to‐point environments in organizations developing complex systems.To address this challenge, we envision SLIM—a collaborative, model‐based systems engineering workspace for realizing next‐generation complex systems. SLIM uses SysML to represent the front‐end conceptual abstraction of a system that can “co‐evolve” with the underlying fine‐grained connections to models in discipline‐specific tools and standards. With SLIM, system engineers can drive automated requirements verification, system simulations, trade studies and optimization, risk analyses, design reviews, system verification and validation, and other key systems engineering tasks from the earliest stages of development directly from the SysML‐based system model. SLIM provides analysis tools that are independent of any systems engineering methodology, and integration tools that connect SysML with a wide variety of COTS and in‐house design and simulation tools.We are presenting SLIM and its applications in two papers. In Part 1 (this paper), we present the motivation and challenges that led to SLIM. We describe the conceptual architecture (section 1) and use cases (section 2) of SLIM followed by tools available for production and evaluation usage (section 3). In Part 2 paper—SLIM Applications—we present the applications of SLIM tools to a variety of domains, both in traditional as well as non‐traditional domains of systems engineering. Representative examples from space, energy, infrastructure, manufacturing and supply chain, military operations, and bank systems are presented.
4.3.2 Systematic Approach to the Development, Evolution, and Effectiveness of Integrated Product Development Teams (IPDTs)
Authors: Jeffs Margie , Hamelin R. Douglas 
Published: November 2014

AbstractIntegrated Product Development Teams (IPDT) are a key component of any systems engineering (SE) application, but since they are formed primarily from technical considerations, many IPDTs are far less productive than they otherwise could be. By recognizing specific personality types and skill sets, a random group of “technical” individuals can be structured to become a highly effective team capable of delivering much more than the sum of its members.
5.2.1 Understanding “System‐of‐Systems” in the Defense Context
Authors: Hiang TEO Siow , Ngah NG Chu 
Published: November 2014

AbstractThe concept and scope of Systems Engineeing (SE), System‐of‐Systems Engineering (SoSE) and Systems Architecting (SA) are subject to various interpretations from subject matter experts across different subject domains. Alongside, there appear to be a wide array of terms describing systems, including, but not limited to, System‐of‐Systems (SoS), complex systems, engineering systems, and large‐scale systems. Reconciliation of the terminologies would facilitate discussions among practitioners and engineers new to the field.The first section of this literature review is therefore an attempt to examine relevant papers and effort in the field of SoS to distil the key concerns and motivations stakeholders have when they refer to the term “SoS”, particularly in the context of defense where its application is in Network‐Centric Warfare. Characteristics that connect the seemingly different terminologies for systems will also be highlighted. The second section reviews the practice of SE/SoSE/SA on defense SoS, and highlights particular challenges that SoSE/SA communities seek to address for this renewed sense of complexity and abstraction.
5.4.2 Competencies Required for Successful Acquisition of Large, Highly Complex Systems of Systems
Authors: Armstrong James R , Kepchar Kenneth , Henry Devanandham , Pyster Arthur 
Published: November 2014

AbstractA generic competency model for acquiring large, highly complex Systems of Systems is presented. The model combines competencies of systems engineering, systems integration, and software engineering. The model is applied to the U.S. Federal Aviation Administration's (FAA) Next Generation Air Transportation System (NextGen). The FAA is facing the challenge of significant increases in workload for the air traffic control system. NextGen efforts are aimed at providing the changes to the system needed to meet that challenge. In order to be prepared, the FAA is looking at the competencies needed to develop and deploy those improvements.
5.6.1 Model‐Based Standards Authoring: This research is supported by EU FP7 VISIONAIR ‐ A World‐class infrastructure for Advanced 3D visualization‐based research
Authors: Blekhman Alex , Dori Dov , Martin Richard 
Published: November 2014

AbstractWe present a methodology for model‐based authoring of standards based on Object‐Process Methodology (OPM). This general systems‐engineering approach to authoring of specifications is supported by an OPM framework and a procedure for model‐to‐text translation. This methodology, developed as part of the ISO TC 184/SC 5 OPM Study Group activities, is expected to become the basis of an emerging ISO Standard for Model‐Based Standards Authoring.
6.3.1 Process Patterns for Agile Capability Engineering Methodology: The PACEM Project
Authors: Nécaille Christophe 
Published: November 2014

AbstractThis paper presents the approach used to investigate the potential of process patterns to increase the level of agility of engineering processes applied to military capabilities or system of systems. This effort is a follow‐up of the Canadian Capability Engineering Process (CEP) defined during the Collaborative, Capability, Definition, Engineering and Management (CapDEM) technology demonstration project. The challenges surrounding process assessment are investigated.
6.4.2 A Systems Assurance Perspective Towards Generic Systems Engineering
Authors: Joyce g Pek Foong , Hin Oh Sin , Seng Yap Kwee , Chan Samuel 
Published: November 2014

AbstractA previous paper (ref.1) was published to describe a generic system‐of‐systems (SoS) requirements model, which was constructed to guide systems engineering process for future Rail Transit Systems (RTS) in Singapore. In that publication, guidelines for detailed analysis of each requirements breakdown in the areas of operational, functional and physical requirements were explained.This paper elaborates on the systems assurance aspect, as part of the generic systems engineering and generic requirements model to guide development of non‐functional requirements. In particular, management of safety and reliability is explained. The systems assurance process described in this paper is derived from valuable experience gained through management of several highly integrated driverless RTS with different procurement strategies. The new systems engineering process will be cascaded to future transit projects for improvements of requirements management, verification and validation, and optimization of available resources.
6.5.0 Integrating Systems Engineering into Engineering Curricula Through Capstone Projects
Authors: McGrath Beth , Nemes James , Umphress David , Whitcomb Cliff 
Published: November 2014

AbstractWith funding from the Department of Defense, a research effort is underway to understand the methods through which systems engineering learning and career interest may be increased among undergraduate and graduate engineering students. This research is being conducted in the context of 14 “capstone” projects, in most cases as an integrative culminating, project‐based course, and in one case involving an entire SE graduate curriculum, involving teams of students working together on the development of a product or prototype that addresses a real Department of Defense need. Implemented as pilot projects in eight civilian and six military universities, these 14 institutions are piloting methods, materials, and approaches to create new courses, enhance existing courses, and adapt curricula, to embed, infuse, and augment systems engineering knowledge, skills, abilities, and behaviors, as defined by the SPRDE‐SE/PSE Competency Model. This session will present an overview of the overall Systems Engineering Capstone research and findings to date, along with an overview and discussion of three different approaches to course design and preliminary student impacts.
7.1.1 Modeling Pilot Workload for Multi‐Aircraft Control of an Unmanned Aircraft System
Authors: Schneider Michael , McGrogan Jason , Colombi John M. , Miller Michael E. , Long David S. 
Published: November 2014

AbstractA demand for increased use of Unmanned Aircraft Systems (UASs) without commensurate increases in pilot manpower has created proposals for the concept of Multiple Aircraft Control (MAC). To understand the potential effect of such proposals, a workload model was developed from pedigreed system architecture which permits the prediction of the effects of MAC on individual pilot workload levels. Results indicate multiple critical factors that affect the implementation of MAC. Although the model suggests that pilots may experience relatively low workload when operating a single UAS during benign operations, workload builds rapidly when the pilot is required to operate three or more aircraft. The results of this model indicate the need for techniques and technology to reduce task and communications demands on UAS pilots to effectively implement MAC.
7.1.2 System of Systems Engineering Facilitates Integration of Large Scale Complex Systems
Authors: Mazzuchi Thomas , Albakri Ghazi 
Published: November 2014

ABSTRACTSystems of Systems Engineering, SOSE, is a new field and opens a wide challenge for Systems Engineering researchers who are dealing with large scale complex systems. Integration is one of many tasks required by Systems Engineers who are involved in the process of acquiring a working system that fulfills the main mission of the large scale system. Generally, there are three large scale complex systems cases that need to be integrated: 1) new systems with new systems, 2) old systems with new systems, and 3) old systems with old systems. In the literature, the main focus of the research is on Systems Engineering integration processes for systems which are still under design and before their final phase‐out. This research presents a contribution to define the System of Systems Engineering (SOSE) science through facilitating the integration of two existing large scale complex systems “old system to old system” into one using a simple and clear new process model for integration. One of the reasons for selecting this case is the significant need to integrate “old systems with other old systems”.The integration process has many approaches and models, i.e. V‐Model which is mostly used during the life cycle of building a system. What makes this research unique is the introduction of the “M‐model” that facilitates integration of “existing / old” large scale complex systems with each other. The M‐Model starts with defining the “Problem statement,” then the sequence of building‐up documents and plans leads to a master plan documented called “SOSE Master Plan (SOSEMP).” Some case studies will be discussed.
7.5.1 Capacity for Engineering Systems Thinking (CEST) and Project Success
Authors: Frank Moti , Sadeh Arik , Ashkenasi Sharon 
Published: November 2014

AbstractDespite the vast amount of literature available on systems engineering and project management, about two‐thirds of all projects still fail. A review of both project management and systems engineering publications reveals that most of these works focus on processes. We suggest focusing on people – project managers and systems engineers. One of our previous studies dealt with project managers; the current paper focuses on systems engineers. The paper presents findings of a study aimed at exploring the relationship between systems engineers' capacity for engineering systems thinking (CEST), project types and project success. The study findings show that there is a significant correlation between CEST and project success. The extent of the project's novelty is a moderator variable that affects this correlation. The more innovative the project is, the higher the correlation between the subjects' CEST and project success.
8.3.2 Using FMEAs to Improve Healthcare Study Design
Authors: Baird Pat 
Published: November 2014

AbstractThere is an intense focus in the United States on ways to improve Healthcare Quality. However, the process of measuring quality improvements can be difficult. This paper proposes the use of traditional FMEA techniques on study design, with a goal of improving the quality of the studies themselves. An example study is examined and a FMEA is performed.
8.6.1 Energy Conservation in Cloud Infrastructures
Authors: Mehta Avinash , Menaria Mukesh , Dangi Sanket , Rao Shrisha 
Published: November 2014

Abstract—With the growth of cloud computing, large scale data centers have become common in the computing industry, and there has been a significant increase in energy consumption at these data centers, which thus becomes a key issue to address. As most of the time a data center remains underutilized, a significant amount of energy can be conserved by migrating virtual machines (VM) running on underutilized machines to other machines and hibernating such underutilized machines. This paper aims to design such a strategy for energy‐efficient cloud data centers. It makes use of historical traffic data from data centers and uses a service request prediction model which enables the identification of the number of active servers required at a given moment, thus making possible the hibernation of underutilized servers. The simulation results indicate that this approach brings about a significant amount of energy conservation.
9.2.1 Transforming systems engineering from a cargocult to a rigorous evidence‐based profession: Empirical research into the foundations of ISO 15288 and ISO 26702
Authors: Sparrius Ad 
Published: November 2014

AbstractSystem engineering is becoming a standards‐driven profession, with an increasing number of ISO standards de facto documenting the body of system engineering knowledge. However, the hard evidence to back up those standardization efforts is lacking. Few, if any, controlled experiments have been conducted. For instance, if a new aircraft were to use a novel new material, it would be reasonable to assume that the strength of that material had been carefully determined by rigorous experiments. System engineering has not been subjected to similar engineering practices.System engineering needs robust research to provide a solid foundation for it, but unfortunately such research is sadly lacking. This paper will identify the foundation of system engineering and determine whether or not it is evidence‐based and backed up by serious research. It will also identify some outlines for system engineering research.
9.6.2 INTEGRATION OF OPERATIONS IN PROCESS SYSTEMS: COMPLEXITY AND EMERGENT PROPERTIES
Authors: Hessami Ali G. , Karcanias Nicos 
Published: November 2014

AbstractThe problem of system Integration in the context of an Industrial Enterprise is a multidimensional problem with fundamental dimensions those of: (i) Purpose, goals and objectives, (ii) Overall process operations, (ii) Overall System Design/Redesign, (iii) Information, Data and Software, and (iv) Verification, validation and assurance. Each of the above areas is addressed by respective groups which consider their area as representing the entirety of the problem and they frequently ignore the other important dimensions. The aim of this paper is to consider first the general problem of integration from all its fundamental aspects and focus on the key paradigm of Global Operations. Within this area we consider the issues of system organization and in particular the problems relating to hierarchical organization of the different operational functionalities, the issues of aggregation and disaggregation and the related problems of the “top‐down” and “bottom up” approaches. System complexity is considered within this framework and the notion of emergent properties is then considered as a problem of aggregation of behaviours, which may be also seen as projections within the setup of a control and information architecture. Such an architecture is defined for the multi‐level hierarchical organisational structure that we consider. We show that systems and control concepts and problems play a central role the development of an overall integration methodology and interpreting the features of the different emergent properties. The subject of modelling emerges with a central role in the effort to develop a methodology for systems integration, as well as quantifying the predictors of relevant emergent properties. The approach introduced here is intimately linked to Multilevel hybrid systems (Hierarchy of Operations), and provides a complementary dimension to issues of System Design (and Re‐design) dominated by the theory of Structure Evolving systems [10] (in the total Design and Life‐cycle analysis) emerges as the central approach. This paper provides an overview of the subject area and focuses on the development of the general conceptual framework for integration. We additionally develop and propose a systems framework for the evolutionary integration in this paper.
10.1.2 Legacy Software System Integration
Authors: Knapper Robert J. , Brouse Peggy S. 
Published: November 2014

AbstractLegacy software systems are often the subject of analyses in attempts to affect modifications to extend their useful lifetimes. For the systems engineer, reengineering legacy systems or integrating legacy systems with new development and/or off‐the‐shelf software are areas which may provide particular challenges and where effective software system analysis is critical. When analyzing a software system, a range of system artifacts may be used. These artifacts include a description of the system in natural language, program design language descriptions, flow charts, object diagrams, as well as the system code. All of these artifact types can contain equivalent information at their specific level of abstraction. However, deriving information that is needed for reengineering or integrating a legacy system from each of these artifacts cannot be performed equivalently. For example, analyzing a poorly structured system with little or no design documentation is a particularly challenging problem. Software modeling using an abstract architecture representation as a common description vehicle, such as the Unified Modeling Language or some other, can “level the playing field” by creating representations of disparate systems at the same level of abstraction. This is of importance to reengineering efforts; it shows promise for supporting and facilitating integration efforts between legacy and other systems. This paper presents a methodology to express and manipulate (i.e. restructure) system architecture‐level models, an evaluation of the integratability of those models, and proposes a decision support system framework that makes the use of the methods.
10.4.1 Sizing Systems Engineering Activities to Optimize Return on Investment
Authors: Honour Eric 
Published: November 2014

AbstractThis work continues significant results from the Systems Engineering Return on Investment (SE‐ROI) project that has quantified systems engineering (SE) success using extensive interviews with real programs. In prior work the project reported that effective systems engineering (SE) at a level of approximately 15% of a project cost optimizes cost, schedule, and stakeholder success measures. The project also identified a set of effective characterization parameters for quantifying SE. This work explores the relationship between the characterization parameters and the success correlations. It is shown that eight major SE activities can be “right‐sized” based on the characterization parameters of a program as an a priori estimation method to optimize the ROI of the activities. The paper shows the quantified relationships, based on the database of interviews. Two example programs demonstrate the method and illustrate the typical optimized level of SE activities.
10.4.2 Convergence of Expert Opinion via the Wideband Delphi Method: An Application in Cost Estimation Models
Authors: Valerdi Ricardo 
Published: November 2014

AbstractThis paper discusses the notion of collective intelligence through the application of the Wideband Delphi method as a way to obtain convergence among a group of experts. The specific application is the definition and calibration of cost estimation models that use data collected from experts as part of their calibration. Convergence is important in this case because companies need to commit to cost estimates early in the planning cycle since so many other decisions are dependent on it. Our results demonstrate that, in most cases, convergence among experts can be achieved after three rounds of the Wideband Delphi.
11.2.3 Systems Concurrent Engineering of a “Green” Car
Authors: Alarcón Javier Efrain Gonzales , Loureiro Geilson 
Published: November 2014

ABSTRACTIn this paper we present the systems concurrent engineering approach to the development of complex products for the automotive industry having as a product a “green car”. Traditional approaches focus on the product, the organizational development and product concepts of operation (CONOPS). This approach is the integration of the Systems Engineering and Concurrent Engineering approaches. Systems Engineering is a multidisciplinary and collaborative engineering approach for deriving, evolving and verifying a system solution, balanced throughout its life cycle, and that meets the expectations of stakeholders and public acceptance. Concurrent Engineering is an engineering approach that anticipates, to the initial stages of development, the product requirements from the life cycle processes such as manufacturing, assembly, testing, maintenance and logistics and disposal of the product. This paper presents the approach of Systems Concurrent Engineering. Systems concurrent engineering acknowledges that the system solution is comprised of product and organization elements. Each product life cycle concept is thought from the outset and using a top‐down approach, from the product context at a given life cycle process scenario. The systems concurrent engineering approach includes in the scope of development effort, not only the development organization, but also the other life cycle processes that a given development organization performs. The approach is exemplified using the case of the development of a ‘green car‘, a car that is environmentally friendly.