bluuebunny/crossref_metadata_2025_split huggingface dataset:
6.4.3 Risk Informed Design for System Life Cycle
Authors: Hill Ralph S. , Nutt Mark W. 
Published: November 2014

AbstractMany facilty life cycle activities including design, construction, fabrication, inspection and maintenance are evolving from a deterministic to a risk‐informed basis. The risk informed approach uses probabilistic methods to evaluate the contribution of individual system components to total system performance. Total system performance considers both safety and cost considerations including system failure, reliability, and availability. By necessity, a risk‐informed approach considers both the component's life cycle and the life cycle of the system.In the nuclear industry, risk‐based approaches, namely probabilistic risk assessment (PRA) or probabilistic safety assessment (PSA), have become a standard tool used to evaluate the safety of nuclear power plants. Recent studies pertaining to advanced reactor development have indicated that these new power plants must provide improved safety over existing nuclear facilities and be cost‐competitive with other energy sources. Risk‐based approaches, beyond traditional PRA, offer the opportunity to optimize design while considering the total life cycle of the plant in order to realize these goals.The use of risk‐based design approaches in the nuclear industry is only beginning, with recent promulgation of risk‐informed regulations and proposals for risk‐based codes. This paper briefly summarizes the current state of affairs regarding the use of risk‐based approaches in design. Key points to fully realize the benefit of applying a risk‐based approach to nuclear power plant design are then presented and illustrated in a case study. These points are equally applicable to non‐nuclear facilities where optimization for cost competitiveness and/or safety is desired.
6.5.1 Information System Security Protection Levels—Enabler for a Secure Millennium National Air‐Space System
Authors: Keblawi Feisal , Fujisaki Norm , McGowan Shirley Brewer , Sullivan Dick 
Published: November 2014

AbstractCritical infrastructures, such as the National Airspace System (NAS), offer a challenging set of information security and systems engineering problems. In 1997, the President's Commission on Critical Infrastructure Protection made protecting critical infrastructures in cyberspace a part of the national agendai. Post 9/11, the flying public expects the Federal Aviation Administration (FAA) to apply the right level of focus to ensure safe air travel. Besides understanding the changing threat environment and managing wide‐ranging vulnerabilities, progress depends on improving systems engineering approaches that unify cyber security in mammoth infrastructures such as the NAS. An important ingredient to the FAA's success lies not only in the technology, but also in the agility of corporate infrastructures that protect the NAS. Corporate security applies to the people and the processes that work behind the scenes to integrate appropriate technology and processes to obtain adequate and timely levels of security. As well, corporate security seeks sufficient funding to support the overarching goals for FAA “Information System Security (ISS) Protection Levels,” described here. The ISS Levels offer a strategy for achieving agile and survivable cyber protection for complex systems of systems.
7.5.2 Agile Systems Engineering for Rapid Project Solution Development
Authors: Wilson Mark A. , Mooz Harold (Hal) 
Published: November 2014

AbstractSystems engineers are frequently reminded of the need for “agility” in many ways. We are encouraged to use “agile methods” to develop systems of systems that are “agile performers,” and have inherent “agility,” meaning they can easily and rapidly adapt to continually changing requirements. It seems that “agility” has become management du jour.The concepts of agile development have been prominent in current technical literature. Some writers contend that the underlying fundamentals of agile methods are significantly different from those of traditional development methods. We believe there are agile best practices that have value across a spectrum of development situations. This paper will propose a working definition of agile development as it relates to project management and systems engineering and describe seven key practices of the “Agile Systems Engineering” process. We will leave an examination of agile performers and agile designs to a future paper.
7.5.3 Management of Enterprise Administrative Systems Implementation at United States Capitol Police
Authors: Valivullah Michael , Getter James R. , Kaisler Stephen H. , Armour Frank 
Published: November 2014

AbstractThis paper describes our management of the systems modernization effort at the United States Capitol Police (USCP). The Enterprise Architecture of the United States Capitol Police comprises six broad categories of business applications. Of these six, two represent clusters of IT applications: the administrative information systems (AIS) and the operational law enforcement information systems (LEIS). The Enterprise System Architecture is comprised mainly of these two systems. A number of guiding principles are used to manage these systems modernization activities. One of those guiding principles is to use commercial off the shelf (COTS) products as much as possible to reduce development time and implementation costs. In some cases, we were able to successfully implement COTS products with little or no modifications. However, in others, the COTS products needed extensive modifications due to new, unique or evolving business needs. This paper will discuss the management strategy used to select, consolidate, modify, test and implement systems within the framework of USCP's enterprise architecture. This paper also discusses lessons learned from our system upgrade, conversion, consolidation, migration, integration and modernization experiences.
3.6.4 Discrete System Optimization Using Cost as an Independent Variable (CAIV) Techniques With Distributed Analysis Models
Authors: Malone Brett , Woyak Scott 
Published: November 2014

AbstractA design environment has been constructed to assist designers and analysts in performing concept studies and optimization based on distributed analysis to support cost as an independent variable (CAIV) studies. This environment uses application server‐based techniques to host distributed simulations and analysis tools. These components are then linked through a common client interface to build an integrated model. A set of unique design exploration tools provides the analyst with a decision support environment for performance, cost, and operational assessments. A design example based on this architecture is shown. This example illustrates discrete configuration selection of platform and sensor types based on a non‐gradient based optimization algorithm to defeat various threats given system cost constraints.
6.6.3 Meeting the Needs of Hydrographic Surveying: A Case Study of the Requirements Development Process
Authors: Collier Wayne M. , Shih H.H. 
Published: November 2014

AbstractA long‐standing challenge in oceanography and hydrographic surveying is accurate real‐time measurement of offshore water levels. The advent of recent techniques and technologies has afforded an opportunity to address this challenge. This paper will discuss the requirement development process as it related to specifying requirements for GPS‐tracked buoy for hydrographic survey applications at the National Oceanic and Atmospheric Administration (NOAA). How stakeholders from a variety of technical disciplines collaborated to develop requirements to meet and solve an important operational need via a Small Business Innovation Research (SBIR) grant will be explored.
6.6.4 The Architecture of Problem Resolution During Assembly of the International Space Station
Authors: Johnson Harry F. , Dagli Cirhan H. 
Published: November 2014

AbstractThis paper describes the architecture for solving U.S. on‐orbit hardware/software problems on the International Space Station. Problems are partitioned, prioritized and coordinated and worked via a combination of monitoring, testing, commanding the vehicle, analysis, meetings, e‐mails, formal written requests, and presentations. Progress is measured against prioritized criteria. Throughout, system architectural heuristics are employed. The key heuristics utilized in solving some of the complex problems are examined for their effectiveness.
7.6.1 Integrated Rollout Project Plan Modelling Tool
Authors: Simmins John J. , Quaglio Kenneth , Appel Peter , Boteler Laura 
Published: November 2014

AbstractThe purpose of the Integrated Rollout Project Plan Modeling Tool is to provide a consistent approach to develop rollout plans for a variety of projects and to provide a program management tool to manage key program office analysis and reporting requirements during rollout. The tool captures those attributes that differentiate the rollout at one location from the next and dynamically builds each individual plan to reflect those different attributes. The tool was can collect inputs and dependencies across various functional groups including: Accounting, HR, Manufacturing, Quality, Shipping, Marketing, etc.
3.7.1 Process Implementation
Authors: Sheard Sarah A. 
Published: November 2014

AbstractProcess improvement requires two major steps. First, new processes must be defined (or existing processes modified). Second, the organization must begin to use those new or changed process descriptions. The literature has provided good guidance on writing new process descriptions, but very little has stated clearly what actions must be taken to implement and then institutionalize the use of the processes. This paper provides a list of implementation and institutionalization actions that organizations should consider to ensure that the new processes are used. These actions fall into the categories of training, ensuring management support, obtaining a measurement baseline, auditing the use of the processes, collecting and maintaining a library of process assets, tailoring the processes, improving the processes, and appraising the organization.
6.7.2 Defining an Architecture with a COTS‐Aware Software Engineering Process
Authors: Chung Lawrence , Cooper Kendra , Kaffenberger Ruediger 
Published: November 2014

AbstractThe goals of developing systems better, faster, and cheaper continue to drive software engineering practitioners and researchers to investigate software engineering methodologies that are novel, yet practical. As the size and complexity of systems continues to grow, there has been a growing interest in the investigation of social paradigms (e.g., agent‐ and goal‐oriented approaches) and the use of COTS components. These are being viewed more and more as promising, and also perhaps inevitable, solutions to this problem. The effective application of social paradigms and use of COTS components, however, requires a systematic approach that provides a set of concepts for modeling the subject matter, a set of guidelines for using such concepts, and tool support to assist the developer.In this paper, we present part of a COTS‐Aware Requirements Engineering and Architecting (CAREA) approach that explicitly supports the use of COTS components. Our CAREA approach, an extension of our previous work in system and software requirements engineering, is agent‐ and goal‐oriented, knowledge based, and has a defined process. In particular, we present part of the process that supports the formal definition of a software architecture. Our CAREA approach is validated using a Digital Library System example; a prototype of the CAREA Assistant tool is used to present some of our preliminary results.
2.8.4 Applying SE and CASE Tool to the Jamming System
Authors: Park Moon‐Bok , Woo Byung‐Il , Lee Dale 
Published: November 2014

AbstractThis paper presents the design concept for the phased array T/R (transmit/receive) jamming system collecting the electromagnetic wave, finding the direction and position from the sources, and transmitting high power to the Radar. This system will be added to a stand‐off jamming system in near future. We introduce systems engineering technique to the jamming system in order to scrutinize the behaviour of the system. And using CASE tool, RDD.Com, we provide a good way to design the system in terms of requirement analysis, system architecture and the system verification. Finally we show that SE approach can be a good solution to reduce design risks for a smaller system and technically complex system.
4.8.2 Incorporating Uncertainty into Conceptual Design of Space System Architectures
Authors: Hastings Daniel E. , Weigel Annalisa L. , Walton Myles A. 
Published: November 2014

AbstractThe environment in which space systems are developed and operated can be classified as nothing less than dynamic. This paper introduces an approach to quantify and compare space system architectures around the central theme of uncertainty, with emphasis on policy uncertainty, as well as, technical and market uncertainty. Two cases of implementation are presented and two generalized principles are proposed that flow from the analysis: 1) space systems must be designed with uncertainty as one of the central organizing principles, 2) since space systems have management and social dimensions and thus involve human interactions, there is an irreducible uncertainty associated with these dimensions that will affect the design of the system.
4.8.4 Four Applications of Bayesian Networks for Systems Engineers
Authors: Jean‐Philippe M. 
Published: November 2014

AbstractAmongst many other considerations, Systems Engineering is based on the capability to predict and control the behaviour of a system.The Bayesian networks method is a technique that uses the theorem of Reverend Thomas BAYES, as established about 250 years ago and as developed by the great mathematician LAPLACE.Dealing with the BAYES theorem is usually reserved to mathematicians, since its application quickly requests a high level of mathematical awareness. Most systems engineers have had some courses on BAYES theorem during their studies, but they cannot envision any use of this rusty knowledge in their daily work.The goal of this paper is to describe four practical uses of Bayesian networks, which can be understood by the “regular” Systems Engineer:

Selecting a design and making trade‐offs
Controlling the system behaviour
Assisting the troubleshooting during integration
Facilitating system maintenance
5.8.1 CADM Compliance for Implementations in an Object‐Oriented Environment
Authors: Smith Darold K. 
Published: November 2014

AbstractThe C4ISR Core Architecture Data Model is defined using a relational database syntax. There are many reasons to consider implementing a C4ISR application in an object‐oriented database (OODB) environment, such as intuitive object representation, performance, and efficient support for a highly collaborative work environment.Clearly, the database schema in the object‐oriented (OO) implementation must comply with the CADM definitions, i.e., be CADM compliant, before implementing applications. This raises the question: “What constitutes CADM compliant?” This paper identifies initial CADM compliance requirements and related issues for OO implementation.
5.8.3 Modelling Integrated Systems Architectures
Authors: Schmidt Richard F. , Macdonald Patrick 
Published: November 2014

AbstractThe Navy's Chief Engineering Office (RDA/CHENG) is attempting to establish an advanced methodology for performing “Capability‐based” system acquisition. This requires the modelling of a “Mission‐oriented” Battle‐force where the contributions of each system, and future system concepts, can be assessed in terms of mission effectiveness. The Naval Collaborative Engineering Environment (NCEE) has been established to support this large‐scale engineering effort and the Authors are working towards a modelling framework which properly captures a Mission Capability Portfolio of systems. In addition, the modelling approach is based on the DOD C4ISR Architecture Framework1, and provides a basis for translating the Operational, System, and Technical Views into System Engineering Models. Furthermore, a significant challenge facing this modelling effort is the capture of the emerging concepts driving Network‐centric warfare. CORE, a commercial Systems Engineering tool, is being utilized to support this modelling effort.
Integrating Legacy Systems with Data Reverse Engineering and Patterns
Authors: Heiligenthal Pamela 
Published: November 2014

AbstractLegacy integration remains a major issue in the systems engineering world. Although many temporary solutions have proved successful for existing systems, the need to support dynamic and real‐time business process opportunities will require that we take a closer look at a more long‐term system solution (Sprott et al. 2002). This paper presents a high‐level introduction that will focus on using Data Reverse Engineering (DRE) and the use of patterns as a methodology to solve legacy system integration. Reverse engineering is a viable long‐term solution that will evolve legacy systems in a disciplined manner in order for it to meet new requirements (SEI 1995).
1.1.2 Naval Combat System Design: System Engineering approach and complexity management
Authors: Ciambra Francesco , Nardini Manuela 
Published: November 2014

AbstractNaval Combat System Design is the process which starting from system specification allows to define system architecture and its functional and physical interfaces in order to obtain an integrated system in its natural operative scenario.The large number of components and interdependent systems of a naval Combat System makes it complex. The application of the System Engineering approach, throughout the project's life cycle, consents to manage the system complexity.
1.3.2 Customer focused Engineering in Airbus A380 programme
Authors: de Chazelles Pierre , Comes Michel , Kerrien Anne 
Published: November 2014

AbstractAt the very beginning of a new program, the environment is not stable because nobody is able to know the answers to the future needs from the previous solutions. In this phase, it is necessary to brain storm with potential customers in order to identify new ideas that are emerging and to learn very fast from the feedback, because the target is moving.The elicitation of the basic ideas allows the preparation of a consistent framework of top level requirements and design solutions. It is a factor of critical success for the continuation of the project.Since the beginning of the development of A380, Airbus has organized many workshops (Customer Focus Group / CFG) with Airline companies who are potential customers of the A380, Airports and other stakeholders. These events give the opportunity to elicit customers needs and to provide visibility on design. This is supported by a process that covers:
customer requests capture and validation during workshop or during bilateral meeting;
processing of the request
feedback and acknowledgment by the customer
In addition, the repository used to manage the requests and answers is a source for Top Level Requirements that drives the development of the A380.The role of the CFG is fundamental to support communication between airlines customers and Airbus specialists from all disciplines. It allows establishing a common and clear vision of the purposes to be achieved by the new product.This paper presents the engineering process deployed by Airbus to guarantee the consideration of the customer point of view and ensure its satisfaction on the final product.
1.6.3 Formalizing the Language in Your Universes of Discourse
Authors: Gonzales Regina M. , Joyce Scott , Cuyler David S. 
Published: November 2014

AbstractSemantic understanding of the domain for which a system or solution is being developed is crucial. Defining the ontology as part of domain modelling at the onset of a project permits effective effort as you communicate with stakeholders and move into formal definition of requirements. However, there is another Universe of Discourse in play when working as an integrated product team (IPT) on a project. Many times the terms used by the project team are assumed to be understood, but with the complexity of today's systems, the tools used to create project artefacts, and the teams needed to realize solutions, this is not always the case. This paper will present a case study illustrating the method applied to model, using UML, the ontology for a Universe of Discourse that represents the problem domain and the ontology of the project team developing the solution.
2.1.3 A Systems Engineering Framework for Design, Construction and Operation of the Next Generation Nuclear Plant
Authors: Gorski Edward J. , Park Charles V. , Southworth Finis H. 
Published: November 2014

AbstractNot since the International Space Station has a project of such wide participation been proposed for the United States. Ten countries, the European Union, universities, Department of Energy (DOE) laboratories, and industry will participate in the research and development, design, construction and/or operation of the fourth generation of nuclear power plants with a demonstration reactor to be built at a DOE site and operational by the middle of the next decade. This reactor will be like no other. The Next Generation Nuclear Plant (NGNP) will be passively safe, economical, highly efficient, modular, proliferation resistant, and sustainable. In addition to electrical generation, the NGNP will demonstrate efficient and cost effective generation of hydrogen to support the President's Hydrogen Initiative.To effectively manage this multi‐organizational and technologically complex project, systems engineering techniques and processes will be used extensively to ensure delivery of the final product. The technological and organizational challenges are complex. Research and development activities are required, material standards require development, hydrogen production, storage and infrastructure requirements are not well developed, and the Nuclear Regulatory Commission may further define risk‐informed/performance‐based approach to licensing. Detailed design and development will be challenged by the vast cultural and institutional differences across the participants. Systems engineering processes must bring the technological and organizational complexity together to ensure successful product delivery. This paper will define the framework for application of systems engineering to this $1.5B ‐ $1.9B project.
2.3.1 A Decision Support Framework for Feasibility Analysis of International Space Station (ISS) Research Capability Enhancing Options
Authors: Ortiz James N. , Scott Kelly , Smith Harold 
Published: November 2014

AbstractThe assembly and operation of the ISS has generated significant challenges that have ultimately impacted resources available to the program's primary mission: research. To address this, program personnel routinely perform trade‐off studies on alternative options to enhance research. The approach, content, level of analysis and resulting outputs of these studies vary due to many factors, however, complicating the Program Manager's job of selecting the best option. To address this, the program requested a framework be developed to evaluate multiple research‐enhancing options in a thorough, disciplined and repeatable manner, and to identify the best option on the basis of cost, benefit, and risk. The resulting framework consists of a systematic methodology and a decision‐support toolset. The framework provides quantifiable and repeatable means for ranking research‐enhancing options for the complex and multiple‐constraint domain of the space research laboratory. This paper describes the development, verification and validation of this framework and provides observations on its operational use.