bluuebunny/crossref_metadata_2025_split huggingface dataset:
3.3.2 Systems Decision Making Failures in Replacing the World Trade Center
Authors: Benjamin Donald 
Published: November 2014

AbstractThis paper is my senior honors project for the Department of Systems Engineering at West Point. Dr. Gregory Parnell, Professor of Systems Engineering at West Point, is my advisor. This paper directly addresses multiple topics of interest of the symposium including system safety and security, managing environmental impacts, use of human resources, and continuous systems development.This paper examines, from a system engineer's perspective, why six years after 9/11 no above ground construction on the Freedom Tower has occurred and how systems engineering should have been used to start rebuilding faster and with a better design. Three issues impeded the development of the Freedom Tower. First, battles for decision making authority continually halted the progress of the project. Second, the exclusion of stakeholders upset many who felt they should have had a say in the rebuilding process. Third, the decision makers did not always consider the values and objectives of the stakeholders. An adequate understanding of stakeholder values would have improved the process of replacing the World Trade Center.
4.4.2 Making Decisions That Have Global Impact
Authors: (Hal) Mooz Harold , Forsberg Kevin 
Published: November 2014

AbstractMaking good decisions is fundamental to everyone's personal and business success. Yet most of us pass through life unskilled in making decisions. Our actions often result in poor choices and undesirable outcomes. Moreover, when the world's situation is critically examined it is obviously fraught with poorly made decisions that will continue to impact entire societies for some time to come. (Consider foreign policies, war, economic tactics, etc.) Globally applied system engineering begs for the application of sound decision making that is rooted in logic, based on facts, and is consistent with high standards of global morals and ethics.This paper examines decisions, decision significance, the many decision influencers, and the available alternative selection methods. The objective is to enlighten decision makers to become decision fit and to be sufficiently skilled to reliably make quality decisions.
5.2.1 On the Various Conceptualizations of Systems and Their Impact on the Practice of Systems Engineering
Authors: Martin James N. , Ferris Timothy L.J. 
Published: November 2014

AbstractWe all have a tendency to confuse an object we observe with the conceptualization of that object. Most of us would not consider this to be a fatal flaw, but when it comes to systems thinking and applying this to systems engineering this tendency could have serious consequences. The object we observe that we call the “system” is not really the system itself. The system is really the “point of view” we take when we properly deal with engineering of what is commonly called “the system”. We will explore in this paper what it means to think of something “as a system” and how we can avoid the common tendencies that get in the way of truly holistic thinking.
5.4.2 The Impact of Environmental Issues on Rolls‐Royce Design Systems and Solutions
Authors: Beasley Richard , Clifton Andrew 
Published: November 2014

AbstractThe prime function of a Power System (e.g. a gas turbine) is to produce power. However, an important side effect of producing and operating such a system is an impact upon the environment. Noise has long been a significant factor, and has been made the subject of firm regulation in Civil Aerospace. More general environmental impact is increasingly becoming the subject of similar concern and regulation. This paper describes how Rolls‐Royce is translating environmental issues into understood and quantifiable requirements, and creating design systems to allow environmental attributes to be assessed. This approach is enabling Rolls‐Royce to organise itself (in terms of process, tools and understanding) to take proper account of environmental issues during the creation of Power Systems.
6.2.2 The Role of Lifecycle Systems in the Through‐life Engineering of System Solutions
Authors: Mackley Tim 
Published: November 2014

AbstractThere are many examples of failures of systems both in terms of their operation and acquisition. In many of these cases, not enough consideration was given to the system context and the needs/ requirements that these place on the system. These wider contextual aspects, how are they identified and where the system boundary should be defined to enable a whole system approach is key.This paper attempts to identify the following:
the key aspects of a system to consider in order to achieve a whole system approach
the key dependencies on the wider context in order to identify the important tradeoffs to be considered when developing and operating a system
how these wider aspects might need to be considered for different acquisition approachesThe conduct of the analysis in this paper uses a traditional Systems Engineering approach to the problem. It examines the functionality required, identifies the associated form and reviews this against the broader context and required behaviour.A Whole Systems Model (WSM) is proposed that helps focus attention on the broader aspects that need to be considered for a system throughout its life.
6.4.1 Managing Ports and Harbours as Sustainable Complex Systems
Authors: Allan Lucy , Godfrey Patrick , Allan Jeff 
Published: November 2014

AbstractPorts and harbours are very large infrastructure projects which have great impact on the community, environment and the economy of a country. Ports are not only a vital lifeline link between water‐side and land‐side traffic, but are also sources of national wealth, pride and concern. Stakeholders now want requirements to be described in a creative, rigorous, and policy‐relevant manner and for critical issues such as sustainable development to be incorporated into developments. This paper looks at the issue of sustainable development for ports and harbours as potentially being one of managing complexity, and it considers how holistic system requirements may be accommodated in this process. It also suggests that currently not enough use is being made of stakeholder data – economic, social, and environmental ‐ and that significant operational improvements could result from closer attention to this issue.Most of the problems related to sustainability and sustainable development are typically complex and inter‐related. It has been shown that the more complex a system the harder it is to manage, although a certain system complexity is needed for both short and long‐term functionality. By having insights into the causes of complexity in systems enables decisions to be made and actions to be taken where otherwise there may be lost opportunities and ultimately reduced profits, or damage to social and environmental networks. Ports have to achieve a harmonious balance between the local community, the environment and economic issues. By applying systems engineering techniques and ideas surrounding complexity management this paper looks at the designing and subsequent management of ports & harbours and in so doing to develop better overall strategies. Research work into a number of operational sub‐processes is used to gain insights into where measures of complexity may be further developed.
7.2.1 Building Bridges Between Systems and Software with SysML and UML
Authors: Hause Matthew , Thom Francis 
Published: November 2014

AbstractSystems are becoming increasingly reliant on software. One of the roles of the systems engineer is to perform a trade‐off analysis of the different architectural solutions to a problem, and allocate requirements to different engineering domains within that solution, including software. It is important to investigate effective ways of establishing traceability from the system definition to the software and other requirements. The Systems Engineering Language, (SysML), which is based on the Unified Modeling language (UML), is being increasingly used by systems engineers to model systems. As well as providing system requirements, SysML models can be used to define the system architecture to be used by the software engineers. In this paper, we will demonstrate how SysML and UML can effectively work together to provide an effective handover between systems and software.
7.2.3 On enabling a model‐based systems engineering discipline
Authors: Denno Peter , Thurman Thomas , Mettenburg John , Hardy Dwayne 
Published: November 2014

AbstractThis paper considers the requirements of a model‐based systems engineering (MBSE) discipline and the benefits that would be realized from it. A premise of MBSE is that the technical environment supporting systems engineering has evolved, and is still evolving. We analyze the basis of systems engineering decision making in conjunction with the technical environment in which it may soon be performed. The analysis provides insight into the requirements that, when met, enable a model‐based systems engineering discipline. We report on our practical experience toward meeting the requirements using UML, SysML, AADL, AP233, and a systems engineering tool interoperability testbed.
7.3.2 Systems Engineering Technical Authority: A Path to Mission Success
Authors: Andary James F. , So Maria M. , Breindel Barry 
Published: November 2014

AbstractThe systems engineering of space missions to study planet Earth has been an important focus of the National Aeronautics and Space Administration (NASA) since its inception. But all space missions are becoming increasingly complex and this fact, reinforced by some major mishaps, has caused NASA to reevaluate their approach to achieving safety and mission success.A new approach ensures that there are adequate checks and balances in place to maximize the probability of safety and mission success. To this end the agency created the concept of Technical Authority which identifies a key individual accountable and responsible for the technical integrity of a flight mission as well as a project‐independent reporting path. At the Goddard Space Flight Center (GSFC) this responsibility ultimately begins with the Mission Systems Engineer (MSE) for each satellite mission.This paper discusses the Technical Authority process and then describes some unique steps that are being taken at the GSFC to support these MSEs in meeting their responsibilities.
7.6.0 How to Engineer the Emergent Behavior of a System of Systems
Authors: Hsu J , Axelband E , Rouse B , Madni A , Sheard S 
Published: November 2014

AbstractEmergent behaviors exist in biological systems, physical systems and human performance. Little is currently known about constructing an interoperable network of systems and the incorporation of known emergent behaviors. The purpose of this panel is to explore the methods and principles in developing an architecture including the emergent behavior.SoS displays a global complexity that cannot be adequately managed by hierarchical structures and central control; therefore, traditional systems engineering and management approaches are inadequate and insufficient for a SoS.The challenge is how to understand the initiation mechanisms of the emergent behaviors for a particular system architecture model so that the resident beneficial or harmful emergent behaviors can be enhanced or mitigated with selected changes in the current system architectural model. Is model‐based the only feasible approach to develop the architecture model with emergent behavior? If this is the answer, what kind of modeling methodology? Should it be solely based on agent‐based modeling? or combination of SysMl and agent‐based? Is SysML ready to deal with emergent behavior?For a non‐modeling consideration, can we plan for the beneficial or harmful emergent properties? How do we overcome development friction that is bound to arise when there are complex, independent, overlapping governances? We may need experiment with “guided” emergence that help produce the desired SoS capabilities and behaviors.The customer requirements for systems‐of‐systems evolve over time. There may only be system‐of‐system modeling at the level of the government agency, who actually procures but does not build, and not at the level of contractors who build the next generation of technologies.Even we have methodology to build SoS architecture, whether model‐base or non model‐base. How do we train systems engineers to understand the emergent behavior to be incorporated in a newly designed SoS?
8.2.2 A Project‐Product Lifecycle Management approach for improved systems engineering practices
Authors: Sharon Amira , Perelman Valeria , Dori Dov 
Published: November 2014

AbstractDeveloping and sustaining complex systems requires collaboration of multidisciplinary teams, coordination of processes, methods and tools, allocation of resources, and utilization of adequate facilities within enterprises. Engineering and management of a system comprises three intertwined domains: the product, the project and the enterprise. Despite the obvious links between them, each domain is distinct and uses its own ontology and toolset. This conceptual separation hinders effective handling of the project and product lifecycle activities within the enterprise. The unified Product‐Project Lifecycle Management (PPLM) collaborative research project aims to establish, implement, and evaluate a methodology for managing and engineering complex enterprise‐wide systems. The resulting software environment will serve as a test bed for proof‐of‐concept of the PPLM vision and approach. The comprehensive PPLM methodology with its software implementation is expected to enhance enterprise‐level systems engineering and management by unifying the product and the project within which it is developed. The paper presents and illustrates the PPLM vision and framework.
9.3.1 Prime Value Method to Prioritize Risk Handling Strategies
Authors: Venkatesh Srini , Noller David K. 
Published: November 2014

ABSTRACTFunding for implementing risk handling strategies typically is allocated according to either the risk‐averse approach (the worst risk first) or the cost‐effective approach (the greatest risk reduction per implementation dollar first). This paper introduces a prime value approach in which risk handling strategies are prioritized according to how nearly they meet the goals of the organization that disburses funds for risk handling. The prime value approach factors in the importance of the project in which the risk has been identified, elements of both risk‐averse and cost‐effective approaches, and the time period in which the risk could happen. This paper also presents a prioritizer spreadsheet, which employs weighted criteria to calculate a relative rank for the handling strategy of each risk evaluated.
10.1.1 Toward an Evolutionary System of Systems Architecture
Authors: Selberg Scott A. , Austin Mark A. 
Published: November 2014

AbstractWhile recent advances in computing/communications technology have enabled the development and managed evolution of large scale system of systems (SoS) applications, lessons learned from industry indicate that these projects are not always successful. A key problem is the lack of a formal framework from which the development and management of SoS architectures can be studied. This paper describes the key ingredients and approaches to formal analysis that we believe will end up in this architectural infrastructure.
10.1.2 The Applicability of Architecture Reference Models
Authors: Hsu John C. , Raghunathan S. , Curran R. 
Published: November 2014

AbstractNetwork communications transmit data as the foundation for the deployment of Net‐Centric Operations (NCO). The data are transferred through a series of layers. These layers form the Architecture Reference Model (ARM). The applicability of several ARMs were presented and discussed. The ARMs can be classified to internet application, military/government application, general (commercial and military) application and company/organizational application. Some of the ARMs are related and augmented each other. Each ARM was developed for a different purpose. There are no good or bad ARMs. The architecture models are developed from the ARM. It is necessary to understand the modeling techniques and systems architecting methods to develop architecture models.
10.4.1 Transitioning to Biofuels: A System‐of‐Systems Perspective
Authors: Riley Cynthia , Sandor Debra 
Published: November 2014

AbstractToday, almost 60% of the petroleum consumed in the United States is imported. The U.S. transportation sector currently consumes for over two‐thirds of the 11 million barrels of oil used in the U.S. each day. Global demand for transportation fuels is increasing dramatically as developing countries expand their economies and become more energy intensive. Clean energy systems are needed to support sustainable global economic growth while mitigating impacts on air quality and greenhouse gas emissions. Biofuels offer a near‐term solution for reducing U.S. oil consumption. Transitioning to a significantly larger biofuels industry will require the creation of a robust biomass‐to‐biofuels system of systems that operates in concert with the existing agriculture, forestry, energy and transportation markets. Using the fuel supply chain infrastructure as a framework, the current petroleum‐based transportation economy, a vision for biomass‐based fuels and the challenges associated with such a massive market and infrastructure transformation are discussed.
11.1.3 Medical Device Development Process
Authors: Jones David J. , Masters Melissa T. 
Published: November 2014

AbstractMedical devices of increasing complexity are central to mankind's continuously expanding ability to save lives and improve the quality of life. Within our business, we often reflect on how fortunate we are to have the opportunity to work on a variety of these remarkable devices. We believe that such rewarding experiences are made possible through the application of a rigorous system engineering process, ensuring that the resulting devices are safe, effective, and successful.This paper describes a deployed System Engineering process tailored for Medical Device Development. This process (based on ISO 15288:2002, the INCOSE System Engineering Handbook and a Legacy Process), integrates compliance to international regulations, embeds a Safety Risk Management process as defined in ISO 14971:2007, and assures adherence to ISO 13485:2003 Quality management systems. Based on the classification and complexity of the device the process is scalable, may be tailored, and supports iterative design and development activities.
11.3.2 Verification Closure Strategies – A Collaborative Systems Engineering Approach
Authors: Haskins Bill 
Published: November 2014

AbstractA collaborative systems engineering approach to verification planning was used to develop verification closure strategies for large complex systems. Verification closure strategies (e.g., Verification Logic Networks) ensure that each Section 3 requirement in a specification is ultimately satisfied. The verification planning process begins with an assignment of a verification method for each applicable Section 3 requirement and developing the associated Section 4 verification text for each verifiable requirement in Section 3 of the specification. Following the development of the Section 4 verification text, a detailed verification closure strategy is developed. Completing the verification closure strategy requires developing the applicable verification objectives to prove compliance with the applicable Section 3 requirement.
KR19 Applying the Sensor Web Enablement Architecture to Reliable Fire Detection
Authors: Echterhoff Johannes , Hahn Daniel , Jirka Simon 
Published: November 2014

AbstractCurrent fire detection systems sense a fire by responding to the by‐products or symptoms of fire like heat, smoke and light radiation. Our aim is to increase the reliability of fire alarms and to eliminate nuisance alarms. A quick incident assessment by continuous tracking of the fire spread and knowledge about the incident location enables the decision making about the fire fighting strategy and adequate resource strategy and resource mitigation planning. In this paper we show an approach how to apply the emerging Sensor Web Enablement technology to this use case for implementing an improved fire detection system in a very efficient manner. A comprehensive description of the architecture of Sensor Web Enablement is given in order to explain how the system is built.
KR24 Use of QRA in Supporting a System Safety Case for the Victoria Line Upgrade
Authors: Regan Lucy , Lucic Ivan 
Published: November 2014

AbstractIn the support of a safety case for a complex system, there is often the need to gain an understanding of the overall risk for the system and the way in which this risk will change. To do this in quantitative terms requires a system quantitative risk model. There are a number of such models available for use in the UK railway domain: for heavy rail, the Railway Safety and Standards board (RSSB) has developed a Safety Risk Model (SRM) which is available to stakeholders, and for the London Underground (LU), a London Underground QRA model (LU QRA) has been developed for each underground line which can be used in support of safety cases.This paper describes the use of the LU QRA in supporting the safety case for the Victoria Line Upgrade (VLU), which involved an upgrade to rolling stock and signalling systems. It describes the primary uses of the model, the main issues involved and the techniques developed in the course of the task.
1.2.3 Systems Engineering Application to Community Innovative Diagnosis System Development
Authors: Wang T.J. , Chin David , Chang Larry 
Published: November 2014

AbstractThe community building is a comprehensive transformation process and the long‐term project for the local community's cultural form, the landscape environment and the life quality. The purpose of community building is to arouse the cooperation consciousness, participation in mutual resolve the society problems for the civil organization. At present, the Taiwan government supports and strengthens the welfares and service functions of the community through this process. Although the appraisal mechanism has the advantage to select a good community, but it also creates problems such as the difference between the appraisal items and community actual results, and individual standards for appraisal reviewers. Other problem such as taking strives for the government funds primarily but the community inhabitants as the auxiliary phenomenon has also appeared.The present study applies an innovation concept in the community building process through the systematic innovation think, methodology and process which combines system engineering technique and information technology to construct a community innovation service platform in order to provide an innovation service environment for the diagnosis and dialogue communication of the community.The present study explores community research papers including community definitions, category and measurement index. It then designs a community innovative index questionnaire. With the help of the result of this questionnaire, statistics analysis, and AHP, this study reveals the community innovative index and the weight factors. The study also gives quantify diagnose results and with the application of system engineering technique and process to construct this e‐platform from the diagnose model.