bluuebunny/crossref_metadata_2025_split huggingface dataset:
THE PLACEMENT OF AN AIR FORCE ENGINEER AT THE CONTRACTOR'S FACILITY
Authors: Vajdos Michael D. 
Published: November 2014

AbstractThis paper presents an example of the concept of placing an Air Force engineer at contractor's facility on a relatively small Air Force program. The reasons to implement the concept are given. The author points out the positive and negative aspects, and makes recommendations for future programs. The practice of placing an Air Force engineer at the contractor's facility was tried on a small program in 1990, when the Air Force signed a contract with CTA INCORPORATED of Englewood, Colorado and mandated that the contractor fast‐track the program. To allay problems that surfaced, to assure close compliance with the contract requirements and receive real time feedback, the Air Force obtained permission from the contractor to have an Air Force software engineer on‐site. This paper addresses the program benefits and negatives of this practice.
Requirements Management Using SLATE
Authors: Nallon John , Goodwin Steven 
Published: November 2014

ABSTRACTAfter 10 years of automating the electrical design process at Texas Instruments, we could design and build a printed wiring board in 30 days, a 6x cycle time improvement. However, each design was still being built 5.75 times. Further analysis disclosed that the problem was the lack of requirements analysis and poorly written (or not written) specifications.Recent systems engineering surveys found that the management and documentation of requirements comprises over 75% of the tasks performed by systems engineering. These findings led to the development of a System Level Automation Tool for Engineers (SLATE) to improve the productivity of systems engineers. SLATE is a multi‐user, multi‐dimensional, concurrent engineering design tool for managing system design from product definition through design, development, manufacturing, deployment, maintenance, and the disposal of a product. This paper focuses on the approach taken to implement Requirements Management in SLATE.
SysEn: An Integrated Approach to Specification, Modeling, Rapid Prototyping, Simulation and Documentation
Authors: Adhikari Sam B. 
Published: November 2014

AbstractSysEn provides an integrated approach to specification, modeling, multimedia based presentation, rapid prototyping, simulation and documentation. It provides complete traceability across the entire development lifecycle. Specification, code, object code, test documentation and user documentation are tightly linked through fine grained object oriented repositories. It provides systems engineers a rapid method of building and testing specifications through actual system development and/or simulation. SysEn accepts descriptive requirements as input and helps users to develop task oriented detailed specification which is transformed to code, executables as well as documentation to support the use of executables. A reusable component library feeds detailed specification and source code generation process. System changes and modifications are done by changing requirements and regenerating code, executables and user documentation. Requirements document and user guide are generated in compliance with various ISO, IEC, IEEE, JIS and DoD standards.
SYSTEMS ENGINEERING APPROACH TO INSTRUCTIONAL SYSTEMS DEVELOPMENT (ISD), MANPOWER, AND PERSONNEL DECISION MAKING
Authors: Flowers Shirlee J. , Gaffney John E. , Kaufman Petrus J. 
Published: November 2014

AbstractThe purpose of this paper is to describe a methodology which uses common elements of DoD systems engineering and ISD in a manner that supports low‐risk, concurrent engineering of training systems.Standard systems engineering techniques can be adapted for early identification of “people” requirements. Near‐concurrent development of the primary system and its training system is possible if traditional concept phase analyses are broadened and reprioritized. Systems engineering analyses can provide “people” data at the system concept level, while ISD is dependent on detailed data that usually is not available in the early phases of system development. Therefore, when ISD alone is applied during acquisition programs, it lags behind design with the result that training systems are late.This paper addresses the role of systems engineering in defining requirements in terms of missions, jobs, and duties in concert with the system concept. Early front‐end analysis provides for the optimization of hardware, software and human interfaces. Requirements allocations can be performed early to define training system trade studies and life cycle cost issues.The key to concurrent engineering of training systems and other support systems is introduction of manpower, personnel and training considerations into the concept development process at the right stage and in the right depth.
SYSTEMS ENGINEERING LOOKS AT AB939, THE CALIFORNIA INTEGRATED WASTE MANAGEMENT ACT OF 1989
Authors: Kayhanian Masoud , Martin Frederick 
Published: November 2014

AbstractIn 1988, Californians produced and disposed of 38 million tons of municipal solid waste(MSW). This equates to 2500 pounds per year per person, more than any other state in the union and more than twice that of most other industrial countries. Because ninety percent of this waste was landfilled and with most landfills closing in the mid 1990s, as well as threatening ground water with contamination, the State Legislature enacted AB939. The goal of this legislation is to “reduce, recycle and reuse to the maximum extent feasible” the municipal waste generated in the State; it requires that 50% of MSW be recycled by the year 2000 rather than to “transform” the waste to energy. We estimate that at least 50% of MSW consists of mixed organic material that is only usable as fuel for energy, consequently local governments may not be able to meet the mandate of AB939. In addition, AB939 improves the regulation of landfills and assigns local governments responsibility for integrated waste management. In a previous paper, one of the authors explored the concept of adopting MIL‐STD‐499B to resource and environmental management; AB939 fits very well into that concept. However, AB939 has serious limitations in defining an engineering process for implementing its functional requirements.In this paper we examine the mission‐goals and top‐level requirements imposed upon local governments (LG) by AB939. Moreover, to minimize the amount of MSW for disposal, increase the longevity of landfills, and maximize the return to the nation's economy, SE analysis may show these functional requirements to have priorities different from those set forth in AB939. We shall outline the Systems Engineering (SE) methodology that LG might follow in developing a solid waste management system for implementing the goals of AB939. We shall illustrate the SE process by examining how anaerobic digestion of solid waste would integrate into a program for managing it and address the overall goals set forth in AB939.
AN ENABLING TOOL FOR THE SYSTEMS ENGINEERING RAPID ASSESSMENT PROCESS
Authors: Tubbs Allan D. 
Published: November 2014

AbstractThe Systems Engineering Rapid Assessment Process is defined here as a quick assessment effort involving only one or two systems engineers. It was analyzed in the AT&T Advanced Technical Systems (ATS) division for improvement opportunities. The methodology used for this study was that set forth in the Process Quality Management and Improvement (PQMI) guidelines. The process was determined to have four readily defined phases. It begins with the Formulation Phase, in which the systems engineer characterizes the problem. Next, an action plan is laid out in the Planning Phase. Then comes the Assessment Phase, in which the work mapped out in the action plan is actually performed. Finally, the last phase is the close‐out phase, which is essentially a documentation effort.It was determined that the best apparent improvement opportunity for this process was to create a set of guidelines, formatted in the form of a single‐page checklist. The checklist was reviewed and tested for effectiveness. As expected, it was found to be an aid to the engineer in both increasing the quality of assessment output and in decreasing the time required for this output. It is also not burdensome to use, as it requires very little up‐front investment of time.
Emerging Applications Technical Committee
Authors: Mintz Richard B. 
Published: November 2014

AbstractAn introduction to the charter, history, and activities of the Emerging Applications Technical Committee (EATC) is given along with a status report on the EATC membership. Near terms activities including meetings during the 1994 Symposium in San Jose are discussed along with long range ideas for the EATC. A sample of a technical product from the EATC's Resources and Environmental Management Working Group is provided.
In Search of a Capability Assessment Model for Systems Engineering: A Reflection on the Past Year's Activities and a Look to the Future
Authors: Widmann E. R. , Andrews B. A. , Pyster A. 
Published: November 2014

AbstractThe Capability Assessment Working Group (CAWG) is one of four working groups that comprise the Measurement Technical Committee of the Technical Board of the National Council On Systems Engineering (NCOSE). This paper presents the efforts of the CAWG over the past year to: (1) define requirements for a model that measures systems engineering capability, (2) search for such a model(s), and (3) develop an Interim Model capable for assessing systems engineering capability with respect to a subset of the defined requirements. The paper presents the charter of the CAWG, a brief review of its activities over the past year, and future planned activities. Key issues decided by the CAWG, and some awaiting resolution, are addressed.
SYSTEMS ENGINEERING TERMINOLOGY ESTABLISHMENT WITHIN THE NCOSE SYSTEMS ENGINEERING PROCESS AND SYSTEMS ARCHITECTURE WORKING GROUPS
Authors: Olson Robert 
Published: November 2014

AbstractFundamental to the efficient and effective communication of complex ideas is a set of terms, the definitions for which are sufficiently detailed to provide the precision required by the ideas to be communicated. In order to efficiently and effectively accomplish the objectives of the NCOSE Systems Engineering Process and Systems Architecture Working Groups, a terminology subgroup has been established to provide definitions that meet the needs of both working groups. This paper provides some background on how we arrived at where we are today, and describes the current process for establishing required definitions within these two NCOSE working groups.
A Process Description for a New Paradigm in Systems Engineering
Authors: Wray Richard B. 
Published: November 2014

AbstractSystem Engineering usually has a key technical responsibility on systems acquisition projects. The activities normally viewed as systems engineering include Mission Requirements Analysis, Functional Analysis, Requirements Allocation, Synthesis, Optimization and Specification. This is insufficient in practice. There is a lot of confusion over the relationship of systems engineering functions to the life cycle of system development effort. The National Council on Systems Engineering's (NCOSE) national Systems Engineering Process Description Working Group (SEPWG) has been chartered to prepare a description of systems engineering to clarify its roles. The SEPWG has determined that a new way of thinking about systems engineering is needed. This new paradigm includes understanding of two levels to systems engineering; considering all systems engineering customers; and learning and applying systems engineering to projects. This SEPWG Chair Report identifies some of the problems facing systems engineering, addresses the other development participants with whom Systems Engineers must work, and identifies the overall activities and processes in each aspect of systems engineering as used throughout the system life cycle. This report establishes a “sense of the SEPWG” baseline for efforts still underway for the NCOSE interest group members supporting the SEPWG.
SYSTEMS ENGINEERING FOR THE DOE SNF PROGRAM
Authors: Beebe Corey L. 
Published: November 2014

AbstractSystems engineering has been formally implemented as a management strategy in the National Spent Nuclear Fuel Program. DOE Headquarters, DOE Operations Offices, contractors at each site that have spent nuclear fuel, and other stakeholders are working together in applying systems engineering to develop Program functions, requirements, schedules, priorities, and solutions for managing spent nuclear fuel. The systems engineering process has successfully unified and integrated high level activities at each of the major sites. Examples of implementing the systems engineering process and the resulting paths forward are presented.
INTEGRATION OF THE IDAHO NATIONAL ENGINEERING LABORATORY ENVIRONMENTAL MANAGEMENT ACTIVITIES USING SYSTEM ENGINEERING
Authors: Murphy James A. 
Published: November 2014

AbstractIntegrating the Environmental Management activities across the Idaho National Engineering Laboratory (INEL) has involved a number of technical experts evaluating the existing system and plans with the facilitation, methodology, and tools of the INEL Systems Engineering organization. The use of the systems engineering methodology in the design and facilitatation the INEL EM integration activities is discussed. Additionally, the lessons learned in applying systems engineering to well‐entrenched organizations with many years of operations is relayed as was found in the INEL experience. The INEL EM Engineered Baseline definition and the process that will be used to mature the baseline at the INEL is discussed.
INTRODUCTION OF SYSTEMS ENGINEERING AND APPROPRIATE TOOLS TO A MASS TRANSIT RAILWAY PROJECT
Authors: Allan Jeff , Burdett Stuart , Neal Philip , Williams John 
Published: November 2014

AbstractThis paper describes the introduction of formal systems engineering including the introduction of a requirements management and modelling tool to a particular mass transit railway renewal project. The paper begins by explaining the nature of railway projects and the need, yet current scarcity, of application of formal systems engineering. It describes the specific project and the events leading up to the introduction of a systems engineering team into a project which would otherwise have not adopted formal systems engineering techniques. These are specifically the development of a code of practice and an initial feasibility study. It also describes the issues that have had to be resolved in this emerging application which include selection of a systems engineering tool, training, architecture and processes.
DESIGN ANALYSIS CYCLE APPLICATION TO THE INTERNATIONAL SPACE STATION DESIGN
Authors: Brown Gary L. 
Published: November 2014

AbstractThe International Space Station (ISS) has much in common with past major programs. However, it does exhibit one fundamental difference, the ultimate configuration is assembled on‐orbit in a series of stages. Each stage must be a viable spacecraft, capable of meeting stage mission requirements and capable of survival until the next assembly stage. The Design Analysis Cycle (DAC) is a process to integrate the ongoing program design/analyses tasks to ensure through analysis, that each stage of the current design of the ISS vehicle can perform the intended mission objectives. The intent of the DACs, is to integrate stage oriented, “horizontal” assessments in support of each program Incremental Design Review (IDR).
PRIVATIZING GOVERNMENT OPERATIONS A SYSTEMS APPROACH
Authors: Duffy Michael A. , Sailor William C. , Schmieman Eric A. , Baker Loyd 
Published: November 2014

AbstractThe Hanford Area is a U.S. Department of Energy (DOE) reservation in Southeastern Washington, where the primary mission for nearly fifty years was production of nuclear weapons materials. It is now the nation's largest superfund site and its sole mission is environmental remediation of the mixed wastes generated during plutonium production. A large fraction of these wastes are stored in 177 underground tanks and are the subject of the DOE's Tank Waste Remediation System (TWRS) Program. Since its inception the TWRS Program has been managed by a Maintenance and Operations (M&O) contractor.The DOE is now considering the privatization of a portion of this program and has recently issued a Request for Proposals (RFP) seeking new, qualified, private vendors. Successful bidders will be expected to build waste processing facilities with their own financial resources and to recover their costs by charging fixed prices for the various products delivered to the DOE. Because the TWRS Program is such a large, complex, and expensive undertaking, the privatization initiative will be conducted in two phases: a small proof‐of‐concept phase, followed by full‐scale production. A primary objective of the proof‐of‐concept phase is to test this new contracting approach by determining the interest of private companies and demonstrating their technical capabilities.The key to a successful demonstration is establishing the right set of requirements to be satisfied by the private vendors. These requirements must be consistent with the existing requirements set developed over the past three years by the M&O contractor. This paper presents the results of a systems engineering effort that was conducted in support of the RFP preparation and had to be coordinated with an ongoing program. Much of the effort was focused on the specification of new proof‐of‐concept requirements that are directly traceable to corresponding requirements in the M&O's RDD‐100® database. A new functions and requirements database was created for this first privatization phase using CORE®, a systems engineering support tool, produced by Vitech Corporation.
IMACCS: A DEMONSTRATION IN REENGINEERING GROUND DATA SYSTEMS DEVELOPMENT
Authors: Bracken M.R. , Hoge S.L. , Pendley R.D. , Rashkin R. , Sary C. , Werking R.D. 
Published: November 2014

AbstractThis paper describes a successfully functioning, commercial, off‐the‐shelf (COTS)‐based ground support system called the Integrated Monitoring, Analysis, and Control COTS System (IMACCS). IMACCS was implemented as a prototype by Goddard Space Flight Center (GSFC), Mission Operations and Data Systems Directorate (MO&DSD) to operate NASA's Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX). IMACCS was conceived specifically to build on previous experience in testbed evaluation of COTS products. The purpose of the IMACCS project was to integrate a typical set of such tools, connect them to live tracking and telemetry data from a real, on‐orbit satellite, and perform shadow mission operations. The objective of the IMACCS project was to assess the completeness, robustness, and performance of a COTS‐based ground system. As a constraint, IMACCS was to be implemented within 90 days of project approval. This paper discusses the challenges that led to the IMACCS project; the processes used for implementing IMACCS; how these processes fit within MO&DSD's reengineered ground systems development processes; and the results obtained by comparing IMACCS' requirements, operations, costs, and implementation process against the currently operating ground system.
SYSTEM ENGINEERING APPLICATION TO LOCAL GOVERNMENTS PART 1: IDENTIFYING THE MISSION
Authors: Nagle Thomas J. 
Published: November 2014

AbstractThis is the first in a series of papers documenting the author's vision for implementation of system engineering principles in the conduct of a municipal government. The author has worked in a strict system engineering environment for over 15 years. This experience has been on a variety of government programs in the aerospace field ranging from missile systems to ground based weapons and communications systems to spacecraft. He has worked with many tools and in support of many different agencies. He has been involved in the application of these principles to commercial ventures. In late 1994, he became city councilmember for a small municipality in Southern California and set out to identify what the mission is for the city government and how system engineering principles could ultimately be utilized to achieve this mission. This is a look at early observation, actions and results.
Leveraging Limited Research and Development (R&D) Resources in the Public Sector
Authors: Senglaub Michael 
Published: November 2014

AbstractMission‐directed public‐sector research facilities are experiencing increasingly severe budget environments while seeing expanding missions and responsibilities. In an effort to identify research leveraging methodologies an information search was conducted in conjunction with some efforts to find the proper links to systems engineering fundamentals. The result is an initial model for use in a pre‐concept/phase‐1 engineering design organization, with a goal of improving the organizations performance.
Specification for “Century Compliance”
Authors: Louton Robert 
Published: November 2014

AbstractAnalysis of the Year 2000 (Y2K) problem is a systems‐engineering job. This analysis considers the business and technical elements of the problem and produces a specification of acceptance criteria which software must meet to be deemed century‐compliant. This paper identifies and discusses four criteria that form the basis of any specification for century compliance. A specification for century compliance may be used both as a standard in Year 2000 program efforts and where applicable in a company's day‐to‐day business.
THE APPLICATION OF RISK MANAGEMENT TO THE NEO THREAT
Authors: Friedman George 
Published: November 2014

AbstractIn the spring of 1995, the author, as Adjunct Professor of Engineering at the University of Southern California, developed a new graduate level course in risk management applied to problems in systems engineering and program management. The class project for this course was the near‐earth‐object (NEO) threat. Risk management has been one of the most recent arrivals to be recognized within systems engineering, but it is usually ad hoc and qualitative. The core of this new course established risk management on the foundation of probabilistic decision theory. For the class project, the students were asked to develop decision networks, probability assessments, and alternative criteria relating to the conduct of a planetary defense program. A good consensus was obtained: all investments for acceleration of NEO detection and characterization as well as preliminary design of mitigation systems were shown to be very cost effective, key risk reduction tests on mitigation technologies were recommended within limits, and the full deployment of actual mitigation systems should be paced by the results of the NEO detection program.
SYSTEMS ENGINEERING ON THE INTERNET HIGHWAY – ROADKILL OR ROAD RUNNER?
Authors: Lee Llewellyn A. , Parker Barnes R. 
Published: November 2014

AbstractThis paper examines the Internet for its worth from the viewpoint of a practicing systems engineer. Are there resources strewn across the Internet for systems engineers to discover? Have the paths to systems engineering gems on the Internet been explored? If systems engineers are not using the Internet, what are they missing? Because the very nature of the Internet makes it an “unsecure” medium of communications, does that mean that information received over the Internet is possibly not authentic?The systems engineer has special needs (not unique needs) and expectations of the Internet. This paper presents a list of the systems engineer's requirements for Internet usage and examines how the Internet satisfies most of the requirements.The examples and Internet sites presented in this paper are not inclusive. The reader is encouraged to explore the Internet, develop strategies to find information and share the findings.