Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “NASA Process Requirements”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Goals Analysis Procedure Guidelines for Applying the Goals Analysis Process

One of the key elements to successful project management is the establishment of the "right set of requirements", requirements that reflect the true customer needs and are consistent with the strategic goals and objectives of the participating organizations. A viable set of requirements implies that each individual requirement is a necessary element in satisfying the stated goals and that the entire set of requirements, taken as a whole, is sufficient to satisfy the stated goals. Unfortunately, it is the author's experience that during project formulation phases' many of the Systems Engineering customers do not conduct a rigorous analysis of the goals and objectives that drive the system requirements. As a result, the Systems Engineer is often provided with requirements that are vague, incomplete, and internally inconsistent. To complicate matters, most systems development methodologies assume that the customer provides unambiguous, comprehensive and concise requirements. This paper describes the specific steps of a Goals Analysis process applied by Systems Engineers at the NASA Langley Research Center during the formulation of requirements for research projects. The objective of Goals Analysis is to identify and explore all of the influencing factors that ultimately drive the system's requirements.

Motley, Albert E., III↗
NASA NTRS2007

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record↗
NASA NTRS1992

Independent verification and validation for Space Shuttle flight software

The Committee for Review of Oversight Mechanisms for Space Shuttle Software was asked by the National Aeronautics and Space Administration's (NASA) Office of Space Flight to determine the need to continue independent verification and validation (IV&V) for Space Shuttle flight software. The Committee found that the current IV&V process is necessary to maintain NASA's stringent safety and quality requirements for man-rated vehicles. Therefore, the Committee does not support NASA's plan to eliminate funding for the IV&V effort in fiscal year 1993. The Committee believes that the Space Shuttle software development process is not adequate without IV&V and that elimination of IV&V as currently practiced will adversely affect the overall quality and safety of the software, both now and in the future. Furthermore, the Committee was told that no organization within NASA has the expertise or the manpower to replace the current IV&V function in a timely fashion, nor will building this expertise elsewhere necessarily reduce cost. Thus, the Committee does not recommend moving IV&V functions to other organizations within NASA unless the current IV&V is maintained for as long as it takes to build comparable expertise in the replacing organization.

Source record↗
NASA NTRS2013

Challenges of Integrating NASAs Space Communication Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Reinert, Jessica M.↗
NASA NTRS2013

Challenges of Integrating NASA's Space Communications Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Systems Integration↗
NASA NTRS1988

Integrated resource scheduling in a distributed scheduling environment

The Space Station era presents a highly-complex multi-mission planning and scheduling environment exercised over a highly distributed system. In order to automate the scheduling process, customers require a mechanism for communicating their scheduling requirements to NASA. A request language that a remotely-located customer can use to specify his scheduling requirements to a NASA scheduler, thus automating the customer-scheduler interface, is described. This notation, Flexible Envelope-Request Notation (FERN), allows the user to completely specify his scheduling requirements such as resource usage, temporal constraints, and scheduling preferences and options. The FERN also contains mechanisms for representing schedule and resource availability information, which are used in the inter-scheduler inconsistency resolution process. Additionally, a scheduler is described that can accept these requests, process them, generate schedules, and return schedule and resource availability information to the requester. The Request-Oriented Scheduling Engine (ROSE) was designed to function either as an independent scheduler or as a scheduling element in a network of schedulers. When used in a network of schedulers, each ROSE communicates schedule and resource usage information to other schedulers via the FERN notation, enabling inconsistencies to be resolved between schedulers. Individual ROSE schedules are created by viewing the problem as a constraint satisfaction problem with a heuristically guided search strategy.

Zoch, David↗
NASA NTRSDate not supplied

What Is the OPP Approach to the Next Generation of Laboratory Requirements

Planetary Protection Quality Management System NASA’s Office of Planetary Protection uses a quality-based process evaluation approach to verify planetary protection bioburden compliance over a project’s life cycle. The verification strategy shifts from a comparative direct assay approach validating hardware bioburden at a “moment in time,” to one that implements a continual quality assurance demonstration of the analytical process via established data requirements, laboratory operational, and management parameters throughout the mission’s entire assembly process. Laboratory quality-based systems and management strategies are standardized and implemented across government and industry. A standardized laboratory quality system approach increases transparency throughout the project’s life cycle and aligns planetary protection analytical approaches with government and industry practices to support both NASA and commercial endeavors. Strategies include the implementation of a laboratory quality management structure that documents and routinely validates parameters critical to experimental design and data collection, provides data quality assessment parameters, and ultimately validates that the collected data is of sufficient quality and quantity to meet the specified technical goals. Planetary protection can draw on these practices to provide a systematic process-based quality approach to support planetary protection validation and compliance requirements. Quality approaches including data quality objectives, method performance, data acceptance criteria and the associated laboratory quality management system are presented to provide an overview and framework for a planetary protection laboratory quality management system.

Amy Baker↗
NASA NTRS2008

Polymeric Materials for Aerospace Power and Propulsion-NASA Glenn Overview

Use of lightweight materials in aerospace power and propulsion components can lead to significant reductions in vehicle weight and improvements in performance and efficiency. Polymeric materials are well suited for many of these applications, but improvements in processability, durability and performance are required for their successful use in these components. Polymers Research at NASA Glenn is focused on utilizing a combination of traditional polymer science and engineering approaches and nanotechnology to develop new materials with enhanced processability, performance and durability. An overview of these efforts will be presented.

Meador, Michael A.↗
NASA NTRS1990

College education

Space Grant Colleges and Universities must build the space curriculum of the future on the firm basis of deep knowledge of an involvement with the present operating programs of the nation and an on-going and extensive program of leading edge research in the aerospace sciences and engineering, management, law, finance, and the other arts that are integral to our planetary society. The Space Grant College and Fellowship Program must create new academic fields of enquiry, which is a long and difficult process that will require deeper and broader interaction between NASA and academia than has previously existed.

Criswell, David R.↗
NASA NTRS2019

NASA CA Operations Devolution: Status Update

What is Devolution? Devolution is a spreading of CA (Conjunction Assessment) operations responsibilities to mission FOTs (Flight Operations Teams): Permits efficiencies in handling the increased workload caused by Space Fence and large constellations; Missions given more flexibility in choosing specific approach to CA requirements that resonates best with their particular needs; CARA (Conjunction Assessment Risk Analysis) retains Agency oversight through an established NASA Standard - will establish requirements for devolved CA preparations, processing, and operations conduct. Devolution is a PROPOSED paradigm under consideration by SMD (Space Missions Directorate): Number of activities required before Agency-level decision can be rendered; Agency requirements established via approved CA Standard; Operational experience testimony from two separate pilot programs; After these activities complete, decision will be made whether devolution is a feasible option for missions; CARA is recommending devolution to exist as an option for missions.

conjunction↗
NASA NTRS2001

A Stream lined Approach for the Payload Customer in Identifying Payload Design Requirements

NASA payload developers from across various disciplines were asked to identify areas where process changes would simplify their task of developing and flying flight hardware. Responses to this query included a central location for consistent hardware design requirements for middeck payloads. The multidisciplinary team assigned to review the numerous payload interface design documents is assessing the Space Shuttle middeck, the SPACEHAB Inc. locker, as well as the MultiPurpose Logistics Module (MPLM) and EXpedite the PRocessing of Experiments to Space Station (EXPRESS) rack design requirements for the payloads. They are comparing the multiple carriers and platform requirements and developing a matrix which illustrates the individual requirements, and where possible, the envelope that encompasses all of the possibilities. The matrix will be expanded to form an overall envelope that the payload developers will have the option to utilize when designing their payload's hardware. This will optimize the flexibility for payload hardware and ancillary items to be manifested on multiple carriers and platforms with minimal impact to the payload developer.

Miller, Ladonna J.↗
NASA NTRSDate not supplied

Use NASA Earthdata in the Cloud

With the impending arrival of new, high-data-volume Earth observation missions, NASA’s ability to effectively ingest, process, and archive large amounts of data requires the most cost-effective, flexible, and scalable data-management architectures and technologies. To meet these demands, NASA's Earth Science Data Systems (ESDS) Program is implementing a strategic vision to develop and operate multiple components of NASA's Earth Observing System Data and Information System (EOSDIS) in a commercial cloud environment. As more earth observing data is moved into the cloud, NASA EOSDIS wants to share our reasoning for moving data into the commercial cloud, as well as demonstrate how end-users can take advantage of both data in the cloud and cloud-deployed services. This presentation explains the enterprise reasons for moving data into the cloud, specifically the scalability of cloud systems, the flexibility to pivot to the most optimal language/system/architecture, and the reduced redundancy of a common architecture. Then we primarily focus on the user-driven reasons for moving to the cloud. Equal access to high performance computing helps all parties, especially users that don't have access to their own on-premise computing infrastructure. Rapid deployment allows users to spin up their own systems without needing the extensive platform previously required for large scale development. Cost effectiveness allows users a wide breadth of computing options, from super computer ability to small scale development, which can help underserved communities. Finally we link to internal resources that users can utilize to begin their cloud based development journey without having to be an expert in the field.

Nicholas Doty↗
NASA NTRS1996

Technology Directions for the 21st Century

The Office of Space Communications (OSC) is tasked by NASA to conduct a planning process to meet NASA's science mission and other communications and data processing requirements. A set of technology trend studies was undertaken by Science Applications International Corporation (SAIC) for OSC to identify quantitative data that can be used to predict performance of electronic equipment in the future to assist in the planning process. Only commercially available, off-the-shelf technology was included. For each technology area considered, the current state of the technology is discussed, future applications that could benefit from use of the technology are identified, and likely future developments of the technology are described. The impact of each technology area on NASA operations is presented together with a discussion of the feasibility and risk associated with its development. An approximate timeline is given for the next 15 to 25 years to indicate the anticipated evolution of capabilities within each of the technology areas considered. This volume contains four chapters: one each on technology trends for database systems, computer software, neural and fuzzy systems, and artificial intelligence. The principal study results are summarized at the beginning of each chapter.

Crimi, Giles F.↗
NASA NTRS2006

Progress in the Development of Practical Remote Detection of Icing Conditions

The NASA Icing Remote Sensing System (NIRSS) has been under definition and development at NASA Glenn Research Center since 1997. The goal of this development activity is to produce and demonstrate the required sensing and data processing technologies required to accurately remotely detect and measure icing conditions aloft. As part of that effort NASA has teamed with NCAR to develop software to fuse data from multiple instruments into a single detected icing condition product. The multiple instrument approach utilizes a X-band vertical staring radar, a multifrequency microwave, and a lidar ceilometer. The radar data determine cloud boundaries, the radiometer determines the sub-freezing temperature heights and total liquid water content, and the ceilometer refines the lower cloud boundary. Data is post-processed with a LabVIEW program with a resultant supercooled liquid water profile and aircraft hazard depiction. Ground-based, remotely-sensed measurements and in-situ measurements from research aircraft were gathered during the international 2003-2004 Alliance Icing Research Study (AIRS II). Comparisons between the remote sensing system s fused icing product and the aircraft measurements are reviewed here. While there are areas where improvement can be made, the cases examined suggest that the fused sensor remote sensing technique appears to be a valid approach.

Reehorst, Andrew↗
NASA NTRSDate not supplied

NASA’s Plans for the Release of Standards for Additive Manufactured Components

NASA has a critical need for the development of Agency standards for the certification of additively manufactured (AM) components. This is necessary since the current version of NASA standards for manned and noncrewed spaceflight hardware do not contain sufficient detail and the development of documents by the international standards organizations are not mature enough for implementation. AM parts are currently flying or in development for nearly all NASA flight programs. To bridge the gap prior to the release of Agency standards MSFC released two documents, MSFC-STD-3716 and MSFC-SPEC-3717. These documents were written specifically for laser power fusion of metallic powder, but the principles defined were used for tailoring requirements for current NASA manned missions. In 2018 a team of Agency AM experts was assembled and development of standards for the certification of additively manufactured components. These standards are design for use by all NASA programs and a broader spectrum of mature materials and processes. Four documents are being planned; NASA-STD-6030 (add title), NASA-STD-6032 (add title), NASA-STD-6033 (add title) and NASA-HNBK-6034 (add title). Two of these documents, NASA-STD-6030 and NASA-STD-6033, are being finalized for release in late 2020. These standards contain requirements that address part classification, metallurgical process control, material property development, part process control, part inspection and acceptance, equipment process control and vendor process control. This paper will present a summary of the status of each document and provide an overview of the content of NASA-STD-6030.

Richard Russell↗
NASA NTRS1993

Optical information processing at NASA Ames Research Center

The combination of analog optical processors with digital electronic systems offers the potential of tera-OPS computational performance, while often requiring less power and weight relative to all-digital systems. NASA is working to develop and demonstrate optical processing techniques for on-board, real time science and mission applications. Current research areas and applications under investigation include optical matrix processing for space structure vibration control and the analysis of Space Shuttle Main Engine plume spectra, optical correlation-based autonomous vision for robotic vehicles, analog computation for robotic path planning, free-space optical interconnections for information transfer within digital electronic computers, and multiplexed arrays of fiber optic interferometric sensors for acoustic and vibration measurements.

Reid, Max B.↗
NASA NTRS1990

Telescience - Optimizing aerospace science return through geographically distributed operations

The paper examines the objectives and requirements of teleoperations, defined as the means and process for scientists, NASA operations personnel, and astronauts to conduct payload operations as if these were colocated. This process is described in terms of Space Station era platforms. Some of the enabling technologies are discussed, including open architecture workstations, distributed computing, transaction management, expert systems, and high-speed networks. Recent testbedding experiments are surveyed to highlight some of the human factors requirements.

Rasmussen, Daryl N.↗