bluuebunny/crossref_metadata_2025_split huggingface dataset:
Cost Effectiveness Enhancement Initiative For The Space Shuttle Contract
Authors: Akhavi Mina , Antony Patrick , Davidoff Larry , Robitaille Richard 
Published: September 2023

AbstractThis paper will describe the partnership agreement with our NASA Customer and the process improvement techniques utilized to reduce the cost of performing integration tasks during a downturn of the business environment. It will cover a period of two years (FY91 & FY92). It will provide insight on the people's attitudes at the beginning of the initiative and where they are today. Lessons learned during this period will also be delineated which could be used to help others in starting up a similar program.A specific case study on establishment of metrics for a Shuttle Integration analysis operation will be presented and will include techniques and tools utilized to facilitate the people performing the task.
Life Cycle Cost Analysis with Two Reliability Models: A Systems Engineering Approach
Authors: Chan Tony , Suzuki John 
Published: September 2023

AbstractAlthough product development specialists typically consider product costs in a specific portion of a project, they often ignore the full costs associated with the entire life cycle, which includes maintenance and disposal. One of the key aspects of systems engineering is an integrated, full life cycle orientation to product development. When one considers the value of a system using a systems engineering approach, one needs to consider both the technical characteristics of the system as well as the system cost. The financial aspect of the system is one of several key constraints in the design phase of the systems engineering process. Life cycle cost (LCC) analysis, used as an evaluation tool, helps identify the preferred design approach.
HIGH‐LEVEL SOFTWARE SYNTHESIS
Authors: Brackett John W. , Pyster Arthur B. 
Published: September 2023

AbstractHigh‐Level Software Synthesis (HLSS) is an advanced model‐based, product‐line‐oriented software development process being developed by the Software Productivity Consortium (Consortium). The HLSS process is based upon thorough requirements‐ and design‐level validation through the use of models that can predict important properties of the software to be built. The HLSS process is designed to enable an organization to produce members of an embedded system product line at reduced cost, with higher quality, and more rapidly than conventional software production methods.
INSIGHT ‐ AN OBJECT‐ORIENTED MODELING TOOL
Authors: Rudmik Andres , Rohde Sharon 
Published: September 2023

AbstractThis paper describes a new approach to system modeling and analysis predicated on the construction and execution of object‐oriented models of systems. Our approach uses constraints to describe a system's response behavior to stimuli, it incorporates a solver to execute the model, and it provides a tailorable user interface that allows one to define the modeling symbology. An advantage of object‐oriented system modeling, execution and analysis is an increased ability to handle complexity.A prototype of this tool has been developed and applied to different system engineering problems. Applications include modeling of a system engineering method, modeling the Viking Lander Guidance and Control Systems for the Descent Phase on Mars, and an executable simulation of a spacecraft landing on the moon.
Requirements: Going From User Needs to Detailed Performance Parameters
Authors: Might Robert J. 
Published: September 2023

AbstractThe requirement development process for a system starts when a user need is first mentioned. Requirement analysis starts when someone tries to interpret this attempted communication. After that the process that leads from user needs to specific performance parameters of an actual system is described by some as “chaotic.” Current methods isolate several user needs at a time, then a few point solutions are studied to determine which one is most cost effective. This paper addresses how this process should be performed for the class of problems where there are many user needs, many possible solutions (i.e. systems), and each solution has some potential for satisfying multiple user needs. The objective is to determine what combination of performance characteristics for each potential system provides the greatest marginal contribution to the entire set of user needs.
DESIGNING REQUIREMENTS FOR VERIFIABILITY
Authors: Gerson Amy C. R. 
Published: September 2023

AbstractThe purpose of this paper is to describe recent requirements verification experiences and offer hindsights on designing requirements for verifiability. With the advent of concurrent engineering and multi‐disciplinary product development teams, hardware designers must “design for manufacturability.” Systems Engineers must “design for verifiability,” keeping in mind the ultimate purpose of requirements and specifications: verifying that the end product exhibits the intended properties. Composite case examples are drawn from various programs in the space systems domain to illustrate the concepts of perceptiveness, observability, verification methods, environmental factors, safety, etc. Epistemological concepts of sufficient proof, validity of evidence, and degree of rigor are invoked in the interest of philosophical consistency, cost savings, and quality improvement. Specific case examples center on tasks such as the following: Verifying that the power subsystem will support vehicle loads for a specified time; verifying that the vehicle will survive in a contingency mode for a specified time, and verifying proper operation, integration, and installation of a backup attitude control subsystem. Tradeoffs are discussed between requirements design and the resulting impacts on analysis and test processes. Techniques are discussed for bounding the verification task, prioritizing effort, ensuring discipline (traceability), and breaking down high‐level requirements into verifiable portions.
APPLYING SYSTEMS ENGINEERING STANDARDS TO EARLY STAGES OF THE SYSTEM LIFE CYCLE
Authors: Uhrig Jerome L. 
Published: September 2023

AbstractThis paper proposes some process refinements of the initial stages of the system life cycle: Pre‐Concept and Concept Exploration and Definition. They are suggested in the interests of improving the clarity and coherence of these necessarily loosely defined activities. Further structuring is offered both between major stages, in the form of a review specifically suited to early conceptual work, and minor reviews within stages to more effectively demark the three major submodes: requirements analysis, functional analysis and allocation, and synthesis. It is suggested that an appropriate, commonly accepted process would be preferable to the ad hoc approaches that are now the usual rule.
System Integration Applications of Information Systems in the Space Station Freedom Program
Authors: Thomas L. Dale , Cohen Brad , Young Judy 
Published: September 2023

ABSTRACTThe development of large scale systems necessarily involves a large number of engineering organizations, each working individually to design separate components which will ultimately be integrated. If these organizations are to work concurrently, routine and methodological communication between the engineering organizations is required. One necessary product of this communication is the timely specification and design of the components' mating interfaces.The Space Station Freedom (S.S. Freedom) program is a multinational venture, with participating agencies including the National Aeronautics and Space Administration (United States), the National Space Development Agency of Japan, the Canadian Space Agency, the European Space Agency, and the Italian Space Agency. To integrate a project of this scale, with such a large number of participants, a very large quantity of interface development is required to allow the design of the S.S. Freedom's components to proceed concurrently around the world. This paper briefly describes the scope of the system integration task in the S.S. Freedom program and discusses the utilization of an electronic information system specifically developed to facilitate the efficient organization and timely completion of interface design activities.
ON MANAGEMENT AND METRICS
Authors: Thomas Henry D. 
Published: September 2023

AbstractThis paper examines the origins of the modern‐day system of business accounting and its logical extension to management metrics as we know them. It will demonstrate that the majority of metrics used in industry today are based on financial reporting requirements. It will address the impact of these same metrics on management decision‐making.The paper proposes a systems approach to metrics that really allows management to gauge progress towards the achievement of customer satisfaction and greater profitability. It demonstrates where to find the language in a customer's requirements that will spell the difference between customer acceptance and customer excitement. It introduces a Customer Satisfaction Matrix ‐ and explains how to build and use one. It will use a Window of Opportunity to show how an asset can really be a liability in disguise. It will demonstrate how to structure a metric so that the managerial behavior a company needs for long‐term customer satisfaction and profitability is the only behavioral choice logically and emotionally supported by the metric.
UTILIZATION OF NOMOGRAMS BY SATELLITE SYSTEMS ENGINEERS
Authors: Galvin Dennis M. 
Published: September 2023

AbstractOne of the more challenging tasks of a satellite systems engineer is to measure the effects of changes in either mission requirements or subsystem capabilities in a timely manner during a programs' early development phase. The nomogram offers a means of relating a very large number of satellite system parameters on a graphical medium, thus providing a valuable tool for the systems engineer. The nomogram provides a faster method of estimating the effects of parameters than might otherwise be obtained using simulations or analytic methods. Nomograms also permit visualization of the effect of a change in one parameter on other parameters defined on the nomogram.This paper presents the development and utilization of nomograms to show the effects of mission planning parameters on an earth resources or surveillance satellite mission and to show the effect of satellite mission requirements on satellite subsystems requirements. Each nomogram is presented on a medium for application as a tool for the satellite systems engineer.
DEVELOPING A SYSTEMS ENGINEERING AUTOMATION STRATEGY
Authors: Vigland Albert R. 
Published: September 2023

AbstractIn response to industry's need to manage systems engineering processes and methods, a market is evolving which is targeted at high‐level system design automation. Many of the tools on the market are extremely appealing — almost seductive — in their ability to captivate executives of large corporations struggling with systems engineering implementation issues. Just as an enterprise–wide homogeneous computer environment is a thing of the past, a “one–size–fits–all” solution to systems engineering automation is not likely to provide a competitive, cost effective solution. This paper describes a simple approach to organizing existing methodologies, analyzing the cost drivers for automation, and developing a strategy for automating the cost–effective segments of methodologies within an organizations systems engineering process.
THE AT&T FSAT RISK MANAGEMENT PROCESS
Authors: Marion Edwin D. 
Published: September 2023

AbstractThe basic concepts that support the AT&T Federal Systems Advanced Technology's (FSAT) standard Risk Management process are discussed, and an overview of the process, currently a DOD Best Manufacturing Practice1 (Department of Defense 1991) is provided.Risk management is an attempt to deal, in a structured and organized way, with technical, cost, and schedule uncertainties in project execution. In this context, risk and risk management are defined, and the basic concepts of aggregate and detailed risk analysis are developed. The standard techniques for analyzing and quantifying risk, including scenario mapping, Monte Carlo analysis, and decision trees are discussed, and an organized and integrated approach to risk management is suggested that can provide useful ways of addressing both known and unknown uncertainties.AT&T FSAT's implementation of this approach, including integrated software tools and a close coupling to the Project Management, Systems Engineering, and Product Realization standard processes is discussed. The standard process consists of three major components identified as Risk Modeling, Decision Analysis, and Event Analysis. These components are combined into an integrated process that can be tailored to meet a wide range of project needs and can be applied on a project over its complete life cycle, from opportunity assessment to contract completion. Some recent experiences and reactions to the Risk Management process are included.
6.1.3 Systems Engineering and Supportability Analysis: Technology Refreshment for COTS‐Intensive Systems
Authors: Verma Dinesh , Plunkett Galen 
Published: September 2023

AbstractThe desire to integrate supportability issues in product and system design has long been articulated within the systems engineering community [Asimow, 1964; Ostrofsky, 1977; Pugh, 1980]. However, there has often been a lag between this intent and its execution. Supportability and serviceability analysis (traditionally, also referred to as ILS in the aerospace industry) is often relegated to a reactionary mode during detailed system design. At least partially, a contributing factor to this reality has been a hazy definition of supportability and serviceability parameters. This inhibits quantitative “dovetailing” of supportability parameters into the design and architecture synthesis activity.The application of a systematic and integrated development approach must contend with the prevailing business realities. These include increased international competition, resource constraints, evolving system requirements and customer expectation, along with an imperative to get the system to market expeditiously. Furthermore, there is an increasing emphasis on assessing systems and products from a total ownership cost perspective. This mandates explicit inclusion of supportability and serviceability issues into system design. The requirement becomes even more urgent with the emphasis on commercial‐off‐the‐shelf system elements (COTS) in the development of complex, distributed, and multi‐functional systems. This emphasis on COTS technologies and elements has already resulted in significant, relatively immediate, reduction in system development and production costs, as reflected in Figure 1.These benefits and cost reductions notwithstanding, an emphasis on utilizing COTS system elements results in unique challenges from a systems and supportability engineering standpoint. Proactive refreshment of COTS system elements becomes a key component within the overall system supportability and serviceability strategy. Furthermore, any technology refreshment strategy must be tailored to account for the system operational concept, its availability and accessibility, the business strategy, and the system maintenance concept. This is necessary if reductions in development and production costs are to be extended into an overall reduction in system ownership costs.
8.1.1 Systems Engineering and the Legal Profession – Revisited
Authors: Mackey William F. 
Published: September 2023

AbstractThis paper explores some of the similarities of the approaches taken by attorneys to a complex litigation case and those taken by engineers to a complex system development problem. The system development life cycle used in systems engineering has a direct corollary in the process of developing a legal case. Furthermore, the identification of technical, management, and legal risks; mitigation of those risks; and allocation of responsibility for them are of common interest to attorneys and engineering managers. This paper explores how attorneys can best assist engineers in the development process and how engineers can begin to address the problems of the litigation process.Selected topics concerned with the invention and patent process, the systems development life cycle, and the criminal justice system are also examined in this paper. These topics are evaluated to determine some of the ways the systems engineer and the attorney can improve the people, the process, and the tools used in these two professions. The thesis is that many of the problems to come in the 21st century can be solved by the collaboration of systems engineers and attorneys.
7.2.1 A Data Structure Approach to Systems Engineering
Authors: Battersby D. J. 
Published: September 2023

ABSTRACTA fundamental aspect concerning the implementation of an efficient systems engineering process is the management and control of the data arising from the systems engineering process itself. This paper concentrates on defining the overall coordination of the disparate processes needed to define information flows within an extended organisation.The problems of data control with respect to current data configurations are addressed and a concept for the future engineering environment developed. Discussion is presented in terms of the configuration management requirements of an organisation with semi‐integrated, large‐scale software solutions implemented across its business, design, development and manufacturing operations. A data structure concept is developed by matching the requirements of the organisation to the trends seen in the wider business environment.In this context the systems engineering process is seen to be that by which a number of related databases evolve into a structure fitting the practical objectives of a project. The potential difficulties in achieving this are discussed in Section 2. One result that emerges from this view of systems engineering is the importance of collaboration in developing compatible data structures between organisations throughout the supply chain. The potential benefits arising from collaborative working and the associated control measures are discussed.
2.3.1 Examining the Necessity and Benefits of Systems Engineering in the Trenches
Authors: Chapin Gregory G. 
Published: September 2023

AbstractThis paper examines the necessity and benefits of systems engineering in the trenches1. Planner, orchestrator, negotiator, relationship builder, and communicator are key roles for a systems engineer to take in the trenches. The systems engineering approaches used and roles taken to provide technical and business process engineering solutions required to implement collaboration2 that operators used successfully to coordinate and approve fixed targets during the Operation Allied Force air campaign are documented. System objectives were: modify the existing process, leveraging collaboration to improve the effectiveness of information processes; improve product quality; and benefit federated efforts by geographically separated partners. This systems engineering effort took place at the United States European Command (USEUCOM) from February 1998 to June 1999 and continues as of this publication. USEUCOM targets community representatives estimate that using collaboration decreased target approval time from 2–4 days to 2–3 hours. Participants indicated collaboration improved process efficiencies, product quality, and synchronization. The success increased interest in and expansion of collaboration within the intelligence and operations communities, including expansion to the North Atlantic Treaty Organization (NATO). Clearly, the results and impact on mission effectiveness indicate systems engineering in the trenches is both necessary and beneficial.
6.3.3 Commercial System Development Models
Authors: Cathcart Tim , Grady Jeffrey O. , Jain Ravi , Surber Dan 
Published: September 2023

AbstractThe authors believe that system engineers commonly fail to include the full sweep of program possibilities in their view. Their views do not always encompass the full programmatic scope of marketing, system development, and programmatic life cycle issues. As a result they are not able to contribute to their full capacity in the evolution of maximally effective strategies for their enterprise. This paper does two things of value to this engineer so constrained: (1) attempts to expand the readers model of the development environment to the ultimate and (2) offers, in the process, a general model that includes within it several commercial models as well as the fairly traditional aerospace/defense development model. The authors maintain that essentially the same system engineering process will be effective within any of these particular applications of the general model, though the practitioner will have to make choices among alternative techniques.
1.4.2 Global System Architecture Optimization: Quantifying System Complexity
Authors: Carson Ronald S. 
Published: September 2023

AbstractMathematical optimization techniques are applied to the problem of selecting an optimized system architecture. Using complexity criteria we seek the allocation of functions which globally minimizes coupling and fan‐out and maximizes cohesion. The technique requires detailed functional analysis at the next lower level of indenture prior to completing the architecture at the current level. This aspect raises issues regarding the decomposition process, since the “answer” for the prior level is not completed until the functional analysis is at least begun at the next lower level. It is found that a globally optimum architecture probably cannot be defined based solely on the analysis and allocation of functions. However, the attempt to quantify complexity can yield useful data for analyzing architecture alternatives.
5.4.4 An Integrated Information Representation Schema for Complex Human Centric Systems
Authors: Crisp Harry E. , Hoang NgocDung T. , Nguyen Cuong M. , Karangelen Nicholas E. , Britton David 
Published: September 2023

AbstractThis paper will introduce the development of an information representation schema that can be used to support the development of complex human centric systems. Technology that was adopted to support schema evolution to accommodate new methods and tools or schema tailoring for the need of a specific program will also be addressed.
7.4.3 Learning and improvement in Product Innovation Processes: Enabling behaviors
Authors: Gieskes José F.B. , Langenberg Ilse W.H.A. 
Published: September 2023

ABSTRACTThis paper describes Product Innovation as a continuous and cross‐functional process involving all stages of the product life cycle. This approach gives way to study knowledge transfer and learning in companies from a continuous improvement viewpoint. Based on a model developed in CIMA, a European ESPRIT project, the way in which a company shares and transfers knowledge and learning experiences in its product innovation process are assessed. The results can be used to give focus and direction to improvement actions (such as systems engineering and software development improvement plans).The model describes learning and knowledge transfer within product innovation processes in terms of a number of interrelated variables: (improvement) performances, behaviors and levers to stimulate improvement, contingencies and learning / innovation capabilities. At the Research & Development Department of SIGNAAL the model was used to assess its current practices with regard to learning and improvement in product innovation. The results validate efforts on current and past improvement actions and provide additional insight into the past, current and future situation. Furthermore, the recommendations provide guidelines on how to continue with improvement.