bluuebunny/crossref_metadata_2025_split huggingface dataset:
7.3.4 Optimising the Value of Systems Engineering
Authors: Honour Eric C. 
Published: November 2014

AbstractHeuristic, intuitive wisdom holds that the practices of systems engineering have high value in the development of complex systems, yet no accepted methods exist to measure that value. In this theoretical paper, the quantitative value of systems engineering is proposed as measurable in several definitive and objective ways. The scope of systems engineering in this context is defined in the broadest terms, matching the perceived value held by those who hire systems engineers. Major components of systems engineering are described in two dimensions: task categories and development system attributes. Measurable value of these components is proposed using three product‐level measures: technical quality, risk avoidance, and problem discovery. Finally, a useable program is proposed that can lead to the information necessary to optimise the use of the systems engineering components.
3.5.2 Virtual Collaboration, e‐SE, and Team Sports Metaphors –Opportunities to Innovate, Integrate, and Invigorate
Authors: Pohlmann Lawrence D. , Myers Kenneth N. , Eilers Richard L. 
Published: November 2014

AbstractParticipation in virtual teams performing systems engineering‐related activities is a part of our collective destiny. While many of the functions of systems engineering (SE) are already difficult, they may be even more challenging in virtual team settings. As we transition to an electronic‐systems engineering (e‐SE), our success will depend in part on whether the environment, training, culture, infrastructure, and processes provide the appropriate support for various types of virtual collaboration that will occur within a project or enterprise.This paper characterizes several models of collaboration and virtual collaboration – some of them based on team sports metaphors. We identify and describe different kinds of web‐based support that may be advantageous to these variations on the collaboration theme. In the process, we identify a variety of opportunities for innovation and integration – all with the aspiration of helping to invigorate SE‐related virtual team processes and activities.
1.6.2 Application of Computer‐Aided Systems Engineering to Develop Automated Guided Transit(AGT) System Architecture
Authors: Park Joong Yong , Lee Joong Yoon , Mok Jai Kyun , Park Young Won , Ahn Jang Keun , Lee Woo Dong 
Published: November 2014

AbstractAutomated Guided Transit (AGT) system is a complex and large system in which there are many subsystems, interfaces, functions and demanding performance requirements. Because many contractors participate in the development, it is necessary to apply methods of sharing common objectives and communicating effectively among all of the stakeholders. This paper shows not only the methodology and the results of computer‐aided systems engineering including requirement management, functional analysis and architecting the AGT system, but also an application of the tool to help manage a project by linking WBS (Work Breakdown Structure), work organization and PBS (Product Breakdown Structure). The application of computer‐aided tool, RDD‐100, provides the capability to model product design knowledge and decisions about important issues such as the architecting rationale of the top‐level system. The product design knowledge will be essential in integrating the follow‐on life‐cycle phase activities over the life of the AGT system. Additionally, when a new generation train system is required, the reuse of the database can increase the system design productivity and effectiveness significantly.
5.7.4 Support for Object‐Orientation in AP‐233
Authors: Pandikow Asmus , Törne Anders 
Published: November 2014

AbstractThis paper is motivated by the need to bridge the gap between the engineering methods used in software engineering and those used in systems engineering. Different alternatives attacking the problem are presented and evaluated. An implementation of one of the alternatives is described, namely the inclusion of the most important object‐oriented concepts from the OMG Unified Modeling Language (UML) into the working draft 5 of the ISO‐10303‐233 (AP‐233) systems engineering standard proposal. These concepts have also been integrated into the AP‐233 structures for version and configuration management and hence, allow now for the traceability of design elements between systems and software specifications. The extensions allow to include UML conformant tools in AP‐233 controlled system designs and on the other hand, the use of AP‐233 management capabilities for designing software.
7.7.1 Knowledge Management in Collaborative Product Development
Authors: Fagerström Björn , Olsson Lars‐Erik 
Published: November 2014

AbstractAn increasing amount of main suppliers are using sub‐suppliers to perform different tasks in the product development process. As a result, the knowledge needed for developing a new product will be distributed throughout many actors. Knowledge management is a comprehensive term for providing the right piece of knowledge to the right persons at the right time. This paper deals mainly with the question for how knowledge is managed in the collaborative product development between main and sub‐suppliers (system level). The result is based on a case study with one main supplier and ten of their sub‐suppliers, in which the main suppler develops, assembles, and delivers a whole, complex product to the customer. The study shows that the sub‐suppliers' knowledge and experiences are not fully utilized in the relationship with the main supplier. Some different ways of working are discussed in the paper's conclusions section, to improve the knowledge exchange between main and sub‐suppliers.
1.2.2 Better Systems Engineering with Dialogue
Authors: Backlund Göran , Sjunnesson Jan , Johansson Ingemar 
Published: November 2014

AbstractManaging knowledge involves having the ability to establish intersubjectivity between a group of individuals. This paper describes two case studies where an advanced and highly structured dialogue is used as the key instrument for generating new ideas, and for establishing a common understanding of a new subject. Together with Prof. Bo Göranzon at the Department of Skill and Technology at Sweden's Royal Institute of Technology (KTH), Combitech Systems AB spent four years developing Dialogue Seminar method. After a period of thorough testing at Combitech Systems, the method has been in use at a number of other development organisations. The method is based on a view of knowledge developed by philosophers such as Aristotle, Descartes, Diderot and Wittgenstein, where tacit knowledge—or experience‐based knowledge—is central. The purpose of the concept is to give a wider understanding of knowledge, and the basic procedure involves training people to change perspective in order to stimulate new thinking. The three different cases clearly demonstrate that the Dialogue Seminar method can be successful in different situations, for example, gathering experience from a completed project, establishing a common language in a newly formed team or helping to specify a new product.
2.2.4 Operational Concepts and the Case for Use Cases: Unifying UML with Systems Engineering
Authors: Jorgensen Raymond 
Published: November 2014

AbstractOperational Concepts have been used in varying degrees for many years by government acquisition agencies and contractors to help understand the operational nature of systems. Seldom, however, have the concepts been used at subcontractor levels or been encouraged by subsystem developers. Nor has there been much formality in the use and structure of the operational concept document (OCD). The typical content of the OCD remains highly textual with verbose description and little discipline in the thought process. The Unified Modelling Language (UML) has, however, introduced the notion of the Use Case, which, when examined as to purpose and focus, may provide an excellent basis for formalising the OCD content and providing a tool to help capture more effective operational scenarios at all levels of system composition. This paper explores the use of the UML Use Case as an essential part of the system Operational Concept.
4.2.2 Organizational Safety: A Systems Engineering Perspective
Authors: Jackson Scott 
Published: November 2014

AbstractNumerous studies have shown that organizational factors are contributors to major accidents, in particular, catastrophes, such as Chernobyl and Challenger. Organizational safety, as distinguished from industrial and system safety, can be viewed in a systems engineering context. Case histories of these and other disasters are reviewed with a focus on the organizational aspects. First, the systems engineering concept of the development and support systems, that is, the engineering and support organizations, as categories of enabling systems dictates that these systems be considered concurrently with the operational system in establishing the total system requirements. Secondly, the systems engineering processes of requirements development and synthesis enable the creation of an organizational system which meets the total system requirements for safety. Finally, systems of verification are addressed, both externally mandated systems as well as internally conducted audits.
4.2.3 Systems Engineering Approach for Modeling An Organizational Structure
Authors: Rushton Gary , Zakarian Armen , Grigoryan Tigran 
Published: November 2014

AbstractAn organization is just another type of system. Why not use systems engineering techniques for modeling and development of the organizational structure. Within every organization there are required tasks/functions that interact with each other. Therefore, one may use system engineering techniques to define what the organization is required to do and then develop an organizational structure using some basic design principals, e.g., integration analysis technique to minimize coupling and maximize cohesion between various organizational tasks and functions. In this paper, we illustrate how systems engineering design principles can be used for modeling and analysis of an organization structure.
3.5.5 Integrated Cost / Schedule Risk Analysis
Authors: Hulett David T. , Campbell Bill 
Published: November 2014

AbstractProject costs often exceed their estimates because those estimates do not take into consideration the actual duration of project activities. Cost risk will also be underestimated if it does not take into consideration schedule risk. This paper presents a method of incorporating the uncertainty in activities' durations into the assessment of cost risk. In this method, a Monte Carlo simulation of the schedule provides uncertainty in time. Incorporating the schedule risk results into the cost risk model provides the linkage between schedule and cost risk. Then equivalence must be established between the schedule and network concepts. Uncertainty in costs is then represented by uncertainty in “independent costs” (costs that do not depend on time) and “variable costs” (costs that depend on uncertain time and cost per unit time or “burn rate” and rate of labor compensation.) Simulation of the cost model combines the results from the schedule risk analysis with the uncertainty in the cost assumptions. The results include the probability distribution of total project costs and sensitivity of that distribution to the different inputs. Issues are discussed and simplified examples are provided.
5.5.5 Systems Engineering with ICDM – A Case Study
Authors: Herscovitz Jacob , Hari Amihud 
Published: November 2014

AbstractThis paper presents and demonstrates the design of a new system using the ICDM method.ICDM is an Integrated, Customer Driven, Conceptual Design Method that encompasses the entire process of conceptual design, starting from customer needs up to the selection of the best solution to that need.In an engineering design process, the most critical phase is the initial conceptualization of the needed system or product, where about 75% of its life cycle cost is committed (Blanchard 1978). Therefore, using efficient methodologies and practices during this phase is essential to the whole effort success (Pahl 1984).ICDM, demonstrated in this paper, is a flexible 10 step method, tailorable to multifaceted project needs and organization's requirements.The case study describes the stages of a system definition and conceptual design of a Personal Identification of Friend or Foe system ‐ PIFF. The problem behind this need is defined as the difficulty of friend or foe identification in terror fighting or infantry arena.As a result, the case study showed the ability of ICDM to enable quick and efficient team decisions upon the customer needs and produced an optimal conceptual design that scored the best in terms of Customer Satisfaction Rating (CSR).
2.6.4 An Initial Application of AP‐233
Authors: Scott William , Cook Stephen C , Harris David , Smith John , Johnson Julian 
Published: November 2014

AbstractThe System Engineering Design Methodologies (SEDM) project is concerned with potential avenues to exploit the AP‐233 system engineering data exchange standard. The project is a joint venture between the System Engineering and Evaluation Centre of the University of South Australia and BAE SYSTEMS Australia. The work described in this paper covers the design and implementation of an import interface from the AP‐233 data model to DOORS. The project showed that AP‐233 is an effective medium for tool independent transfer of systems engineering information.
5.6.2 Decision Making in Modular Product Platform Development
Authors: Ofer Christian M. , Otto Kevin N. , Whitcomb Clifford , Igenbergs Eduard , Schulz Armin P. 
Published: November 2014

AbstractIn order to achieve larger market share and address individual customer needs, firms are challenged to manage the seemingly contradictory existence of internally low variety and a maximum external variety. One very powerful approach is to use modular product architectures (PA). This permits one to establish product families based on platforms.Using platforms is a common strategy in diverse industries. For development of platform architectures, there are almost infinite possible configurations. There is a need for a framework for evaluation and selection of possible concepts. By evaluating design concepts one is faced with decision‐making. To do this, one must make choices over a distinct evaluation method and effective metrics. In this choice, the quality of information is the limiting and determining factor, it is the differentiating characteristic among methods. To show this, diverse methods will be presented and their characteristics and benefits will be discussed.
6.6.3 Safety Systems Intervention Plan for Yellowstone National Park
Authors: Plowman Catherine , Alessi Sam 
Published: November 2014

AbstractManagers of Yellowstone National Park are interested in improving both the safety performance and the systems design and project management capability of the Park's personnel. The objective of our research was to address this need by constructing a safety enhanced Capability Maturity Model that will simultaneously assess systems design and safety. This approach advances the integration safety into business decisions and identification of ‘leading’ indicators of safety performance. We modified the EIA 731 Capability Maturity Model to include a focus on safety management systems. This model was used to assess the safety culture at Yellowstone National Park (YNP) in the spring of 2001. Using the standard assessment approach, results from the safety‐augmented survey were used to target specific areas of investigation. Results from the interviews and focus groups led to a collection of information and potential improvement opportunities that were subsequently used to develop a five‐year safety system intervention plan for the Park. This paper deals with the intervention plan development that occurred after the standard CMM assessment activities were completed.
3.1.1 COSYSMO: A Constructive Systems Engineering Cost Model Coming of Age
Authors: Valerdi Ricardo , Boehm Barry W. , Reifer Donald J. 
Published: November 2014

AbstractBuilding on the synergy between Systems Engineering and Software Engineering, the Center for Software Engineering (CSE) at the University of Southern California (USC), is in the process of developing a parametric model to estimate Systems Engineering costs. The goal of this model, called COSYSMO (Constructive Systems Engineering Cost Model), is to more accurately estimate the time and effort associated with performing the system engineering tasks defined by ISO/IEC 15288.This paper outlines the work accomplished thus far by USC, in collaboration with its Corporate Affiliates and the INCOSE Measurement Working Group, to develop the initial version of COSYSMO. This paper describes the development of the model, explains both its size and cost drivers, and outlines future steps that need to be taken to guarantee COSYSMO's successful adoption by the Systems Engineering community.
1.2.1 The Role of Systems Engineering in Combating Terrorism
Authors: Mackey William F. , Crisp Harry , Cropley David , LongPresident James , Mayian Stephen , Raza Shabaz 
Published: November 2014

AbstractFollowing the terrorist events of September 11, 2001, several members of INCOSE have become involved in international, regional, and local activities to respond to those events that have shaken the international community. A charter for the INCOSE Systems Engineering Initiatives Technical Committee (SEITC) and an Anti‐Terrorism International Working Group (ATIWG) were established in October 2001. INCOSE ATIWG members are applying the multidisciplinary approach of systems engineering to understanding all facets of terrorism. The ATIWG convened a special panel at INCOSE 2002 in Las Vegas, NV, using the same name as the title of this paper. Rather than lose the information conveyed during that session, many of the panelists agreed to join their efforts to coauthor this paper and document much of what was said.This paper's thesis is that the multidisciplinary approach of systems engineering is useful in evaluating terrorist threats, identifying potential target vulnerabilities, and reducing or eradicating international terrorism.
4.2.2 Trust Lubricates the Organizational System: The System Dynamics Approach
Authors: Kurstedt Harold , Tech Virginia 
Published: November 2014

AbstractTo be systems thinkers, we must easily and comfortably integrate human subsystems into complex systems. We can diagram dyadic and triadic human relationships to better analyze, design, and implement complex systems containing human subsystems. Trust and distrust are separate but linked state variables. Trust is fragile and distrust is robust because they fit differently into the system structure of the dyadic relationship. Key considerations for trust in the organization include risk and experience. From a systems perspective, we must design into the organization and our dyadic relationships the structure needed to increase trusting and trustworthy behaviors and to reduce opportunistic behaviors. These behaviors are bound together in feedback loops that define the structure of our relationships. We determine that structure using system dynamics tools. These tools provide the needed understanding of trust to identify steps for changing the relationship or organizational system structure that leads to changed behavior.
4.2.3 Mentoring Technical and Professional People in Today's ‘Demented’ Environment
Authors: Haskins Bill R. 
Published: November 2014

AbstractToday, organizations increasingly place value on individuals who not only can adapt, but also can learn quickly—indeed, who can ‘learn how to learn‘. The recognition of mentoring as an important transfer mechanism for knowledge within organizations has grown significantly in the past couple of decades. Mentoring has become a prime tool for individual survival and professional development. As a professional development strategy, mentoring is a process whereby a more experienced employee (mentor) serves as a role model, provides support, direction, and feedback to the less experienced employee (mentee) regarding career plans and interpersonal development, helps develop specific skills and knowledge that will enhance the mentee's professional and personal growth; and increases the visibility of the mentee to decision makers in the organization who may influence career opportunities. Today, mentoring is being used by many organizations to seek a competitive advantage in a global marketplace.
6.2.4 Evolutionary Project Management (Evo): How to Manage Project Benefits and Costs
Authors: Gilb Tom 
Published: November 2014

AbstractEvolutionary project management is one of many non‐waterfall (Iterative, Incremental, Spiral, Evolutionary Acquisition) project management methods used in industry today. The variation described here is the current view of the author, who has applied Evo since 1960 on real projects, both personally and through clients and students. The central distinctive characteristic of this version of Evo is its focus on quantified specification and tracking of multiple performance and cost requirements during early and frequent Evo steps of result delivery to stakeholders.
3.3.2 Object Oriented Architecture for Collaborative Web‐Centric Configuration Management of Military Rotorcraft
Authors: Stanilka Stanley P. , Dagli Cihan H. 
Published: November 2014

AbstractRotorcraft configuration management is a process, which documents performance, functionality and physical attributes of a military helicopter. This process applies technical and administrative surveillance against a certified design baseline and controls change incorporation throughout the life cycle of the aircraft. The United States Department of Defense (DOD) provides guidance on configuration management through military handbook MIL‐HDBK‐61A and EIA Standard 649. The data governed by configuration management processes can be viewed as a colossal mixture of design drawings, technical service manuals, change documents, material & process specifications, test plans, maintenance & repair records and many other forms of accountability. This paper describes how a collaborative network can be modeled around this configuration management requirement. It will partition and decompose rotorcraft‐engineering data into independent configuration management items and explain how Object Oriented (OO) design philosophies and Unified Modeling Language (UML) methods can maximize an architect's ability to integrate disparate data into a collaborative network.
6.3.3 Cost Effective Systems Engineering for Companies that Build‐on‐Speculation
Authors: Lentz V. A. , Lerner Bruce 
Published: November 2014

AbstractThe System Engineering community has long been looking for a Systems Engineering solution for ‘Commercial’ Systems Engineering. Our recent initiatives in the cost effective practice of System Engineering for one commercial enterprise leads us to believe that the differentiation between the two types of System Engineering might be in the business strategy. Does the company build‐to‐specification (BTS) or build‐on‐speculation (BOS)? That is the question. The answer is still evolving. However, the insight from more than 5 years of trying to apply the Mil‐Aero SE Process to engineering for a commercial enterprise that enters new product development on speculation, leads us to believe there are indeed differences. Continuing to focus on making the case for the value of Mil‐Aero style system engineering to the ‘commercial’ enterprise doesn't get us to the cost effective solution build‐on‐speculation businesses need. We offer some thoughts about the differences, and the allowances that need to be made. We provide some directions for organizing the SE methods to cost effectively provide the advantages of Systems Engineering to an organization that builds‐on‐speculation. Note: We borrowed the term ‘Build on Speculation’ from the construction industry. We are using it to identify a company that brings new product to market without a specific buyer or contract.