Search NASA⌕ Search

SEARCH · Search NASA

Results for “CONTRACT MANAGEMENT”

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 199 records · Page 11

Managing Requirements-Documents to Data

Managing Requirements on long term projects like International Space Station (ISS) can go thru many phases, from initial product development to almost over 20 years of operations and sustainment. Over that time many authorized changes have been made to the requirement set, that apply to any new systems that would visit the ISS today, like commercial cargo/crew vehicles or payloads. Explore the benefits of managing requirements in a database while satisfying traditional documents needs for contracts and stakeholder/user consumption that are not tied into the database.

Orr, Kevin↗

High-Performance Spaceflight Computing (HPSC) Middleware Overview

High Performance Spacecraft Computing (HPSC) is a joint project between the National Aeronautics and Space Administration (NASA) and Air Force Research Lab (AFRL) to develop a high-performance multi-core radiation hardened flight processor. HPSC offers a new flight computing architecture to meet the needs of NASA missions through 2030 and beyond. Providing on the order of 100X the computational capacity of current flight processors for the same amount of power, the multicore architecture of the HPSC processor, or "Chiplet" provides unprecedented flexibility in a flight computing system by enabling the operating point to be set dynamically, trading among needs for computational performance, energy management and fault tolerance. The HPSC Chiplet is being developed by Boeing under contract to NASA, and is expected to provide prototypes in 2021. The HPSC Chiplet prototypes will be delivered with an evaluation board, system emulators, comprehensive system software, and a software development kit. In addition to the vendor deliverables, the AFRL is funding the development of a flexible Middleware to be developed by NASA Jet Propulsion Laboratory and NASA Goddard Space Flight Center. The HPSC Middleware provides a suite of thirteen high level services to manage the compute, memory and I/O resources of this complex device.This presentation will provide an overview of the HPSC project, including a hardware overview, system software overview, Middleware overview, and mission use cases. The hardware overview will provide a look at the 8 core High Performance Processing Subsystem (HPPS), the Real Time Processing Subsystem (RTPS), the Chiplet Configuration Management Subsystem, on chip peripherals, and high speed I/O. The system software overview will introduce the boot loaders, operating systems, device drivers, and software development environment. The Middleware overview will provide insight into the high-level services that will be provided to help mission developers manage the many resources and configurations made possible with the Chiplet. Finally, the presentation will provide a brief look at the mission use cases that can be enabled with this next generation architecture.

middleware↗

Software engineering project management - A state-of-the-art report

The management of software engineering projects in the aerospace industry was investigated. The survey assessed such features as contract type, specification preparation techniques, software documentation required by customers, planning and cost-estimating, quality control, the use of advanced program practices, software tools and test procedures, the education levels of project managers, programmers and analysts, work assignment, automatic software monitoring capabilities, design and coding reviews, production times, success rates, and organizational structure of the projects.

Thayer, R. H.↗

Integrating NASA's Land Analysis System (LAS) image processing software with an appropriate Geographic Information System (GIS): A review of candidates in the public domain

A user requirements analysis (URA) was undertaken to determine and appropriate public domain Geographic Information System (GIS) software package for potential integration with NASA's LAS (Land Analysis System) 5.0 image processing system. The necessity for a public domain system was underscored due to the perceived need for source code access and flexibility in tailoring the GIS system to the needs of a heterogenous group of end-users, and to specific constraints imposed by LAS and its user interface, Transportable Applications Executive (TAE). Subsequently, a review was conducted of a variety of public domain GIS candidates, including GRASS 3.0, MOSS, IEMIS, and two university-based packages, IDRISI and KBGIS. The review method was a modified version of the GIS evaluation process, development by the Federal Interagency Coordinating Committee on Digital Cartography. One IEMIS-derivative product, the ALBE (AirLand Battlefield Environment) GIS, emerged as the most promising candidate for integration with LAS. IEMIS (Integrated Emergency Management Information System) was developed by the Federal Emergency Management Agency (FEMA). ALBE GIS is currently under development at the Pacific Northwest Laboratory under contract with the U.S. Army Corps of Engineers' Engineering Topographic Laboratory (ETL). Accordingly, recommendations are offered with respect to a potential LAS/ALBE GIS linkage and with respect to further system enhancements, including coordination with the development of the Spatial Analysis and Modeling System (SAMS) GIS in Goddard's IDM (Intelligent Data Management) developments in Goddard's National Space Science Data Center.

Rochon, Gilbert L.↗

Integrated Baseline Review (IBR) Handbook

The purpose of this handbook is intended to be a how-to guide to prepare for, conduct, and close-out an Integrated Baseline Review (IBR). It discusses the steps that should be considered, describes roles and responsibilities, tips for tailoring the IBR based on risk, cost, and need for management insight, and provides lessons learned from past IBRs. Appendices contain example documentation typically used in connection with an IBR. Note that these appendices are examples only, and should be tailored to meet the needs of individual projects and contracts.

Project↗

Micro Machining Enhances Precision Fabrication

Advanced thermal systems developed for the Space Station Freedom project are now in use on the International Space Station. These thermal systems employ evaporative ammonia as their coolant, and though they employ the same series of chemical reactions as terrestrial refrigerators, the space-bound coolers are significantly smaller. Two Small Business Innovation Research (SBIR) contracts between Creare Inc. of Hanover, NH and Johnson Space Center developed an ammonia evaporator for thermal management systems aboard Freedom. The principal investigator for Creare Inc., formed Mikros Technologies Inc. to commercialize the work. Mikros Technologies then developed an advanced form of micro-electrical discharge machining (micro-EDM) to make tiny holes in the ammonia evaporator. Mikros Technologies has had great success applying this method to the fabrication of micro-nozzle array systems for industrial ink jet printing systems. The company is currently the world leader in fabrication of stainless steel micro-nozzles for this market, and in 2001 the company was awarded two SBIR research contracts from Goddard Space Flight Center to advance micro-fabrication and high-performance thermal management technologies.

Source record↗

Procurement evaluation

Procurement process for evaluating logistics performance, and incentive features in support contracts

CONTRACTOR↗

Space Transportation System Technology Symposium: Operations, Maintenance, and Safety (Including Cryogenic Systems) - Volume 5

The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OART and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.

Source record↗

Space Transportation System Technology Symposium: Propulsion - Volume 4

The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OAR T and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.

Source record↗

Space Transportation System Technology Symposium: Biotechnology - Volume 7

The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OART and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.

Source record↗

Distributed Virtual System (DIVIRS) Project

As outlined in our continuation proposal 92-ISI-50R (revised) on contract NCC 2-539, we are (1) developing software, including a system manager and a job manager, that will manage available resources and that will enable programmers to program parallel applications in terms of a virtual configuration of processors, hiding the mapping to physical nodes; (2) developing communications routines that support the abstractions implemented in item one; (3) continuing the development of file and information systems based on the virtual system model; and (4) incorporating appropriate security measures to allow the mechanisms developed in items 1 through 3 to be used on an open network. The goal throughout our work is to provide a uniform model that can be applied to both parallel and distributed systems. We believe that multiprocessor systems should exist in the context of distributed systems, allowing them to be more easily shared by those that need them. Our work provides the mechanisms through which nodes on multiprocessors are allocated to jobs running within the distributed system and the mechanisms through which files needed by those jobs can be located and accessed.

Schorr, Herbert↗

User interface to administrative DRMS within a distributed environment

The implementation of a data base management system (DBMS) into a communications office to control and report on communication leased service contracts is discussed. The system user executes online programs to update five files residing on a UNIVAC 1100/82, through the forms mode features of the Tektronix 4025 terminal and IMSAI 8080 microcomputer. This user can select the appropriate form to the Tektronix 4025 screen, and enter new data, update existing data, or discontinue service. Selective online printing of 40 reports is accomplished by the system user to satisfy management, budget, and bill payment reporting requirements.

Martin, L. D.↗

Earned Value Management (EVM): Reference Guide for Project-Control Account Managers

The purpose of this guide is intended to be a quick reference for a Project-Control Account Manager (P CAM) or technical manager empowered with a project’s cost, schedule, and technical responsibilities of a control account(s) when Earned Value Management (EVM) is required. The overall objective is to support the P CAM in performing their responsibilities as they relate to EVM. In addition, the reference guide describes at a summary level how the scope, schedule, and budget of a project integrate for optimal planning and control of prime contracts and in-house projects.

Control Account Manager↗

Integrated water and waste management system for future spacecraft

Over 200 days of continuous testing have been completed on an integrated waste management-water recovery system developed by General Electric under a jointly funded AEC/NASA/AF Contract. The 4 man system provides urine, feces, and trash collection; water reclamation; storage, heating and dispensing of the water; storage and disposal of the feces and urine residue and all of other nonmetallic waste material by incineration. The heat required for the 1200 deg F purification processes is provided by a single 420-w radioisotope heater. A second 836-w radioisotope heater supplemented by 720 w of electrical heat provides for distillation and water heating. Significant test results are no pre-or-post treatment, greater than 98 per cent potable water recovery, approximately 95 per cent reduction in solids weight and volume, all outflows are sterile with the water having no bacteria or virus, and the radioisotope capsule radiation level is only 7.9 mrem/hr unshielded at 1 m (neutrons and gamma).

Ingelfinger, A. L.↗

GCS plan for software aspects of certification

As part of the Guidance and Control Software (GCS) research project being sponsored by NASA to evaluate the failure processes of software, standard industry software development procedures are being employed. To ensure that these procedures are authentic, the guidelines outlined in the Radio Technical Commission for Aeronautics (RTCA/DO-178A document entitled, software considerations in airborne systems and equipment certification, were adopted. A major aspect of these guidelines is proper documentation. As such, this report, the plan for software aspects of certification, was produced in accordance with DO-178A. An overview is given of the GCS research project, including the goals of the project, project organization, and project schedules. It also specifies the plans for all aspects of the project which relate to the certification of the GCS implementations developed under a NASA contract. These plans include decisions made regarding the software specification, accuracy requirements, configuration management, implementation development and verification, and the development of the GCS simulator.

Shagnea, Anita M.↗

Applied Meteorology Unit - Operational Contributions to Spaceport Canaveral

The Applied Meteorology Unit (AMU) provides technology development, evaluation and transition services to improve operational weather support to the Space Shuttle and the National Space Program. It is established under a Memorandum of Understanding among NASA, the Air Force and the National .Weather Service (NWS). The AMU is funded and managed by NASA and operated by ENSCO, Inc. through a competitively awarded NASA contract. The primary customers are the 45th Weather Squadron (45WS) at Cape Canaveral Air Force Station (CCAFS), FL; the Spaceflight Meteorology Group (SMG) at Johnson Space Center (JSC) in Houston, TX; and the NWS office in Melbourne, FL (NWS MLB). This paper will briefly review the AMU's history and describe the three processes through which its work is assigned. Since its inception in 1991 the AMU has completed 72 projects, all of which are listed at the end of this paper. At least one project that highlights each of the three tasking processes will be briefly reviewed. Some of the projects that have been especially beneficial to the space program will also be discussed in more detail, as will projects that developed significant new techniques or science in applied meteorology.

Bauman, William H., III↗

Methods of Increasing Terminal Airspace Flexibility and Control Authority

The focus of the NRA contract is to develop a What-if Analysis Tool for planning Departure Management Programs (DMP) at airports. This final report summarizes the work conducted throughout the base year, with a focus on use case specification for the what-if analysis capability and the implementation of the What-if Analysis Tool and its application to traffic and weather scenarios at Charlotte Douglas International Airport (CLT).

NRA Final Report↗