Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “specifications standards”

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 235 records · Page 13

NASA'S Standard Measures During Bed Rest: Adaptations in the Cardiovascular System

Bed rest is a well-accepted analog of space flight that has been used extensively to investigate physiological adaptations in a larger number of subjects in a shorter amount of time than can be studied with space flight and without the confounding effects associated with normal mission operations. However, comparison across studies of different bed rest durations, between sexes, and between various countermeasure protocols have been hampered by dissimilarities in bed rest conditions, measurement protocols, and testing schedules. To address these concerns, NASA instituted standard bed rest conditions and standard measures for all physiological disciplines participating in studies conducted at the Flight Analogs Research Unit (FARU) at the University of Texas-Medical Branch. Investigators for individual studies employed their own targeted study protocols to address specific hypothesis-driven questions, but standard measures tests were conducted within these studies on a non-interference basis to maximize data availability while reducing the need to implement multiple bed rest studies to understand the effects of a specific countermeasure. When possible, bed rest standard measures protocols were similar to tests nominally used for medically-required measures or research protocols conducted before and after Space Shuttle and International Space Station missions. Specifically, bed rest standard measures for the cardiovascular system implemented before, during, and after bed rest at the FARU included plasma volume (carbon monoxide rebreathing), cardiac mass and function (2D, 3D and Doppler echocardiography), and orthostatic tolerance testing (15- or 30-minutes of 80 degree head-up tilt). Results to-date indicate that when countermeasures are not employed, plasma volume decreases and the incidence of presyncope during head-up tilt is more frequent even after short-duration bed rest while reductions in cardiac function and mass are progressive as bed rest duration increases. Additionally, while plasma volume loss can be corrected and cardiac mass can be prevented with properly applied countermeasures, orthostatic tolerance is more difficult to protect when supine exercise is the only countermeasure. Similar results have been observed after space flight. Plasma volume, cardiac chamber volume, and orthostatic tolerance recover relatively quickly with resumption of ambulation and normal activity levels after bed rest but restoration of cardiac mass is prolonged.

Lee, Stuart M. C.↗

The COBE normalization for standard cold dark matter

The Cosmic Background Explorer Satellite (COBE) detection of microwave anisotropies provides the best way of fixing the amplitude of cosmological fluctuations on the largest scales. This normalization is usually given for an n = 1 spectrum, including only the anisotropy caused by the Sachs-Wolfe effect. This is certainly not a good approximation for a model containing any reasonable amount of baryonic matter. In fact, even tilted Sachs-Wolfe spectra are not a good fit to models like cold dark matter (CDM). Here, we normalize standard CDM (sCDM) to the two-year COBE data and quote the best amplitude in terms of the conventionally used measures of power. We also give normalizations for some specific variants of this standard model, and we indicate how the normalization depends on the assumed values on n, Omega(sub B) and H(sub 0). For sCDM we find the mean value of Q = 19.9 +/- 1.5 micro-K, corresponding to sigma(sub 8) = 1.34 +/- 0.10, with the normalization at large scales being B = (8.16 +/- 1.04) x 10(exp 5)(Mpc/h)(exp 4), and other numbers given in the table. The measured rms temperature fluctuation smoothed on 10 deg is a little low relative to this normalization. This is mainly due to the low quadrupole in the data: when the quadrupole is removed, the measured value of sigma(10 deg) is quite consistent with the best-fitting the mean value of Q. The use of the mean value of Q should be preferred over sigma(10 deg), when its value can be determined for a particular theory, since it makes full use of the data.

Bunn, Emory F.↗

Progress of the NASA/USGS Lunar Regolith Simulant Project

Beginning in 2004 personnel at MSFC began serious efforts to develop a new generation of lunar simulants. The first two products were a replication of the previous JSC-1 simulant under a contract to Orbitec and a major workshop in 2005 on future simulant development. Beginning in 2006 the project refocused its efforts and approached simulant development in a new and more comprehensive manner, examining new approaches in simulant development and ways to more accurately compare simulants to actual lunar materials. This led to a multi-year effort with five major tasks running in parallel. The five tasks are Requirements, Lunar Analysis, Process Development, Feed Stocks, and Standards. Major progress has been made in all five areas. A substantial draft of a formal requirements document now exists and has been largely stable since 2007. It does evolve as specific details of the standards and Lunar Analysis efforts proceed. Lunar Analysis has turned out to be vastly more difficult than anticipated. After great effort to mine existing published and gray literature, the team has realized the necessity of making new measurements of the Apollo samples, an effort that is currently in progress. Process development is substantially ahead of expectations in 2006. It is now practical to synthesize glasses of appropriate composition and purity. It is also possible to make agglutinate particles in significant quantities. A series of minerals commonly found on the Moon has been synthesized. Separation of mineral constituents from starting rock material is also proceeding. Customized grinding and mixing processes have been developed and tested are now being documented. Identification and development of appropriate feedstocks has been both easier and more difficult than anticipated. The Stillwater Mining Company, operating in the Stillwater layered mafic intrusive complex of Montana, has been an amazing resource for the project, but finding adequate sources for some of the components remains a difficult problem. For example the ratio of clino- to ortho-pyroxenes in the Stillwater is not an exact match for lunar materials. One of the sources being examined as an alternative pyroxene source is the Bushveld Complex in South Africa. Standards have been a major success for the project. The Figure of Merit algorithms have been created, tested, and are being considered for an ISO standard. Agreement has been reached in the community about how to make many of the critical measurements. There remains much work to do: (1) driving down the cost of simulants remains a major obstacle; (2) documentation and cost data analysis have not kept up with progress; (3) educating users in the complexity of the lunar regolith and the use of simulants remains a major task. In summary the project has made enormous progress and is successfully placing simulant development and use on a rigorous, scientifically defensible, engineering basis.

Rickman, Doug↗

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗

NASA Software Documentation Standard

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗

DSS-13 - Using an OSI process control standard for monitor and control

The flexibility and robustness of a monitor and control (M&C) system are a direct result of the underlying inter-processor communications architecture. A new architecture for M&C at the Deep Space Communications Complexes has been developed based on the manufacturing message specification (MMS) process control standard of the open system interconnection (OSI) suite of protocols. This architecture has been tested both in a laboratory environment and under operational conditions at the Deep Space Network experimental station (DSS-13). The DSS-13 experience in the application of OSI standards to support M&C has been extremely successful. MMS meets the functional needs of the station and provides a level of flexibility and responsiveness previously unknown in that environment. The architecture is robust enough to meet current operational needs and flexible enough to provide a migration path for new subsystems. This paper describes the architecture of the DSS-13 M&C system, discuss how MMS was used and the requirements this imposed on other parts of the system, and provides results from systems and operational testing at DSS-13.

Heuser, W. R.↗

DSS-13: Using an OSI Process Control Standard for Monitor & Control

The flexibility and robustness of a monitor and control (M&C) system are a direct result of the underlying inter-processor communications architecture. A new architecture for M&C at the Deep Space Communications Complexes (DSCCs) has been developed based on the Manufacturing Message Specification (MMS) process control standard that is part of the Open System Interconnection (OSI) suite of protocols. This architecture has been tested both in a laboratory environment and under operational conditions at the Deep Space Network (DSN) experimental station (DSS-13)...

Stockett, Michael H.↗

DSS-13: Using an OSI Process Control Standard for Monitor and Control

The flexibility and robustness of a monitor and control (M&C) system are a direct result of the underlying inter-processor communications architecture. A new architecture for M&C at the Deep Space Communications Complexes (DSCCs) has been developed based on the Manufacturing Message Specification (MMS) process control standard of the Open System Interconnection (OSI) suite of protocols. This architecture has been tested both in a laboratory environment and under operational conditions at the Deep Space Network (DSN) experimental station (DSS-13). The DSS-13 experience in the application of OSI standards to support M&C has been extremely successful. MMS meets the functional needs of the station and provides a level of flexibility and responsiveness previously unknown in that environment.

Stockett, Michael H.↗

Past, Present and Future Trends for NASA's EEE Parts Program

The foundation of NASA's Electrical, Electronic and Electromechanical (EEE) parts program is standardization. Standardization helps to reduce the number of unknown variables present as a project or program progresses; unknown variables equate to unknown risk. NASA spacecraft are usually 'one-offs' or at least part of a very short run, and every new part that is used represents a risk that has to be understood and mitigated as necessary. This equates directly to time and cost. Standardization of component parts is used to provide a foundation of known, dependable, qualified parts upon which a safe, reliable system can be built. In addition, the evaluation and selection of parts for the standard parts list unifies the activity under one group of experts rather than having engineers on each project overlapping and duplicating efforts. Thus, the project support engineers are able to concentrate on understanding and mitigating the risks for the non standard parts required to meet specific requirements of their project. Rapid technology change is producing conditions that make any form of parts-based standardization increasingly difficult, particularly the use of Commercial Off The Shelf (COTS) parts and assemblies. There are many complications to COTS-based standardization. COTS parts change rapidly and unpredictably, often have different characteristics fiom manufacturer to manufacturer, frequently are only available through distribution, have no universal specification and have variable and unpredictable radiation characteristics. This presentation will discuss some potential approaches to COTS parts standardization. Further into the future, in three to five years perhaps, the use of COTS boards and boxes will be extensive and standardization at these levels of assembly will be necessary. In five to ten years, most major spacecraft functions will probably be performed by COTS boards. How will this be achieved? What role will the parts engineer play, if any? This presentation will borrow from the lessons of the past to suggest some scenarios for the future.

Sampson, Michael J.↗

SCOS 2: An object oriented software development approach

The Spacecraft Control and Operations System 2 (SCOS 2), is intended to provide the generic mission control system infrastructure for future ESA missions. It represents a bold step forward in order to take advantage of state-of-the-art technology and current practices in the area of software engineering. Key features include: (1) use of object oriented analysis and design techniques; (2) use of UNIX, C++ and a distributed architecture as the enabling implementation technology; (3) goal of re-use for development, maintenance and mission specific software implementation; and (4) introduction of the concept of a spacecraft control model. This paper touches upon some of the traditional beliefs surrounding Object Oriented development and describes their relevance to SCOS 2. It gives rationale for why particular approaches were adopted and others not, and describes the impact of these decisions. The development approach followed is discussed, highlighting the evolutionary nature of the overall process and the iterative nature of the various tasks carried out. The emphasis of this paper is on the process of the development with the following being covered: (1) the three phases of the SCOS 2 project - prototyping & analysis, design & implementation and configuration / delivery of mission specific systems; (2) the close cooperation and continual interaction with the users during the development; (3) the management approach - the split between client staff, industry and some of the required project management activities; (4) the lifecycle adopted being an enhancement of the ESA PSS-05 standard with SCOS 2 specific activities and approaches defined; and (5) an examination of some of the difficulties encountered and the solutions adopted. Finally, the lessons learned from the SCOS 2 experience are highlighted, identifying those issues to be used as feedback into future developments of this nature. This paper does not intend to describe the finished product and its operation, but focusing on the journey to arrive there, concentrating therefore on the process and not the products of the SCOS 2 software development.

Symonds, Martin↗

Report of the Interagency Space Reactor Standards Working Group

A U.S. governmental interagency space reactor standards working group (SWG) was convened in April 2021 with a memo from the NASA Chief Engineer to address the limited standards and regulations in place specifically for space reactor design and safety. The convening memo requested support from the Standards Executives of six other federal agencies. The Standards Executives agreed to support a 6-month study to assess the need for consensus standards and identified SWG representatives from each agency. This report summarizes the SWG’s study, their findings, and their recommendations.

Space Reactor Standards Working Group↗

Lightning Protection and Structural Bonding for the B2 Test Stand

With the privatization of the space industry, NASA has entered a new era. To explore deeper parts of the solar system, NASA is developing a new spacecraft, the Space Launch System (SLS), capable of reaching these destinations, such as an asteroid or Mars. However, the test stand that is capable of testing the stage has been unused for many years. In addition to the updating/repair of the stand, more steel is being added to fully support the SLS. With all these modifications, the lightning protection system must be brought up to code to assure the protection of all personnel and assets. Structural bonding is a part of the lightning protection system. The focus of this project was to assure proper structural bonding. To begin, all relevant technical standards and the construction specifications were reviewed. This included both the specifications for the lightning protection and for general construction. The drawings were reviewed as well. From the drawings, bolted structural joints were reviewed to determine whether bonding was necessary. Several bolted joints were determined to need bonding according to the notes in the drawings. This exceeds the industry standards. The bolted joints are an electrically continuous joint. During tests, the stand experiences heavy vibration that may weaken the continuity of the bolted joint. Therefore, the secondary bonding is implemented to ensure that the structural joint has low resistance. If the structural joint has a high resistance because of corrosion, a potential gradient can occur that can cause a side flash. Damage, injury, or death can occur from a side flash so they are to be prevented. A list of the identified structural joints was compiled and sent to the contractor to be bonded. That covers the scope of this project.

Kinard, Brandon↗

The NASA program for standardizing silicon solar cells

The program is discussed which was initiated to formulate standard silicon solar cell and cover specifications. The program includes (1) compilation of solar cell and cover specifications, both past and present (2) elicitation of inputs from major users and suppliers and (3) establishment of tentative standardized solar cell and cover specifications.

Bifano, W. J.↗

Intelligent Devices - Sensors and Actuators - A KSC Perspective

The primary objective of this workshop is to identify areas of advancement in sensor measurements and technologies that will help to define standard practices and procedures that will better enable the infusion into flight programs of sensors with improved capabilities but limited or no flight heritage. These standards would be crucial to demonstrating a methodology for validating current models while also creating the possibility of being able to have sufficient data to either update these models (e. g., spatial or temporal resolution, etc.) or develop new models based on the ability to simulate the new measured physical parameters. The workshop is also intended to narrow the gap between sensor measurements (and techniques), data processing techniques and the ability to make use of that data by gathering together experts in the field for a short workshop. This collaboration will unite NASA and other government agencies with contractor capabilities industry-wide to prevent duplication, spawn synergistic growth in sensor technology, help analysts make good engineering decisions and help focus new sensor maturation efforts to better meet future flight program customers' needs. This is the first such workshop designed to specifically address establishing a standardized protocol/methodology for demonstrating the technology readiness of non-flight heritage sensor systems. While other similar workshops are held covering many areas of interest to the sensor development community, no other meeting is specific enough to address this vital but often overlooked topic. By encouraging cross-fertilization of ideas from instrument experts from many different backgrounds, it is hoped that this workshop will initiate innovative new ideas and concepts in sensor development, calibration and validation. It is anticipated this workshop will repeat periodically as needed.

Mata, Carlos T.↗

Integrated flexible manufacturing program for manufacturing automation and rapid prototyping

The Kansas City Division of Allied Signal Inc., as part of the Integrated Flexible Manufacturing Program (IFMP), is developing an integrated manufacturing environment. Several systems are being developed to produce standards and automation tools for specific activities within the manufacturing environment. The Advanced Manufacturing Development System (AMDS) is concentrating on information standards (STEP) and product data transfer; the Expert Cut Planner system (XCUT) is concentrating on machining operation process planning standards and automation capabilities; the Advanced Numerical Control system (ANC) is concentrating on NC data preparation standards and NC data generation tools; the Inspection Planning and Programming Expert system (IPPEX) is concentrating on inspection process planning, coordinate measuring machine (CMM) inspection standards and CMM part program generation tools; and the Intelligent Scheduling and Planning System (ISAPS) is concentrating on planning and scheduling tools for a flexible manufacturing system environment. All of these projects are working together to address information exchange, standardization, and information sharing to support rapid prototyping in a Flexible Manufacturing System (FMS) environment.

Brooks, S. L.↗

A Cognitive Systems Engineering Approach to Developing HMI Requirements for New Technologies

This document examines the challenges inherent in designing and regulating to support human-automation interaction for new technologies that will deployed into complex systems. A key question for new technologies, is how work will be accomplished by the human and machine agents. This question has traditionally been framed as how functions should be allocated between humans and machines. Such framing misses the coordination and synchronization that is needed for the different human and machine roles in the system to accomplish their goals. Coordination and synchronization demands are driven by the underlying human-automation architecture of the new technology, which are typically not specified explicitly by the designers. The human machine interface (HMI) which is intended to facilitate human-machine interaction and cooperation, however, typically is defined explicitly and therefore serves as a proxy for human-automation cooperation requirements with respect to technical standards for technologies. Unfortunately, mismatches between the HMI and the coordination and synchronization demands of the underlying human-automation architecture, can lead to system breakdowns. A methodology is needed that both designers and regulators can utilize to evaluate the expected performance of a new technology given potential human-automation architectures. Three experiments were conducted to inform the minimum HMI requirements a detect and avoid system for unmanned aircraft systems (UAS). The results of the experiments provided empirical input to specific minimum operational performance standards that UAS manufacturers will have to meet in order to operate UAS in the National Airspace System (NAS). These studies represent a success story for how to objectively and systematically evaluate prototype technologies as part of the process for developing regulatory requirements. They also provide an opportunity to reflect on the lessons learned from a recent research effort in order to improve the methodology for defining technology requirements for regulators in the future. The biggest shortcoming of the presented research program was the absence of the explicit definition, generation and analysis of potential human-automation architectures. Failure to execute this step in the research process resulted in less efficient evaluation of the candidate prototypes technologies in addition to the complete absence of different approaches to human-automation cooperation. For example, all of the prototype technologies that were evaluated in the research program assumed a human-automation architecture that relied on serial processing from the automation to the human. While this type of human-automation architecture is typical across many different technologies and in many different domains, it ignores different architectures where humans and automation work in parallel. Defining potential human-automation architectures a priori also allows regulators to develop scenarios that will stress the performance boundaries of the technology during the evaluation phase. The importance of adding this step of generating and evaluating candidate human-automation architectures prior to formal empirical evaluation is discussed.

human systems integration↗

Transputer parallel processing at NASA Lewis Research Center

The transputer parallel processing lab at NASA Lewis Research Center (LeRC) consists of 69 processors (transputers) that can be connected into various networks for use in general purpose concurrent processing applications. The main goal of the lab is to develop concurrent scientific and engineering application programs that will take advantage of the computational speed increases available on a parallel processor over the traditional sequential processor. Current research involves the development of basic programming tools. These tools will help standardize program interfaces to specific hardware by providing a set of common libraries for applications programmers. The thrust of the current effort is in developing a set of tools for graphics rendering/animation. The applications programmer currently has two options for on-screen plotting. One option can be used for static graphics displays and the other can be used for animated motion. The option for static display involves the use of 2-D graphics primitives that can be called from within an application program. These routines perform the standard 2-D geometric graphics operations in real-coordinate space as well as allowing multiple windows on a single screen.

Ellis, Graham K.↗

Extravehicular Activity (EVA) Office Exploration EVA System Technical Standards

The purpose of this Extravehicular Activity (EVA) Office specification is to define the types of Programmatic-level standards to be used for design, manufacturing, testing, and quality control for the Exploration EVA (xEVA) System. The xEVA system includes both space suits and EVA hardware elements (e. EVA Tools, Airlock hardware, etc.). Many of the standards referenced in this document can be substituted for similar standards used in industry; this document provides the scope of which standards need to be considered. This document is the EVA-centric implementation of Chapter 3 of NPR 7120.10, Technical Standards for National Aeronautics and Space Administration (NASA) Programs and Projects: Select technical standards for use as program/project requirements. This also addresses the intent of Section 2.2.6 of NPR 8705.2, Human-Rating Requirements for Space Systems.

EVA↗