Search NASASearch

SEARCH · Search NASA

Results for “technical levels”

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 55 records · Page 3

Skylab Operations Handbook: Orbital Workshop (OWS), Airlock Module (AM), Multiple Docking Adapter (MDA): Systems Descriptions - Volume 1

The Skylab Program consists of three low-earth-orbit missions of the Orbital Assembly (OA) (figure 1.0-1), extending over.an a-month period. The OA consists of the CSM docked to the Saturn Workshop.(SWS). This handbook describes the systems for three of the four major components of the SWS (OWS, AM, and MDA), and also discusses significant interfaces with the Instrument Unit (IU), ATM, and CSM. The other major component of the SWS, the ATM, is treated separately in its own handbook. The OWS, AM, MDA, ATM Deployment Assembly (ATM-DA), Fixed Airlock Shroud (FAS), Payload Shroud (PS), and IU are addressed throughout this document as individual modules from a structural standpoint only. Although normally considered a part of the launch vehicle, the IU is treated in this document as part of the SWS because of its function in preparing the SWS for orbital operation. Section 1.0 describes vehicle and mission configurations of the Skylab program and provides general descriptions of the various systems. Section 2.0 provides detailed systems data covering system interfaces, functional description, subsystems and major components description, component operation, failure modes, performance and design data, operational limitations and restrictions, and instrumentation, and briefly outlines the experiments. Section 3.0 contains illustrations of all panels and identifies the controls and displays, panels, reference designators, nomenclature, functions, circuit breakers, and power sources. The Table of Contents lists in order of appearance all sections, subsections, major paragraphs, illustrations, and tables and provides their respective page locations. Appendix A defines the abbreviations and acronyms employed throughout this handbook, and Appendix B explains the symbols used. Appendix C is a locator index that references component controls contained in Section 3.0. Appendix D is an alphabetical index of paragraph headings, illustrations, and tables, according to the key word, with applicable page numbers. Additional items of significance to the user have been included in the index. The technical level to which this document is written assumes the reader to have general knowledge of engineering terms and principles.

West, W. D.

Lunar Hydrogen Infrastructure

This presentation uses recent developments and discoveries to provide a high-level technical overview of a hydrogen-based energy infrastructure that supports sustained exploration of the moon. Combining creative orbital mechanics, robotic mining and process automation techniques, humanity can use lunar resources to generate the necessary propellant to support the transportation of cargo and humans between multiple points in the cis-lunar space. Robotic systems could collect water by either directly collecting the water entrained in the lunar regolith or by processing minerals found in the lunar regolith. These robotic systems could then electrolyze the water to generate high quality hydrogen and oxygen propellant and capitalize on the very low temperatures (< 15 Kelvin) in permanently shadowed regions (PSR) to maintain these propellants in a cryogenic state. Uncrewed service vehicles could distribute this lunar-generated resource throughout the cis-lunar space to intermediary waystations, like the Gateway. These platforms enable larger payloads into Low Earth Orbit (LEO) by providing the propellant necessary to travel through the cis-lunar space without requiring launch mass to lift the propellant and supporting tankage into LEO from the Earth's surface. Delivering 1 kg to LEO from the lunar surface reduces the propellant mass of the launch vehicle from Earth by 7 kg to 11.3 kg, depending on the final destination. By leveraging resources among multiple nations and corporations, this exploration infrastructure potentially can be both fiscally self-supporting and enable more organizations to sustain a human presence on the moon.

Lunar Architecture

Designing Experiments for SpinSat, A Novel Variable-Gravity-and-Radiation Platform for Deep-Space Science

Conducting experiments to measure the effects of deep-space radiation and reduced gravity on biological and physical systems remains challenging. The result is a substantial knowledge gap that poses risks to our ability to sustain life and conduct critical operations in deep space. The SpinSat spacecraft platform is designed to bridge such gaps by providing low-cost, reliable, and frequent access to deep space. A disk-shaped rotating satellite that can provide artificial gravity and exposure to space radiation simultaneously, SpinSat is designed to accommodate payloads in a CubeSat form factor (with at least 48 “U” volume), providing power, communications, and a benign thermal environment. It is orbit-agnostic, enabling access to a variety of radiation environments (Van Allen belts, deep space, cis-lunar); and can be equipped with shielding to mimic planetary radiation environments, for both short- and long-term experiments. Because of its versatility and prioritization of late loading for biological payloads, it is well suited to host a wide range of ranging from human tissues and organoids to microorganisms, plants, chemistry, and regolith. Here, we present examples of potential experiment concepts for SpinSat, and discuss the details of how experimental designs could interact with the platform. Potential SpinSat studies have diverse applications, including fundamental radiation biology and DNA repair; cancer biology and countermeasure development; space agriculture; bioproduction of nutrients and pharmaceuticals; understanding regolith dynamics in low gravity; prebiotic chemistry and panspermia. We will further highlight ideas for SpinSat-compatible experimental hardware, existing and in development, and experiment-relevant details on SpinSat capabilities including artificial gravity, potential radiation environments, data, and power. This presentation will aim to provide investigators with the high-level technical information necessary to inspire experiments for SpinSat. We also seek to stimulate conversation and to gain community input on accommodations needs to help guide the evolving design of this platform.

experiment design

An analysis of the technical status of high level radioactive waste and spent fuel management systems

The technical status of the old U.S. mailine program for high level radioactive nuclear waste management, and the newly-developing program for disposal of unreprocessed spent fuel was assessed. The method of long term containment for both of these waste forms is considered to be deep geologic isolation in bedded salt. Each major component of both waste management systems is analyzed in terms of its scientific feasibility, technical achievability and engineering achievability. The resulting matrix leads to a systematic identification of major unresolved technical or scientific questions and/or gaps in these programs.

English, T.

UTM RTT CWG Concept & Use Cases Package #2

The Concept & Use Cases Package #2: Technical Capability Level 3 document represents the collaborative research efforts between the FAA and NASA as joint members of the Unmanned Aircraft System Traffic Management (UTM) Research Transition Team (RTT). Contained in this document are the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views, and 6) Roles and Responsibilities of actors interacting within what is considered to be encompassed by Technical Capability Level 3 UTM operating environments. The contents of Package #2 should NOT be considered established policy or construed as regulatory in nature. What is presented is meant to communicate the current, agreed upon understanding between the FAA and NASA on particular features of UTM as exemplified through use cases and concept narratives for the purposes of supporting joint NASA/Industry Demonstrations and the UTM Pilot Program. It is also meant to foster discussion and refinement of the concepts and approaches being pursued by the other RTT working groups.

RTT

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 53: From student to entry-level professional: Examining the technical communications practices of early career-stage US aerospace engineers and scientists

Studies indicate that communications and information-related activities take up a substantial portion of an engineer's work week; therefore, effective communications and information-use skills are one of the key engineering competencies that early career-stage aerospace engineers and scientists must possess to be successful. Feedback from industry rates communications and information-use skills high in terms of their importance to engineering practice; however, this same feedback rates the communications and information-use skills of early career-stage engineers low. To gather adequate and generalizable data about the communications and information-related activities of entry-level aerospace engineers and scientists, we surveyed 264 members of the AIAA who have no more than 1-5 years of aerospace engineering work experience. To learn more about the concomitant communications norms, we compared the results of this study with data (1,673 responses) we collected from student members of the AIAA and with data (341 responses) we collected from a study of aerospace engineering professionals. In this paper, we report selected results from these studies that focused on the communications practices and information-related activities of early career-stage U.S. aerospace engineers and scientists in the workplace.

Pinelli, Thomas E.

Controlled flexibility in technical editing - The levels-of-edit concept at JPL

The levels-of-edit concept, which can be used to specify the amount of editorial effort involved in the preparation of a manuscript for publication, is discussed. Nine types of editing are identified and described. These include coordination edit (preparing estimates, gathering cost data, monitoring production processes), policy edit, integrity edit (making sure that parts of a publication match in a physical or numerical sense), screening edit (ensuring that the quality of camera-ready copy is sufficient for external publication), copy clarification edit, format edit, mechanical style edit, language edit, and substantive edit (reviewing the manuscript for content coherence, emphasis, subordination and parallelism). These functions are grouped into five levels of edit. An edit-level number is assigned to each manuscript, providing a quantitative and qualitative indicator of the editing to be done which is clearly understood by authors, managers, and editors alike. In addition, clear boundaries are drawn between normal and extraordinary editing tasks. Individual organizations will group various edits in different ways to reflect their needs and priorities; the essential element of the system is unambiguous definition and coding of the types and amount of work to be done.

Buehler, M. F.

eddy Users Manual

eddy is a collection of tools - nonlinear solvers, meshing, post-processing, visualization, optimization, etc. - for performing scale-resolving simulations of multi-physics applications. The framework is designed to enable advanced R&D on a variety of topics by leveraging a mature capability for scale resolving simulations, and simultaneously be an appropriate tool for application analysis and support. Currently, eddy is at a relatively low technical readiness level (TRL), and users and developers should maintain appropriate expectations. The technical details behind eddy are outlined in several publications which can be consulted for more information [1–10]. The solvers are built around an unstructured high-order capability, and heavily utilize the tensor product sum-factorization approach for efficiency. The unsteady formulation utilizes a fully implicit space-time approach with a matrix-free Newton- Krylov method. A primitive steady-state solver is available for testing purposes, but is not expected to converge for all but simple verification cases. The Navier-Stokes fluid solvers do not support either RANS or hybrid-RANS capability, only LES and wall-modeled LES approaches. All of the solvers within eddy support three modes of operation: a primal solve of the full nonlinear problem, and two linearization approaches of the primal solve - the ad joint and the tangent solution. Details on how to select and use these three modes are outlined in Sec. 3.

Murman, Scott M.

Small Unmanned Aircraft System Communications and Navigation Performance

NASA performed research and development of technologies and requirements for traffic management of small Unmanned Aircraft Systems (UAS). In this effort, four measures of performance (MOPs) were developed to understand the performance of small UAS communications and navigation systems in urban operations. This Technical Memorandum (TM) describes UAS Traffic Management (UTM) operational architecture, UTM Technical Capability Level 4 (TCL4) flight tests that took place in two different urban settings, the four MOPs, and the TCL4 MOP results.

Unmanned Aviation Systems Traffic Management

Automated Management of Small Unmanned Aircraft System Communications and Navigation Contingency

The number of small Unmanned Aircraft System (sUAS) operating in the low-altitude of the National Airspace System (NAS) has been rapidly increasing in the past few years and this number is expected to grow in the future. However, aside from a few special cases, all sUAS must fly within visual line-of-sight (VLOS) of their operators and this limitation is blocking highly anticipated beyond visual line-of-sight (BVLOS) sUAS applications such as package delivery from practice. To enable routine low-altitude BVLOS operations, there needs to be a traffic management ecosystem that complements the FAA’s Air Traffic Management (ATM) system, which does not provide air traffic services under 400 feet above ground level (AGL). NASA has been pioneering research and development of this ecosystem under UAS Traffic Management (UTM) project since 2015 in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting, and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for BVLOS operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 is building on the earlier TCLs and focuses on technologies and requirements for operations in higher-density urban areas for tasks such as newsgathering and package delivery and for managing large-scale contingencies. To coordinate and facilitate the incremental implementation of the UTM ecosystem in the NAS, a Research Transition Team (RTT) has been formed between the FAA, NASA, and industry. The RTT is divided into four subgroups, concept and use case development, data exchange and information architecture, sense and avoid, and communications and navigation (C&N). This paper focuses on C&N subgroup activities, in particular about the development of automated sUAS communications and navigation contingency management. The goal of this development is to prepare sUAS to display predictable behavior while handling C&N off-nominal events. It is expected that the adoption of the presented automated contingency management by the sUAS community will accommodate and inform rulemaking towards governing low-altitude BVLOS operations.

Unmanned Aviation System (UAS) Traffic Management

Automated Management of Small Unmanned Aircraft System (UAS) Communications and Navigation Contingency

The number of small Unmanned Aircraft System (sUAS) operating in the low-altitude of the National Airspace System (NAS) has been rapidly increasing in the past few years and this number is expected to grow in the future. However, aside from a few special cases, all sUAS must fly within visual line-of-sight (VLOS) of their operators and this limitation is blocking highly anticipated beyond visual line-of-sight (BVLOS) sUAS applications such as package delivery from practice. To enable routine low-altitude BVLOS operations, there needs to be a traffic management ecosystem that complements the FAA’s Air Traffic Management (ATM) system, which does not provide air traffic services under 400 feet above ground level (AGL). NASA has been pioneering research and development of this ecosystem under UAS Traffic Management (UTM) project since 2015 in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting, and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for BVLOS operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 is building on the earlier TCLs and focuses on technologies and requirements for operations in higher-density urban areas for tasks such as newsgathering and package delivery and for managing large-scale contingencies. To coordinate and facilitate the incremental implementation of the UTM ecosystem in the NAS, a Research Transition Team (RTT) has been formed between the FAA, NASA, and industry. The RTT is divided into four subgroups, concept and use case development, data exchange and information architecture, sense and avoid, and communications and navigation (C&N). This paper focuses on C&N subgroup activities, in particular about the development of automated sUAS communications and navigation contingency management. The goal of this development is to prepare sUAS to display predictable behavior while handling C&N off-nominal events. It is expected that the adoption of the presented automated contingency management by the sUAS community will accommodate and inform rulemaking towards governing low-altitude BVLOS operations.

Unmanned Aviation Systems (UAS) Traffic Management

A Multi-Center Space Data System Prototype Based on CCSDS Standards

Deep space missions beyond earth orbit will require new methods of data communications in order to compensate for increasing RF propagation delay. The Consultative Committee for Space Data Systems (CCSDS) standard protocols Spacecraft Monitor & Control (SM&C), Asynchronous Message Service (AMS), and Delay/Disruption Tolerant Networking (DTN) provide such a method. The maturity level of this protocol set is, however, insufficient for mission inclusion at this time. This prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of these protocols..

Rich, Thomas M.

A Multi-Center Space Data System Prototype Based on CCSDS Standards

Deep space missions beyond earth orbit will require new methods of data communications in order to compensate for increasing Radio Frequency (RF) propagation delay. The Consultative Committee for Space Data Systems (CCSDS) standard protocols Spacecraft Monitor & Control (SM&C), Asynchronous Message Service (AMS), and Delay/Disruption Tolerant Networking (DTN) provide such a method. However, the maturity level of this protocol stack is insufficient for mission inclusion at this time. This Space Data System prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of this protocol set. In order to reduce costs, future missions can take advantage of these standard protocols, which will result in increased interoperability between control centers. This prototype demonstrates these capabilities by implementing a realistic space data system in which telemetry is published to control center applications at the Jet Propulsion Lab (JPL), the Marshall Space Flight Center (MSFC), and the Johnson Space Center (JSC). Reverse publishing paths for commanding from each control center are also implemented. The target vehicle consists of realistic flight computer hardware running Core Flight Software (CFS) in the integrated Power, Avionics, and Power (iPAS) Pathfinder Lab at JSC. This prototype demonstrates a potential upgrade path for future Deep Space Network (DSN) modification, in which the automatic error recovery and communication gap compensation capabilities of DTN would be exploited. In addition, SM&C provides architectural flexibility by allowing new service providers and consumers to be added efficiently anywhere in the network using the common interface provided by SM&C's Message Abstraction Layer (MAL). In FY 2015, this space data system was enhanced by adding telerobotic operations capability provided by the Robot API Delegate (RAPID) family of protocols developed at NASA. RAPID is one of several candidates for consideration and inclusion in a new international standard being developed by the CCSDS Telerobotic Operations Working Group. Software gateways for the purpose of interfacing RAPID messages with the existing SM&C based infrastructure were developed. Telerobotic monitor, control, and bridge applications were written in the RAPID framework, which were then tailored to the NAO telerobotic test article hardware, a product of Aldebaran Robotics.

Rich, Thomas M.

Managing Complex Space Missions Like the James Webb Space Telescope

Program Management Summary; Organizational structure is established. Roles and responsibilities are well defined: a) All major contracts are in place. b) All foreign partners are in place, operating under signed Memoranda of Understanding (MOUs). c) Partners include GSFC, NGST, Ball, ITT, ATK, STScI, ESA, CSA, UAz, LM, JPL, MSFC, ARC, JSC, etc. All enabling technologies are at Technical Readiness Level-6. Earned Value Management is being applied to all major contracts consistent with Agency guidance. Schedules are baselined and the project critical path is understood/managed. Budget with reserves established. Liens and threats system in use. Formal Configuration Management (CM) processes are in place. Project-level schedules are maintained within the CM system. Formal Risk Management processes are in place. Requirements are stable and flowed down. Project metrics are established and tracked monthly: a) Includes technical as well as cost and schedule metrics. b) Changes as well as trends are reported each month.

Sabelhaus, Phil