Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Requirement and 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 37 records · Page 2

Behavioral Makers to Assess During Selection for Active and Non-Active Astronauts

INTRODUCTION: NASA and our international partners seek to stay ahead of the evolving nature of the astronaut role. Spaceflight comes with various risks to team and individual. NASA has worked with its international partners in developing selection guidelines for minimal behavioral competencies needed upon selection. Training should be provided on the remaining behavioral competencies required for spaceflight. We will provide an overview of the process of identifying competencies important to assess as part of a multi-method selection program for active and non-active astronauts. TOPIC: NASA, ESA, CSA, and JAXA agency representatives used their vast combined knowledge and experience to develop competency requirement standards that future selection programs should assess when selecting astronauts. The astronaut role is expanding to include astronauts whose purposes are quite varied. NASA and its international partners identified the need to identify what competencies are required for anyone who will be experiencing the incredible demands, risks, and unique circumstances associated with spaceflight. Competencies include those required for individual and team functioning within the isolated, confined, and extreme environment. This need grew out of greater commercialization of spaceflight and other budding spaceflight prospects. 1. Each agency rated previously defined spaceflight required competencies (not important 0, somewhat important .5, or extremely important 1) to assess during selection. We did this for short duration (<14 days) and for long duration (<14 days) missions as some competencies appear to become of greater importance with longer duration missions. 2. We rated competencies for non-active crew and revisited previous ratings for active crew. 3. We compared agency ratings for non-active/active and short-duration/long-duration requirements and discussed in ratings until consensus was reached. We will use ratings to compile selection standards for active and non-active astronauts. APPLICATION: Our working group has vast operational experience and knowledge of the risk factors present during spaceflight that can disrupt individual and team functioning. Selection is one of the most important countermeasures for mitigating risk to individual and team health and performance. Our work should inform future programs for selecting crewmembers for short- and long-duration spaceflight among active and non-active crews.

Alexa Baxley↗

Managing HRP’S External Deliverables: The Process and the Customers

The Human Research Program’s (HRP) external deliverables (EDs) are the final outcomes of the research that the HRP Elements develop and execute. Four categories of HRP EDs exist: standards, requirements, countermeasures, and tools/technology. The NASA Human Health and Performance directorate’s primary stakeholders, i.e., the customers for the EDs, include the Office of the Chief Health and Medical Officer (OCHMO) (Standards Team, Chief Health and Performance Officers and Chief Medical Officers, Human System Risk Board), and the agency’s System Capability Leadership Teams. The EDs may address the need of a specific customer, a specific design reference mission, or a vehicle lifecycle milestone. HRP’s Maturation and Integration Office External Programs facilitates the process of delivering the EDs to the targeted customers according to the customer’s expectations. This presentation describes this coordinated process and provides an overview of the nature of different types of EDs and how they impact the customers’ products. Successful transfer of the EDs to the customers will help mitigate the health and performance risks that crewmembers will face during NASA’s future exploration missions.

HRP research external deliverables↗

Human Research Program Advanced Exercise Concepts (AEC) Overview

Exercise countermeasures provide benefits that are crucial for successful human spaceflight, to mitigate the spaceflight physiological deconditioning which occurs during exposure to microgravity. The NASA Human Research Program (HRP) within the Human Exploration and Operations Mission Directorate (HEOMD) is managing next generation Advanced Exercise Concepts (AEC) requirements development and candidate technology maturation to Technology Readiness Level (TRL) 7 (ground prototyping and flight demonstration) for all exploration mission profiles from Multi Purpose Crew Vehicle (MPCV) Exploration Missions (up to 21 day duration) to Mars Transit (up to 1000 day duration) missions. These validated and optimized exercise countermeasures systems will be provided to the ISS Program and MPCV Program for subsequent flight development and operations. The International Space Station (ISS) currently has three major pieces of operational exercise countermeasures hardware: the Advanced Resistive Exercise Device (ARED), the second-generation (T2) treadmill, and the cycle ergometer with vibration isolation system (CEVIS). This suite of exercise countermeasures hardware serves as a benchmark and is a vast improvement over previous generations of countermeasures hardware, providing both aerobic and resistive exercise for the crew. However, vehicle and resource constraints for future exploration missions beyond low Earth orbit will require that the exercise countermeasures hardware mass, volume, and power be minimized, while preserving the current ISS capabilities or even enhancing these exercise capabilities directed at mission specific physiological functional performance and medical standards requirements. Further, mission-specific considerations such as preservation of sensorimotor function, autonomous and adaptable operation, integration with medical data systems, rehabilitation, and in-flight monitoring and feedback are being developed for integration with the exercise countermeasures systems. Numerous technologies have been considered and evaluated against HRP-approved functional device requirements for these extreme mission profiles, and include wearable sensors, exoskeletons, flywheel, pneumatic, and closed-loop microprocessor controlled motor driven systems. Each technology has unique advantages and disadvantages. The Advanced Exercise Concepts project oversees development of candidate next generation exercise countermeasures hardware, performs trade studies of current and state of the art exercise technologies, manages and supports candidate systems physiological evaluations with human test subjects on the ground, in flight analogs and flight. The near term goal is evaluation of candidate systems in flight, culminating in an integrated candidate next generation exercise countermeasures suite on the ISS which coalesces research findings from HRP disciplines in the areas of exercise performance for muscle, bone, cardiovascular, sensorimotor, behavioral health, and nutrition for optimal benefit to the crew.

Countermeasures↗

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.

Ingalls, John↗

Energy Conversion Alternatives Study (ECAS), General Electric Phase 1. Volume 1: Executive summary

A data base for the comparison of advanced energy conversion systems for utility applications using coal or coal-derived fuels was developed. Estimates of power plant performance (efficiency), capital cost, cost of electricity, natural resource requirements, and environmental intrusion characteristics were made for ten advanced conversion systems. Emphasis was on the energy conversion system in the context of a base loaded utility power plant. All power plant concepts were premised on meeting emission standard requirements. A steam power plant (3500 psig, 1000 F) with a conventional coal-burning furnace-boiler was analyzed as a basis for comparison. Combined cycle gas/steam turbine system results indicated competitive efficiency and a lower cost of electricity compared to the reference steam plant. The Open-Cycle MHD system results indicated the potential for significantly higher efficiency than the reference steam plant but with a higher cost of electricity.

Corman, J. C.↗

HSI in NASA: From Research to Implementation

As NASA plans to send human explorers beyond low Earth orbit, onward to Mars and other destinations in the solar system, there will be new challenges to address in terms of HSI. These exploration missions will be quite different from the current and past missions such as Apollo, Shuttle, and International Space Station. The exploration crew will be more autonomous from ground mission control with delayed, and at times, no communication. They will have limited to no resupply for much longer mission durations. Systems to deliver and support extended human habitation at these destinations are extremely complex and unique, presenting new opportunities to employ HSI practices. In order to have an effective and affordable HSI implementation, both research and programmatic efforts are required. Currently, the HSI-related research at NASA is primarily in the area of space human factors and habitability. The purpose is to provide human health and performance countermeasures, knowledge, technologies, and tools to enable safe, reliable, and productive human space exploration beyond low Earth orbit, and update standards, requirements, and processes to verify and validate these requirements. In addition, HSI teams are actively engaged in technology development and demonstration efforts to influence the mission architecture and next-generation vehicle design. Finally, appropriate HSI references have been added to NASA' s systems engineering documentation, and an HSI Practitioner's Guide has been published to help design engineers consider HSI early and continuously in the acquisition process. These current and planned HSI-related activities at NASA will be discussed in this panel.

Whitmore, Mihriban↗

Guideline requirements for serviceable spacecraft grasping/berthing/docking interfaces based on simulations and flight experience (survey paper)

As space vehicles and structures become larger and more complex, the development of systems to assist humans in assembling, operating, maintaining, and performing space rescue or retrieval of these vehicles and structures becomes increasingly important. With the diversity of international spacecraft, both manned and unmanned, planned to be in orbit in the future, a set of guidelines for berthing and docking subsystems is mandatory if servicing, resupply, and retrieval is to become practical on an international level. Successful interaction between these space systems and ground and/or space-based humans requires standardized and effective operational interface designs, particularly with respect to space grasping/berthing/docking interface mechanisms. This paper defines the spacecraft mechanical interfaces necessary to create a standard dynamic envelope for joining two free-flying spacecraft in a 'hard' berth or dock with each other in space. A review was made of past space flights and dynamics simulations dating back to 1962 to obtain necessary parameters and their values for successful manually controlled and autonomous spacecraft docking/berthing. The various spacecraft docking/berthing mechanisms and concepts are illustrated along with their dynamic capture and impact tolerances including maximum contact velocity along the approach axis and in the y-z plane; capture linear misalignment tolerances; and maximum capture roll, pitch, and yaw angles. From this data sets of recommended guidelines parameters were developed for autonomous and manual impact docking tolerances, non-impact grasping/berthing tolerances (end effectors), berthing contact conditions, and alignment tolerances after rigidizing. Also, detailed requirements were developed for mechanical design interface features, as well as latching, unlatching, and separation tolerances. This data was drafted in the form of a proposed ANSI Standard guideline, reviewed, and added to by members of the committee representing several spacecraft manufacturers, NASA, and the USAF, and a consensus was reached.

Thompson, Allen B.↗

Boeing Vertol noise reduction experience

Boeing Vertol Model 234, CH-47D and 347 tandem rotor helicopters demonstrate noise levels that comply with the overall noise standard requirements. The helicopters achieve these noise levels because they are, by design, free of impulsive noise in level flight and climb. Avoiding an impulsive noise signature is achieved by developing and applying configuration design criteria that eliminate blade vortex intersections and recognize advancing blade tip noise limitations in high speed forward flight. Airfoil design, rotor separation and rotor tipspeed selection all contribute to the noise control. Compliance with the approach element of the standards is marginal at best. The approach problem is not appreciably alleviated by reduced tipspeed and airfoil design. Since it is a single rotor phenomenon, it is not alleviated by rotor separation in the tandem configuration. Tip shapes may provide the answer, but to date this approach has not led to a satisfactory solution.

Walls, W. W.↗

Notional Scoring for Technical Review Weighting As Applied to Simulation Credibility Assessment

NASA's Modeling and Simulation Standard requires a credibility assessment for critical engineering data produced by models and simulations. Credibility assessment is thus a "qualifyingfactor" in reporting results from simulation-based analysis. The degree to which assessors should be independent of the simulation developers, users and decision makers is a recurring question. This paper provides alternative "weighting algorithms" for calculating the value-added for independence of the levels of technical review defined for the NASA Modeling and Simulation Standard.

Hale, Joseph Peter↗

Automating test case generation for coverages required by FAA standard DO-178B

Coverage testing techniques are required by the FAA for various levels of subsystem criticality at the unit testing level. Higher levels of criticality require coverage schemes that frequently require more and more test cases, particularly when the number of conditions in a decision grows. For example, if we have a decision with n conditions of the form: if (/ci/ or /c2/ or .... or /cn/) then there are 2(n) possible combinations of condition outcomes. Given the enormous number of inputs that may be required to satisfy different coverages, and given that there are no automated tools for determining these inputs (to our knowledge), we will show how one alternative testing technique, mutation testing, can be coerced into generating inputs that satisfy a code coverage scheme X, i.e., if we modify the rules for mutant generation during mutation testing, this technique will provide test cases that satisfy X.

Voas, Jeffrey M.↗

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗

NASA specification for manufacturing and performance requirements of NASA standard aerospace nickel-cadmium cells

On November 25, 1985, the NASA Chief Engineer established a NASA-wide policy to maintain and to require the use of the NASA standard for aerospace nickel-cadmium cells and batteries. The Associate Administrator for Safety, Reliability, Maintainability, and Quality Assurance stated on December 29, 1986, the intent to retain the NASA standard cell usage policy established by the Office of the Chief Engineer. The current NASA policy is also to incorporate technological advances as they are tested and proven for spaceflight applications. This policy will be implemented by modifying the existing standard cells or by developing new NASA standards and their specifications in accordance with the NASA's Aerospace Battery Systems Program Plan. This NASA Specification for Manufacturing and Performance Requirements of NASA Standard Aerospace Nickel-Cadmium Cells is prepared to provide requirements for the NASA standard nickel-cadmium cell. It is an interim specification pending resolution of the separator material availability. This specification has evolved from over 15 years of nickel-cadmium cell experience by NASA. Consequently, considerable experience has been collected and cell performance has been well characterized from many years of ground testing and from in-flight operations in both geosynchronous (GEO) and low earth orbit (LEO) applications. NASA has developed and successfully used two standard flight qualified cell designs.

Source record↗

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.↗

NASA-STD-6016 Standard Materials and Processes Requirements for Spacecraft

The standards for materials and processes surrounding spacecraft are discussed. Presentation focused on minimum requirements for Materials and Processes (M&P) used in design, fabrication, and testing of flight components for NASA manned, unmanned, robotic, launch vehicle, lander, in-space and surface systems, and spacecraft program/project hardware elements.Included is information on flammability, offgassing, compatibility requirements, and processes; both metallic and non-metallic materials are mentioned.

Hirsch, David B.↗

Automated process planning system

Program helps process engineers set up manufacturing plans for machined parts. System allows one to develop and store library of similar parts characteristics, as related to particular facility. Information is then used in interactive system to help develop manufacturing plans that meet required standards.

Mann, W.↗

Performance, emissions, and physical characteristics of a rotating combustion aircraft engine

The RC2-75, a liquid cooled two chamber rotary combustion engine (Wankel type), designed for aircraft use, was tested and representative baseline (212 KW, 285 BHP) performance and emissions characteristics established. The testing included running fuel/air mixture control curves and varied ignition timing to permit selection of desirable and practical settings for running wide open throttle curves, propeller load curves, variable manifold pressure curves covering cruise conditions, and EPA cycle operating points. Performance and emissions data were recorded for all of the points run. In addition to the test data, information required to characterize the engine and evaluate its performance in aircraft use is provided over a range from one half to twice its present power. The exhaust emissions results are compared to the 1980 EPA requirements. Standard day take-off brake specific fuel consumption is 356 g/KW-HR (.585 lb/BHP-HR) for the configuration tested.

Berkowitz, M.↗

The development version control and visibility subsystem

A prototype development version control and programming environment visibility subsystem (DVCS) is described. DVCS provides an implementation/management interface serving both the implementor and management. The DVCS provides the implementor listings annotated with change bars, detects errors in the block structure of the design and indicates when standards requiring the use of structured programming constructs in the design of software are violated.

Hawley, L. R.↗