Search NASA⌕ Search

SEARCH · Search NASA

Results for “parts program 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 73 records · Page 4

3D Printing In Zero-G ISS Technology Demonstration

The National Aeronautics and Space Administration (NASA) has a long term strategy to fabricate components and equipment on‐demand for manned missions to the Moon, Mars, and beyond. To support this strategy, NASA and Made in Space, Inc. are developing the 3D Printing In Zero‐G payload as a Technology Demonstration for the International Space Station (ISS). The 3D Printing In Zero‐G experiment ('3D Print') will be the first machine to perform 3D printing in space. The greater the distance from Earth and the longer the mission duration, the more difficult resupply becomes; this requires a change from the current spares, maintenance, repair, and hardware design model that has been used on the International Space Station (ISS) up until now. Given the extension of the ISS Program, which will inevitably result in replacement parts being required, the ISS is an ideal platform to begin changing the current model for resupply and repair to one that is more suitable for all exploration missions. 3D Printing, more formally known as Additive Manufacturing, is the method of building parts/objects/tools layer‐by‐layer. The 3D Print experiment will use extrusion‐based additive manufacturing, which involves building an object out of plastic deposited by a wire‐feed via an extruder head. Parts can be printed from data files loaded on the device at launch, as well as additional files uplinked to the device while on‐orbit. The plastic extrusion additive manufacturing process is a low‐energy, low‐mass solution to many common needs on board the ISS. The 3D Print payload will serve as the ideal first step to proving that process in space. It is unreasonable to expect NASA to launch large blocks of material from which parts or tools can be traditionally machined, and even more unreasonable to fly up multiple drill bits that would be required to machine parts from aerospace‐grade materials such as titanium 6‐4 alloy and Inconel. The technology to produce parts on demand, in space, offers unique design options that are not possible through traditional manufacturing methods while offering cost-effective, high‐precision, low‐unit on‐demand manufacturing. Thus, Additive Manufacturing capabilities are the foundation of an advanced manufacturing in space roadmap. The 3D Printing In Zero‐G experiment will demonstrate the capability of utilizing Additive Manufacturing technology in space. This will serve as the enabling first step to realizing an additive manufacturing, print‐on‐demand "machine shop" for long‐duration missions and sustaining human exploration of other planets, where there is extremely limited ability and availability of Earth‐based logistics support. Simply put, Additive Manufacturing in space is a critical enabling technology for NASA. It will provide the capability to produce hardware on‐demand, directly lowering cost and decreasing risk by having the exact part or tool needed in the time it takes to print. This capability will also provide the much‐needed solution to the cost, volume, and up‐mass constraints that prohibit launching everything needed for long‐duration or long‐distance missions from Earth, including spare parts and replacement systems. A successful mission for the 3D Printing In Zero‐G payload is the first step to demonstrate the capability of printing on orbit. The data gathered and lessons learned from this demonstration will be applied to the next generation of additive manufacturing technology on orbit. It is expected that Additive Manufacturing technology will quickly become a critical part of any mission's infrastructure.

Werkheiser, Niki↗

Building a Transdisciplinary, Exascale-Capable Workforce for Geospace Science

Key Points: ●First-principles, self-consistent geospace modeling will require at least exascale-level computing capabilities; however, the technical skills necessary to develop such simulation codes are not taught as part of Heliophysics training/PhD programs. ●Developing exascale Heliophysics codes will require transdisciplinary collaborations between physicists, computer scientists, software engineers, data scientists, and applied mathematics. Such teams must be persistent and formed around specific skills, not specific problems. ●We must have stable, positive long-term career outcomes for Heliophysics scientific developers in order to retain knowledge of and promote future innovation in scientific algorithm development and advanced computing techniques. One such way to do this is by funding long-term scientific programming groups, akin to Heliophysics DRIVE Centers. ●We must have a balance between promoting innovation via funding short-term closed-source development and allowing the open-source community to benefit from and build on the newest scientific modeling techniques.

C Bard↗

Flight program language requirements. Volume 1: Executive summary

The activities and results of a study for the definition of flight program language requirements are described. A set of detailed requirements are presented for a language capable of supporting onboard application programming for the Marshall Space Flight Center's anticipated future activities in the decade of 1975-85. These requirements are based, in part, on the evaluation of existing flight programming language designs to determine the applicability of these designs to flight programming activities which are anticipated. The coding of benchmark problems in the selected programming languages is discussed. These benchmarks are in the form of program kernels selected from existing flight programs. This approach was taken to insure that the results of the study would reflect state of the art language capabilities, as well as to determine whether an existing language design should be selected for adaptation.

Source record↗

Lubricant and seal technologies for the next generation of lunar roving vehicles

In a recent study commissioned by NASA it was determined that tribological failures can be life-limiting in many applications for the next generation of lunar rover vehicles and therefore warrant special consideration. This paper describes the technological issues and key findings of the study. Recommended technology development needs are also presented. Because the suitability of lubricant and seal concepts must be evaluated in the context of a specific application, these technology programs are tied to advanced development of key system components. The mobility subsystem mechanisms on rover vehicles plus selected components of attached tools were determined to be essential elements which warrant advanced development in order to enhance reliability and decrease maintenance requirements. Accurate assessments of EVA, logistic support, and spare parts requirements cannot be accomplished until the advanced development programs near completion.

Ramsey, Paul S.↗

Onboard Inert Gas Generation System/Onboard Oxygen Gas Generation System (OBIGGS/OBOGS) Study: Aircraft System Requirements - Part 1

The purpose of this technology assessment is to define a multiphase research study program investigating Onboard Inert Gas Generation Systems (OBIGGS) and Onboard Oxygen Generation Systems (OBOGS) that would identify current airplane systems design and certification requirements (Subtask 1); explore state-of-the-art technology (Subtask 2); develop systems specifications (Subtask 3); and develop an initial system design (Subtask 4). If feasible, consideration may be given to the development of a prototype laboratory test system that could potentially be used in commercial transport aircraft (Subtask 5). These systems should be capable of providing inert nitrogen gas for improved fire cargo compartment fire suppression and fuel tank inerting and emergency oxygen for crew and passenger use. Subtask I of this research study, presented herein, defines current production aircraft certification requirements and design objectives necessary to meet mandatory FAA certification requirements and Boeing design and performance specifications. These requirements will be utilized for baseline comparisons for subsequent OBIGGS/OBOGS application evaluations and assessments.

Reynolds, Thomas L.↗

Design and testing of new center inlet and S-duct for B-727 airplane with refanned JT8D engines

The work described in this paper was part of the NASA refan program. The airflow requirement of the refanned JT8D (-100 series) engine increased about 50% above that of the basic JT8D. This required a redesign of the center inlet and S-duct of the Boeing 727 airplane. The paper describes the design constraints for the S-duct and the analytic method used to define the lines of the new duct. Model tests that were conducted at static, angle-of-attack, and crosswind conditions are described with a variety of flow control devices. Test results showed that the new inlet and S-duct have a pressure recovery comparable to that of the existing inlet. By employing corotating vortex generators, less flow distortion was obtained for the core region than the existing duct has with its counter rotating vortex generators.

Ting, C. T.↗

Advanced Free Flight Planner and Dispatcher's Workstation: Preliminary Design Specification

The National Aeronautics and Space Administration (NASA) has implemented the Advanced Air Transportation Technology (AATT) program to investigate future improvements to the national and international air traffic management systems. This research, as part of the AATT program, developed preliminary design requirements for an advanced Airline Operations Control (AOC) dispatcher's workstation, with emphasis on flight planning. This design will support the implementation of an experimental workstation in NASA laboratories that would emulate AOC dispatch operations. The work developed an airline flight plan data base and specified requirements for: a computer tool for generation and evaluation of free flight, user preferred trajectories (UPT); the kernel of an advanced flight planning system to be incorporated into the UPT-generation tool; and an AOC workstation to house the UPT-generation tool and to provide a real-time testing environment. A prototype for the advanced flight plan optimization kernel was developed and demonstrated. The flight planner uses dynamic programming to search a four-dimensional wind and temperature grid to identify the optimal route, altitude and speed for successive segments of a flight. An iterative process is employed in which a series of trajectories are successively refined until the LTPT is identified. The flight planner is designed to function in the current operational environment as well as in free flight. The free flight environment would enable greater flexibility in UPT selection based on alleviation of current procedural constraints. The prototype also takes advantage of advanced computer processing capabilities to implement more powerful optimization routines than would be possible with older computer systems.

Wilson, J.↗

Space Station Systems Analysis Study. Volume 1: Executive summary, part 1 and 2

The elements of space station programs required to support an operational base theme, a space laboratory theme, and advanced missions relatable to public needs/national interests are defined. Missions satisfying the foregoing requirements are identified, program scenarios/options are established. System options are evaluated for a selected number of program options. Subsystem analysis and programmatic comparisons are performed for selected primary concepts.

Source record↗

A Framework for Dimensioning VDL-2 Air-Ground Networks

This paper describes a framework developed at MITRE for dimensioning a Very High Frequency (VHF) Digital Link Mode 2 (VDL-2) Air-to-Ground network. This framework was developed to support the FAA's Data Communications (Data Comm) program by providing estimates of expected capacity required for the air-ground network services that will support Controller-Pilot-Data-Link Communications (CPDLC), as well as the spectrum needed to operate the system at required levels of performance. The Data Comm program is part of the FAA's NextGen initiative to implement advanced communication capabilities in the National Airspace System (NAS). The first component of the framework is the radio-frequency (RF) coverage design for the network ground stations. Then we proceed to describe the approach used to assess the aircraft geographical distribution and the data traffic demand expected in the network. The next step is the resource allocation utilizing optimization algorithms developed in MITRE's Spectrum ProspectorTM tool to propose frequency assignment solutions, and a NASA-developed VDL-2 tool to perform simulations and determine whether a proposed plan meets the desired performance requirements. The framework presented is capable of providing quantitative estimates of multiple variables related to the air-ground network, in order to satisfy established coverage, capacity and latency performance requirements. Outputs include: coverage provided at different altitudes; data capacity required in the network, aggregated or on a per ground station basis; spectrum (pool of frequencies) needed for the system to meet a target performance; optimized frequency plan for a given scenario; expected performance given spectrum available; and, estimates of throughput distributions for a given scenario. We conclude with a discussion aimed at providing insight into the tradeoffs and challenges identified with respect to radio resource management for VDL-2 air-ground networks.

Aviation↗

Atmospheric, Magnetospheric and Plasmas in space (AMPS) spacelab payload definition study. Volume 4. Part 1, AMPS program specification

The AMPS Program Specification delineates the AMPS Program requirements consistent with the resources defined in the AMPS Project Plan. All subsidiary specifications and requirements shall conform to the requirements presented. The requirements hierarchy for the AMPS program is illustrated. A brief description of each of the requirements documents and their intended use is provided.

Keeley, J. T.↗

Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 4: Design of the IPAD system. Part 1: IPAD system design requirements, phase 1, task 2

System requirements, software elements, and hardware equipment required for an IPAD system are defined. An IPAD conceptual design was evolved, a potential user survey was conducted, and work loads for various types of interactive terminals were projected. Various features of major host computing systems were compared, and target systems were selected in order to identify the various elements of software required.

Garrocq, C. A.↗

Earth Observatory Satellite system definition study. Report no. 3: Design/cost tradeoff studies. Appendix E: EOS program supporting system. Part 1: System trade studies no. 1 through 8

The design requirements and associated cost impacts for using the space shuttle to deliver the Earth Observatory Satellite (EOS) are identified. The additional impact of achieving full compatibility for resupply and retrieval is considered. Based on the results of the analysis, it is concluded that the EOS-Shuttle compatibility can be realized with reasonable spacecraft weight and cost penalties. Inherent space shuttle capabilities are adequate to meet the requirements of all missions except E and F. Mission E (Tiros 0) may be accommodated by either an EOS orbit transfer capability or a tug. The tug appears to be the only viable approach to satisfying the mission F (SEOS) requirements.

Source record↗

Earth Observing System. Science and Mission Requirements, Volume 1, Part 1

The Earth Observing System (EOS) is a planned NASA program, which will carry the multidisciplinary Earth science studies employing a variety of remote sensing techniques in the 1990's, as a prime mission, using the Space Station polar platform. The scientific rationale, recommended observational needs, the broad system configuration and a recommended implementation strategy to achieve the stated mission goals are provided.

Source record↗

International Docking Standard (IDSS) Interface Definition Document (IDD) : Revision - E

This International Docking System Standard (IDSS) Interface Definition Document (IDD) is the result of a collaboration by the International Space Station membership to establish a standard docking interface to enable on-orbit crew rescue operations and joint collaborative endeavors utilizing different spacecraft. This IDSS IDD details the physical geometric mating interface and design loads requirements. The physical geometric interface requirements must be strictly followed to ensure physical spacecraft mating compatibility. This includes both defined components and areas that are void of components. The IDD also identifies common design parameters as identified in section 3.0, e.g., docking initial conditions and vehicle mass properties. This information represents a recommended set of design values enveloping a broad set of design reference missions and conditions, which if accommodated in the docking system design, increases the probability of successful docking between different spacecraft. This IDD does not address operational procedures or off-nominal situations, nor does it dictate implementation or design features behind the mating interface. It is the responsibility of the spacecraft developer to perform all hardware verification and validation, and to perform final docking analyses to ensure the needed docking performance and to develop the final certification loads for their application. While there are many other critical requirements needed in the development of a docking system such as fault tolerance, reliability, and environments (e.g. vibration, etc.), it is not the intent of the IDSS IDD to mandate all of these requirements; these requirements must be addressed as part of the specific developer's unique program, spacecraft and mission needs. This approach allows designers the flexibility to design and build docking mechanisms to their unique program needs and requirements. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.

docking↗

Supporting flight data analysis for Space Shuttle Orbiter Experiments at NASA Ames Research Center

The Space Shuttle Orbiter Experiments program in responsible for collecting flight data to extend the research and technology base for future aerospace vehicle design. The Infrared Imagery of Shuttle (IRIS), Catalytic Surface Effects, and Tile Gap Heating experiments sponsored by Ames Research Center are part of this program. The paper describes the software required to process the flight data which support these experiments. In addition, data analysis techniques, developed in support of the IRIS experiment, are discussed. Using the flight data base, the techniques have provided information useful in analyzing and correcting problems with the experiment, and in interpreting the IRIS image obtained during the entry of the third Shuttle mission.

Green, M. J.↗

Supporting shared data structures on distributed memory architectures

Programming nonshared memory systems is more difficult than programming shared memory systems, since there is no support for shared data structures. Current programming languages for distributed memory architectures force the user to decompose all data structures into separate pieces, with each piece owned by one of the processors in the machine, and with all communication explicitly specified by low-level message-passing primitives. A new programming environment is presented for distributed memory architectures, providing a global name space and allowing direct access to remote parts of data values. The analysis and program transformations required to implement this environment are described, and the efficiency of the resulting code on the NCUBE/7 and IPSC/2 hypercubes are described.

Koelbel, Charles↗

Model Checking Abstract PLEXIL Programs with SMART

We describe a method to automatically generate discrete-state models of abstract Plan Execution Interchange Language (PLEXIL) programs that can be analyzed using model checking tools. Starting from a high-level description of a PLEXIL program or a family of programs with common characteristics, the generator lays the framework that models the principles of program execution. The concrete parts of the program are not automatically generated, but require the modeler to introduce them by hand. As a case study, we generate models to verify properties of the PLEXIL macro constructs that are introduced as shorthand notation. After an exhaustive analysis, we conclude that the macro definitions obey the intended semantics and behave as expected, but contingently on a few specific requirements on the timing semantics of micro-steps in the concrete executive implementation.

Siminiceanu, Radu I.↗

TPSAS-NF1676L-30470-DND

Outside NASA: Single Agency document that can be referenced in NASA contracts (e.g. CCP) and used in NASA-ESA-JAXA Mutual Recognition of SMA Standards Within NASA: - Lists requirements from Center documents that must be addressed by Programs and Projects in their EEE Parts Management and Control Plan (EPMCP) - Tailor-able by Center/Project Technical Authority - Standardize requirements for “Low Risk” projects -not to overburden “Higher Risk” projects with excessive requirements

Peter J Majewicz↗