SEARCH · Search NASA
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.
Technical and management problems associated with the evaluation, selection, installation, and use of data base management system packages in the NASA administrative support environment are examined.
The goal of the Unmanned Aircraft System (UAS) Traffic Management (UTM) effort at NASA is to enable access to low-altitude airspace for small UAS. This goal is being achieved partly through partnerships that NASA has developed with the FAA, other government agencies, the UAS stakeholder community, and the designated FAA UAS Test Sites. This paper reports the technical and operational capabilities demonstrated during the UTM flight demonstration, March 6 through May 30, 2018. The demonstration featured geographically diverse operations, involving FAA UAS Test Sites in Alaska, Nevada, New York, North Dakota, Texas and Virginia. The demonstration leveraged the contributions of 30 partner organizations serving as UAS service suppliers, UAS operators, and/or providers of sensors, surveillance, connectivity, and management roles. Utilizing the UTM architecture developed at NASA, the demonstration explored 11 use cases for small UAS operations to highlight UTM capabilities at what NASA calls “Technical Capability Level (TCL) 3.” TCL 3 is characterized by multiple small UAS safely operating in moderately populated areas and beyond the visual line of sight of their operators. The TCL 3 flights demonstrated the basic feasibility of such operations in the UTM environment, including USS exchanges; communication, navigation and surveillance functions; sense and avoid capabilities; and technologies and procedures to enable them.
The Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 (FAM 2.0), is a discrete event simulation model designed to support analysis of alternative concepts in air traffic management and control. FAM 2.0 was developed by the Logistics Management Institute (LMI) under a National Aeronautics and Space Administration (NASA) contract. This document provides a technical description of FAM 2.0 and its computer files to enable the modeler and programmer to make enhancements or modifications to the model. Those interested in a guide for using the model in analysis should consult the companion document, Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 Users Manual.
The Johnson Space Center s (JSC) International Space Station (ISS) Space Flight Resource Management (SFRM) training program is designed to teach the team skills required to be an effective flight controller. It was adapted from the SFRM training given to Shuttle flight controllers to fit the needs of a "24 hours a day/365 days a year" flight controller. More recently, the length reduction of technical training flows for ISS flight controllers impacted the number of opportunities for fully integrated team scenario based training, where most SFRM training occurred. Thus, the ISS SFRM training program is evolving yet again, using a new approach of teaching and evaluating SFRM alongside of technical materials. Because there are very few models in other industries that have successfully tied team and technical skills together, challenges are arising. Despite this, the Mission Operations Directorate of NASA s JSC is committed to implementing this integrated training approach because of the anticipated benefits.
The SmartGrid Advanced Load Management & Optimized Neighborhood (SALMON) project aimed to demonstrate and document the value of Distributed Energy Resources (DERs) as a grid resource for both bulk system and distribution operations.
Research and education in management of large scale technical programs - education and integration of interdisciplinary team
Since 2003, AIAA's Computer Systems and Software Systems Technical Committees (TCs) have developed a database that aids technical committee management to map technical topics to their members. This Topics/Interest (T/I) database grew out of a collection of charts and spreadsheets maintained by the TCs. Since its inception, the tool has evolved into a multi-dimensional database whose dimensions include the importance, interest and expertise of TC members and whether or not a member and/or a TC is actively involved with the topic. In 2005, the database was expanded to include the TCs in AIAA s Information Systems Group and then expanded further to include all AIAA TCs. It was field tested at an AIAA Technical Activities Committee (TAC) Workshop in early 2006 through live access by over 80 users. Through the use of the topics database, TC and program committee (PC) members can accomplish relevant tasks such as: to identify topic experts (for Aerospace America articles or external contacts), to determine the interest of its members, to identify overlapping topics between diverse TCs and PCs, to guide new member drives and to reveal emerging topics. This paper will describe the origins, inception, initial development, field test and current version of the tool as well as elucidate the benefits and insights gained by using the database to aid the management of various TC functions. Suggestions will be provided to guide future development of the database for the purpose of providing dynamics and system level benefits to AIAA that currently do not exist in any technical organization.
The photovoltaic solar panels on the International Space Station (ISS) track the Sun through continuous rotating motion enabled by large bearings on the main truss called solar array alpha rotary joints (SARJs). In late 2007, shortly after installation, the starboard SARJ had become hard to turn and had to be shut down after exceeding drive current safety limits. The port SARJ, of the same design, had been working well for over 2 years. An exhaustive failure investigation ensued that included multiple extravehicular activities to collect information and samples for engineering forensics, detailed structural and thermal analyses, and a careful review of the build records. The ultimate root cause was determined to be kinematic design vulnerability coupled with inadequate lubrication, and manufacturing flaws; this was corroborated through ground tests, metallurgical studies, and modeling. A highly successful recovery plan was developed and implemented that included replacing worn and damaged components in orbit and applying space-compatible grease to improve lubrication. Beyond the technical aspects, however, lie several key programmatic lessons learned. These lessons, such as running ground tests to intentional failure to experimentally verify failure modes, are reviewed and discussed so they can be applied to future projects to avoid such problems.
Pilot test evaluation of microelectronics data bank response to operational communication
Total Reuse Management (TRM) is a new concept currently being promoted by the NASA Langley Software Engineering and Ada Lab (SEAL). It uses concepts similar to those promoted in Total Quality Management (TQM). Both technical and management personnel are continually encouraged to think in terms of reuse. Reuse is not something that is aimed for after a product is completed, but rather it is built into the product from inception through development. Lowering software development costs, reducing risk, and increasing code reliability are the more prominent goals of TRM. Procedures and methods used to adopt and apply TRM are described. Reuse is frequently thought of as only being applicable to code. However, reuse can apply to all products and all phases of the software life cycle. These products include management and quality assurance plans, designs, and testing procedures. Specific examples of successfully reused products are given and future goals are discussed.
Technical Requirements Analysis and Control Systems/Initial Operating Capability (TRACS/IOC) computer program provides supplemental software tools for analysis, control, and interchange of project requirements so qualified project members have access to pertinent project information, even if in different locations. Enables users to analyze and control requirements, serves as focal point for project requirements, and integrates system supporting efficient and consistent operations. TRACS/IOC is HyperCard stack for use on Macintosh computers running HyperCard 1.2 or later and Oracle 1.2 or later.
No abstract available
No abstract available
Management and maintenance of engineering staff during retrenchment of space program
Design concepts, management philosophy and program highlights of research toward Voyager spacecraft development
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.
Engineering management, discussing technical men work effort, time/intellectual changes, performance measurements, motivational factors and relationship to company
The United States (US) Vision for Space Exploration, announced in January 2004, outlines the National Aeronautics and Space Administration's (NASA) strategic goals and objectives, including retiring the Space Shuttle and replacing it with new space transportation systems for missions to the Moon, Mars, and beyond. The Crew Exploration Vehicle (CEV) that the new human-rated Crew Launch Vehicle (CLV) lofts into space early next decade will initially ferry astronauts to the International Space Station (ISS) Toward the end of the next decade, a heavy-lift Cargo Launch Vehicle (CaLV) will deliver the Earth Departure Stage (EDS) carrying the Lunar Surface Access Module (LSAM) to low-Earth orbit (LEO), where it will rendezvous with the CEV launched on the CLV and return astronauts to the Moon for the first time in over 30 years. This paper outlines how NASA is building these new space transportation systems on a foundation of legacy technical and management knowledge, using extensive experience gained from past and ongoing launch vehicle programs to maximize its design and development approach, with the objective of reducing total life cycle costs through operational efficiencies such as hardware commonality. For example, the CLV in-line configuration is composed of a 5-segment Reusable Solid Rocket Booster (RSRB), which is an upgrade of the current Space Shuttle 4- segment RSRB, and a new upper stage powered by the liquid oxygen/liquid hydrogen (LOX/LH2) J-2X engine, which is an evolution of the J-2 engine that powered the Apollo Program s Saturn V second and third stages in the 1960s and 1970s. The CaLV configuration consists of a propulsion system composed of two 5-segment RSRBs and a 33- foot core stage that will provide the LOX/LED needed for five commercially available RS-68 main engines. The J-2X also will power the EDS. The Exploration Launch Projects, managed by the Exploration Launch Office located at NASA's Marshall Space Flight Center, is leading the design, development, testing, and operations planning for these new space transportation systems. Utilizing a foundation of heritage hardware and management lessons learned mitigates both technical and programmatic risk. Project engineers and managers work closely with the Space Shuttle Program to transition hardware, infrastructure, and workforce assets to the new launch systems, leveraging a wealth of knowledge from Shuffle operations. In addition, NASA and its industry partners have tapped into valuable Apollo databases and are applying corporate wisdom conveyed firsthand by Apollo-era veterans of America s original Moon missions. Learning from its successes and failures, NASA employs rigorous systems engineering and systems management processes and principles in a disciplined, integrated fashion to further improve the probability of mission success.