bluuebunny/crossref_metadata_2025_split huggingface dataset:
Application of Continuous Improvement Methods to Systems Engineering Tasks: A Case Study
Authors: Davis Juliet G. 
Published: September 2023

AbstractContinuous Process Improvement as an organizational culture is recognized in the 1990's as a key to success in a competitive industry. Application of formal Continuous Improvement methodology on long established tasks presents significant challenges for both staff and management at Rockwell International Space Systems Division. This paper shares the experiences of one Systems Engineering project function in its attempt to incorporate structured Ci practices into the performance of contract tasks. Process decomposition, development and use of product metrics, and the implementation of improvements within various processes are described. Successes, failures, and lessons learned from the experiences are summarized as a guide for future endeavors.
RISK ASSESSMENT AND MITIGATION PLANNING EARLY IN THE DEVELOPMENT LIFE CYCLE
Authors: Booth Stuart 
Published: September 2023

AbstractThis paper presents a risk management process and how it will serve as a basis for test and analysis planning early in the development life cycle. To strengthen this process, integrated databases are available to provide mapping between the system design data and the derived risk metrics that test engineers can use to develop their test and analysis plans. As the development life cycle progresses and matures, the original risk forecasting can be updated providing a real‐time assessment of the design.
Can MIL‐STD‐499B Be Adapted for Resource Management and Saving the Environment?
Authors: Martin Frederick , Daetz Douglas 
Published: September 2023

AbstractManagement of resources and the environment is increasingly prominent in the national and global debates on policy. In the U.S. resources and the environment involve a broad range of national policy issues with complex tradeoffs: forest management to maximize yield and maintain biodiversity; alternative fuels for power plants that must meet the requirements for environmental protection, pollution control, performance and community acceptance; allocation of water, a resource in short supply in the southwest. At the local government level, there are local issues such as: locating a new municipal golf course in a county boasting a unique combination of natural environment, agriculture, sophisticated suburban population and a thriving commerce; designing and implementing local welfare assistance programs in a climate of opposition to new taxes. On a global scale, the World Bank announced that all future projects funded by it will be fully examined for their impact on the environment.In the political arena almost none of these issues are heading towards a rational solution, and for most of them there is only a vague definition of the problem.These issues are a system engineer's nightmare (or challenge)! Why? Unlike the traditional Department of Defense programs with well specified systems, the issues of resources and the environment touch many subsystems in a large, multivariable environment. Many of the variables, e.g., those associated with the weather, national economy, business climate, and international political situation are largely or completely beyond the control or influence of the planners, architects, and engineers. The professional must carry out the task of building a successful project in an environment of extreme uncertainty and limited control.In this paper we examine the features of MIL‐STD‐499B to see how they could be applied to managing resources and the environment for a project that is a subsystem embedded in a very uncertain environment. We shall look at the process of identifying the problem to be solved and establishing the interfaces of the subsystem to the larger world systems. We also consider how to deal with the life‐cycle issues. For example, can one define the life‐cycle process for a golf course?Finally, we shall pose the following dilemma. Resource management as practiced by the former Soviet Union and its satellites has proven to be a failure. Is system engineering for resource and environmental management a paradox or a panacea in a democratic, free‐market society?
A CONCURRENT GOVERNMENT/CONTRACTOR APPROACH FOR DEVELOPING DESIGN CONSTRAINTS
Authors: Shimizu Choichi , Goerke Leah 
Published: September 2023

AbstractSpecifications which define the requirements of a system, sub system, or end items consist of both performance requirements and design constraints. Performance requirements state what a system or item must do and how well it must do it. Design constraints state boundary conditions within which the system or item must perform (i.e., environments, reliability, physical characteristics). Design constraints typically form approximately 80% of the requirements in a specification.Early definition and proper allocation of both the performance requirements and design constraints are essential to the successful development of the end item. At the Ballistic Missile Organization, the System Requirements Analysis (SRA) process has been used to synthesize system design and develop specifications from design constraints and performance requirements. This paper concentrates on the SRA process peculiar to design constraints. A team approach was used with both government and contractor technical experts. The entire process will be discussed from the initial identification of design constraints to the incorporation of these constraints into the specifications as authenticated requirements. This process is consistent with the latest system engineering standards being implemented.
THE THREE‐STEP PROCESS FOR MILESTONE AND REVIEW MANAGEMENT
Authors: Posner Stacy A. 
Published: September 2023

AbstractThe prevailing competitive environment has forced most companies to monitor their resources more stringently than ever before to ensure their optimal use. Consequently, program checkpoints and major milestones have gained greater attention from project managers, as well as corporate managers. This paper details the process activities necessary to successfully meet and pass through these milestones. Even though this process was developed specifically for MIL‐STD type reviews, the three‐step approach, P‐E‐P (Pre‐Event, Event, Post‐Event), can be implemented for any milestone or, in general, for any meeting.Currently, Systems Engineering Management is evolving from a calendar‐driven process to an event‐driven process. The prime benefit of this three‐step approach embraces this trend by ensuring steady forward progress of a project/program regardless of size or the number of milestones. It also ensures that all work being done supports the project's mission and is directly traceable to its requirements and objectives. The three‐step process will identify inconsistencies, mistakes, or ambiguities as early as possible. Early error identification is paramount to reducing cost, since errors are more costly to correct the later they are discovered in the product life cycle. Thus, following this three‐step process allows for better response to change, ensures steady progress toward each milestone and minimizes overall cost through disciplined and structured planning and execution.
THE NEED FOR AUTOMATED VERIFICATION TOOLS FOR THE SYSTEMS ENGINEER
Authors: Swift Douglas Keith 
Published: September 2023

AbstractRequirements Verification is an important aspect of Systems Engineering that suffers from a lack of practical tools specifically tailored to encompass the entire verification process. The need for automation is great, specifically for tools able to interface with relational databases. Most of the current Systems Engineering tool development is geared towards program synthesis and design, with less attention given to integration and verification. This paper examines the needs of Verification Engineers with emphasis on developing a computer based tool for automating and managing the verification process. A typical verification flow is outlined, the goals and benefits that could be derived from automation are reviewed, and then a hypothetical Verification Engineering Management System (VEMS) is described.
ORGANIZATIONAL CHALLENGES IN INTEGRATED PRODUCT TEAM IMPLEMENTATION
Authors: Cox James D. 
Published: September 2023

AbstractThis paper presents a brief case study of the obstacles encountered and lessons learned as a result of the implementation of the concurrent engineering process during the Engineering and Manufacturing Development (EMD) phase of the F‐22 program. The process is on‐going; the organizational structure and implementation procedures continue to evolve as the program matures. Results to date have been highly encouraging. Lockheed Aeronautical Systems Company is developing plans to implement the process on all of its existing and future defense programs.
Distributed Design of Computer Based Systems: Methodology
Authors: Oliver David W. 
Published: September 2023

AbstractThe distributed design of computer based systems requires a methodology that supports both the modeling of the distributed system and the ability to assess the impact of requirements and engineering change while the system is at any stage of development. Model Based Systems Engineering, MBSE, provides an approach to these twined problems with the advantages of tailorability to application, culture, notations, and tools. It is critical that traceability linkages be constructed in the normal course of engineering development and that they be adequate for an analysis of the impact of change.
TOWARD A USEFUL BEST COMMERCIAL PRACTICE
Authors: Weaver Charles L. 
Published: September 2023

ABSTRACTThis paper presents the sequence of events and activities which have occurred as a major defense contractor began the migration to the commercial marketplace. This changeover has been focused on the need to modify development processes to continue to use the best parts of the discipline imposed by Military Standards (MIL‐STDs), yet streamline them to avoid cumbersome and unnecessary tasks. While the challenge to define an easy to use Best Commercial Practice has been more difficult and time consuming than originally anticipated, the results to date have been encouraging.
SE APPLICATIONS IN TRANSPORTATION PLANNING
Authors: Dolton Theodore A. , Hoy John P. , Cutler William H. 
Published: September 2023

AbstractSystems engineering processes are designed to address the functions, elements and issues found in many complex systems, including those outside traditional aerospace industry programs. In this paper these processes are applied to transportation planning for a region ‐ the San Francisco Bay Area.This paper examines the application of the Systems Engineering process, as established in the MIL‐STD‐499B, to this civil system. It considers the unique problems and differences such a civil system imposes on the 499B process. These are seen to be identifying the diffuse customer, which includes the various government agencies involved in the system as well as the public; identifying the requirements and functions of such a complex existing system; characterizing this system; and establishing ways to incorporate new technologies. Representative requirements and functional analysis are presented.
MISCONCEPTIONS CONCERNING THE VALUE OF SYSTEMS ENGINEERS
Authors: Swift Douglas Keith 
Published: September 2023

AbstractIn the community of professional engineers, the Systems Engineer is often perceived as an inferior engineer. Misconceptions are especially prevalent among technical design engineers for whom up‐front Systems Engineering should be considered absolutely essential. The Systems Engineer often works in an environment where his engineering peers, and sometimes even management, considers his contribution to be subordinate, of second‐class value, and at times, a nuisance. This paper examines this critical problem from the perspective of an aerospace engineer who spent five years working as a flight controls design engineer (where Systems Engineering was treated with considerable bias), and men transferred into Systems Engineering and has since been working on the opposite side of the fence. An exploration into the causes of the phenomena is detailed in the paper, with special emphasis on the factors perpetuating these misconceptions. A set of practical recommendations (some applicable for working Systems Engineers and some applicable for Managers) is then presented for use in mitigating and eventually dissolving these non‐productive barriers.
Systems Engineering at the SSCL, A Case Study
Authors: Matz John E. 
Published: September 2023

AbstractSystems Engineering (SE) as “defined” by DoD and NCOSE is compared to SE as “redefined” by the SSCL. How and why they differ are discussed. How a practical and pragmatic Systems Engineering program is organized and implemented is outlined with the rationale for the approach chosen. The progress to date, and the anticipated future of Systems Engineering at the SSCL is described.
5.1.1 Modular Vehicle Architectures: A Systems Approach
Authors: Rushton Gary J. , Zakarian Armen 
Published: September 2023

ABSTRACTModular systems provide the ability to achieve product variety through the combination and standardization of components. In this paper, a methodology that combines the Hatley/Pirbhai system model, integration analysis, and optimization techniques for development of modular electrical/ electronic vehicle systems is presented. The approach optimizes integration and interactions of the electrical/ electronic system elements and creates functional and physical modules for the vehicle. The paper illustrates importance of system modeling in developement of modular products. Discussion on how to make the system modeling more attractive to the industry is also presented.
5.1.2 Chances for Systems Engineering in Road Transport and Traffic Telematics
Authors: Hadderingh J. N. 
Published: September 2023

AbstractThis paper highlights some of the possibilities for applying Systems Engineering in the field of Road Transport and Traffic Telematics (RTTT). Although large and often complicated systems are or will be applied in this field, they are often specified, developed, designed and commissioned without employing Systems Engineering (SE). This has resulted in long and cumbersome procurement processes and sub‐optimal solutions. Even more severe problems may occur with the need for further integration of these often stand alone systems. Applying SE may be a way to solve some of these problems. But it will require the use of this methodology in a field that is not (yet?) ready for it. This paper gives examples of some RTTT systems, shows what SE could do for them and gives a few suggestions for achieving these benefits.
5.1.3 Traceability in A Unified Systems Engineering Framework for A High‐Speed Railway System
Authors: Park Young Won , Song Hae Sang , Chung Heung Chae 
Published: September 2023

AbstractThis paper presents results from a computer‐aided systems engineering application to a high‐speed railway system technology development project, called KHST(Korea High Speed Train). RDD‐100 version of ALC Inc. was used in this work. The framework adopted in the study takes a unified approach to the system design and the process management associated with it, thereby coherent and full traceability between them is maintained. Conventional system engineering process supported by the tool is adopted in the KHST system design; however, some modification is inevitable because of a late introduction of the tool on the project. On the other hand, the same tool is also used to the systems engineering management to get full traceability between system design data and engineering management data. It is greatly helpful in managing many sub‐contractors in the sense that the traceability can help identify the sub‐project responsibility as well as the objectives of the project in coordination with interface requirements. We conclude with the advantage and limits of our unified approach.
5.1.4 Information modelling and systems re‐engineering—an efficient approach to assessing complex current Norwegian natural gas transport operations
Authors: Statoil Hans J. Dahl 
Published: September 2023

AbstractThis paper presents the use of information models as tools for systematically assessing existing Norwegian natural gas transport operations. The models, integral parts of a systems re‐engineering process to analyze the entire transport operation, consist of a requirement traceability model, a system architecture model, a behavior model, and a context model. These models not only consistently define existing operations, but also verify how well the operations meet effectiveness measures that have been identified for the operations.Systems re‐engineering and the models derived from it are shown here to reduce the asymmetry in information that is typically present in this industry between principals and their agents (e.g., authorities vs. system owners, system owners vs. system operators, and shippers vs. shippers' dispatching representatives). Further, information modelling of an existing system is shown here to differ from the more traditional application of information modelling: to bring a new system into being.Models provide a scientific framework for evaluating how a changing business environment impacts existing operations. New legislative requirements and economic measures can be tested with models, which also allow new operational services and business opportunities to be identified and evaluated prior to implementation in actual operations.
7.1.2 Abatement Of Nonpoint Source Pollution: A Systems Engineering Model
Authors: Ghahramani Bahador , Elmaimani Bassam , Pope Tito 
Published: September 2023

ABSTRACTNonpoint source pollution prevention management, primarily consisting of education and regulatory efforts, has met little success to date. Indeed, nonpoint pollution is getting worse, not better, and the Environmental Protection Agency rates it as the leading cause of water quality problems. We must deal with the problems through a systems approach to achieve workable, feasible solutions. Unlike point source input, where the levels, quantities, and consistency of loading are known, nonpoint source pollution must be modeled as an environmentally open system that is constantly changing. Successful nonpoint pollution management requires a systems approach for applying general land management practices to specific unique watersheds focusing on identifying the specific objectives, increasing participation of the affected people in the development process, and applying continuous refinements and improvements once the watershed's management system is implemented. This paper proposes a more holistic approach that will result in robust methods for modeling, implementing, and assessing the control and abatement of nonpoint source pollution.
3.2.3 The Use of an Information Model to Describe the SIRTF Spacecraft
Authors: Harrison Jeffrey A. 
Published: September 2023

ABSTRACTA space system information model (SSIM) was developed to guide the identification of the contents for a document which describes the spacecraft system of the NASA/JPL Space InfraRed Telescope Facility (SIRTF) program. The model was adapted from a general model presented by Dr. David Oliver in his tutorial, Engineering Complex Systems with Models and Objects. The contents of the description document are summarized. Additional benefits from using the SSIM for this and other space systems are identified. A range of further applications which can evolve from the SSIM are also discussed.
3.2.4 A Toolset for modelbased AOCS‐Design
Authors: Hoecherl F. , Wilke M. , Quirmbach O. , Surauer M. , Igenbergs E. 
Published: September 2023

AbstractDue to increasing commercialisation in satellite business modern companies have to create proposals quicker and cheaper than ever before. To cope with those demands a model based design approach is currently implemented at the satellite division of DaimlerChrysler Aerospace.The attitude and orbit control system (AOCS) is one of the key subsystems within a satellite, as it's heavily interfacing to all other subsystems.A tool was developed which supports the AOCS‐designer in selecting suitable COTS‐components based on functional requirements. For each functional requirement (product‐function) a set of reference solutions is identified. Based on the designers selection of those reference solutions, a pre‐selection of suitable COTS‐components is being filtered from a component database.After the designer has selected the final set of components, the tool provides a compliancy check to the initial requirements.
4.2.1 Emergence: A Challenge for the Systematic
Authors: McConnell G. R. 
Published: September 2023

AbstractThe word emergence is being used with increasing frequency. Emergent properties are recognised as a fundamental distinguisher of systems, but what exactly are these emergent properties?This paper examines what these terms mean and why these concepts are not just relevant, but extremely important, to the systems engineering community. It represents an introduction for INCOSE to research which is being carried out in this area. It is therefore a ‘work in progress’ report which will hopefully be followed up at future conferences.The aim of the research is to determine ways in which emergence could be better modelled so that it is less of a surprise when it occurs. Perhaps most important, from the viewpoint of the systems engineer, is to predict emergence which has a negative impact on the functioning of the system. It is these unpleasant surprises, often the cause of major problems, which must be addressed.
4.2.4 Guiding Principles for Next Generation Computer‐Aided Systems Engineering Tools
Authors: Sampson Mark E. 
Published: September 2023

AbstractThe Standish Group recently made major waves when it reported a disturbing 50%+ failure rate among software development projects. It places the blame squarely on a number of factors including; failure to understand and deliver customer requirements to design personnel, lack of real time decision support in concert with requirements, as well as delivery mechanism to feed requirements to downstream development tools–all of which falls in CAD/CAE poor purview of systems architects. This was brought closer to home at the 1999 INCOSE International Symposium, when Gerard Le Lann in his “Reality Check” paper threw the focus of blame from software to systems. “like blaming the transmission for engine problems”. This paper attempts to define some high level guiding principles for tools needed to support “systems thinking” and describes the features of these next‐generation systems development CAD/CAE environments needed to counter these alarming trends.
7.2.2 Selection of a Requirement Management Tool for a Semi‐Custom Design Company
Authors: Langston Dale Glyn , Hansen Mary Lynne 
Published: September 2023

AbstractThe purpose of this paper is to define how a requirements management tool might fit into a semi‐custom design company. The paper identifies why this selection is more complex for a semi‐custom design company than either a project‐based company or a pure product‐based company. The paper finally identifies a minimum set of requirements that must be satisfied by the requirements management tool.