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
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Earned Value Management (EVM) Implementation Handbook

The purpose of this handbook is to provide Earned Value Management (EVM) guidance for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts and subcontracts in a consolidated reference document. EVM is a project management process that effectively integrates a project s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical problems as well as the intended course and success of corrective actions.

Source record↗
NASA NTRS2018

Earned Value Management (EVM) Implementation Handbook

The purpose of this handbook is to provide Earned Value Management (EVM) guidance for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts and subcontracts in a consolidated reference document. EVM is a project management process that effectively integrates a project?s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical problems as well as the intended course and success of corrective actions.

Planning Package↗
DOE OSTI2023

The Design and Implementation of a Secure Datastore Based on Ethereum Smart Contract

In this paper, we present a secure datastore based on an Ethereum smart contract. Our research is guided by three research questions. First, we will explore to what extend a smart-contract-based datastore should resemble a traditional database system. Second, we will investigate how to store the data in a smart-contract-based datastore for maximum flexibility while minimizing the gas consumption. Third, we seek answers regarding whether or not a smart-contract-based datastore should incorporate complex processing such as data encryption and data analytic algorithms. The proposed smart-contract-based datastore aims to strike a good balance between several constraints: (1) smart contracts are publicly visible, which may create a confidentiality concern for the data stored in the datastore; (2) unlike traditional database systems, the Ethereum smart contract programming language (i.e., Solidity) offers very limited data structures for data management; (3) all operations that mutate the blockchain state would incur financial costs and the developers for smart contracts must make sure sufficient gas is provisioned for every smart contract call, and ideally, the gas consumption should be minimized. Our investigation shows that although it is essential for a smart-contract-based datastore to offer some basic data query functionality, it is impractical to offer query flexibility that resembles that of a traditional database system. Furthermore, we propose that data should be structured as tag-value pairs, where the tag serves as a non-unique key that describes the nature of the value. We also conclude that complex processing should not be allowed in the smart contract due to the financial burden and security concerns. The tag-based secure datastore designed this way also defines its applicative perimeter, i.e., only applications that align with our strategy would find the proposed datastore a good fit. Those that would rather incur higher financial cost for more data query flexibility and/or less user burden on data pre- and post-processing would find the proposed database too restrictive.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRS1974

Apollo/Skylab suit program management systems study. Volume 2: Cost analysis

The business management methods employed in the performance of the Apollo-Skylab Suit Program are studied. The data accumulated over the span of the contract as well as the methods used to accumulate the data are examined. Management methods associated with the monitoring and control of resources applied towards the performance of the contract are also studied and recommended upon. The primary objective is the compilation, analysis, and presentation of historical cost performance criteria. Cost data are depicted for all phases of the Apollo-Skylab program in common, meaningful terms, whereby the data may be applicable to future suit program planning efforts.

Source record↗
NASA NTRS1998

Aircraft/Air Traffic Management Functional Analysis Model: User's Guide - Version 2.0

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) a National Aeronautics and Space Administration (NASA) contract. This document provides a guide for using the model in analysis. Those interested in making enhancements or modification to the model should consult the companion document, Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 Technical Description.

Etheridge, Melvin↗
NASA NTRS2021

Earned Value Management (EVM) Implementation Handbook

The purpose of this handbook is to provide EVM guidance for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts, and subcontracts in a consolidated reference document. EVM is a project management process that effectively integrates a project’s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical, cost and schedule problems as well as the intended course and success of corrective actions.

Christopher Lewis Sadler↗
NASA NTRS2017

An Analysis of the Speed Commands from an Interval Management Algorithm during the ATD-1 Flight Test

NASA's first Air Traffic Management Technology Demonstration (ATD-1) successfully completed a nineteen-day flight test under a NASA contract with Boeing, with Honeywell and United Airlines as sub-contractors. An Interval Management (IM) avionics prototype was built based on international IM standards, integrated into two test aircraft, and then flown in real-world conditions to determine if the goals of improving aircraft efficiency and airport throughput during high-density arrival operations could be met. This paper describes the speed behavior of the IM avionics prototype, focusing on the speed command rate and the number of speed increases.

Watters, Christine↗
DOE OSTI2020

UESC Overview and FEMP Resources for Project Success

The first part of this webinar provides an introduction to utility energy service contracts (UESCs) and describes the features and benefits of utilizing UESCs to install energy conservation measures at federal sites. The second part introduces the newly launched UESC On-Demand Training Series and other recently published FEMP resources. The modular series of short webinars has been designed to provide in-depth understanding of UESCs and is a great resource for federal agencies and utilities interested in UESC projects.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗
NASA NTRS2010

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↗
NASA NTRS2004

Data Management as a Cluster Middleware Centerpiece

Through earth and space modeling and the ongoing launches of satellites to gather data, NASA has become one of the largest producers of data in the world. These large data sets necessitated the creation of a Data Management System (DMS) to assist both the users and the administrators of the data. Halcyon Systems Inc. was contracted by the NASA Center for Computational Sciences (NCCS) to produce a Data Management System. The prototype of the DMS was produced by Halcyon Systems Inc. (Halcyon) for the Global Modeling and Assimilation Office (GMAO). The system, which was implemented and deployed within a relatively short period of time, has proven to be highly reliable and deployable. Following the prototype deployment, Halcyon was contacted by the NCCS to produce a production DMS version for their user community. The system is composed of several existing open source or government-sponsored components such as the San Diego Supercomputer Center s (SDSC) Storage Resource Broker (SRB), the Distributed Oceanographic Data System (DODS), and other components. Since Data Management is one of the foremost problems in cluster computing, the final package not only extends its capabilities as a Data Management System, but also to a cluster management system. This Cluster/Data Management System (CDMS) can be envisioned as the integration of existing packages.

Zero, Jose↗
NASA NTRS1989

Electrical, Electronic, and Electromechanical (EEE) parts management and control requirements for NASA space flight programs

This document establishes electrical, electronic, and electromechanical (EEE) parts management and control requirements for contractors providing and maintaining space flight and mission-essential or critical ground support equipment for NASA space flight programs. Although the text is worded 'the contractor shall,' the requirements are also to be used by NASA Headquarters and field installations for developing program/project parts management and control requirements for in-house and contracted efforts. This document places increased emphasis on parts programs to ensure that reliability and quality are considered through adequate consideration of the selection, control, and application of parts. It is the intent of this document to identify disciplines that can be implemented to obtain reliable parts which meet mission needs. The parts management and control requirements described in this document are to be selectively applied, based on equipment class and mission needs. Individual equipment needs should be evaluated to determine the extent to which each requirement should be implemented on a procurement. Utilization of this document does not preclude the usage of other documents. The entire process of developing and implementing requirements is referred to as 'tailoring' the program for a specific project. Some factors that should be considered in this tailoring process include program phase, equipment category and criticality, equipment complexity, and mission requirements. Parts management and control requirements advocated by this document directly support the concept of 'reliability by design' and are an integral part of system reliability and maintainability. Achieving the required availability and mission success objectives during operation depends on the attention given reliability and maintainability in the design phase. Consequently, it is intended that the requirements described in this document are consistent with those of NASA publications, 'Reliability Program Requirements for Aeronautical and Space System Contractors,' NHB 5300.4(1A-l); 'Maintainability Program Requirements for Space Systems,' NHB 5300.4(1E); and 'Quality Program Provisions for Aeronautical and Space System Contractors,' NHB 5300.4(1B).

Source record↗
NASA NTRS2012

Hierarchthis: An Interactive Interface for Identifying Mission-Relevant Components of the Advanced Multi-Mission Operations System

Even though NASA's space missions are many and varied, there are some tasks that are common to all of them. For example, all spacecraft need to communicate with other entities, and all spacecraft need to know where they are. These tasks use tools and services that can be inherited and reused between missions, reducing systems engineering effort and therefore reducing cost.The Advanced Multi-Mission Operations System, or AMMOS, is a collection of multimission tools and services, whose development and maintenance are funded by NASA. I created HierarchThis, a plugin designed to provide an interactive interface to help customers identify mission-relevant tools and services. HierarchThis automatically creates diagrams of the AMMOS database, and then allows users to show/hide specific details through a graphical interface. Once customers identify tools and services they want for a specific mission, HierarchThis can automatically generate a contract between the Multimission Ground Systems and Services Office, which manages AMMOS, and the customer. The document contains the selected AMMOS components, along with their capabilities and satisfied requirements. HierarchThis reduces the time needed for the process from service selections to having a mission-specific contract from the order of days to the order of minutes.

Advanced Multi-Mission Operations System (AMMOS)↗
NASA NTRS2008

Engine Validation of Noise and Emission Reduction Technology Phase I

This final report has been prepared by Honeywell Aerospace, Phoenix, Arizona, a unit of Honeywell International, Inc., documenting work performed during the period December 2004 through August 2007 for the NASA Glenn Research Center, Cleveland, Ohio, under the Revolutionary Aero-Space Engine Research (RASER) Program, Contract No. NAS3-01136, Task Order 8, Engine Validation of Noise and Emission Reduction Technology Phase I. The NASA Task Manager was Dr. Joe Grady of the NASA Glenn Research Center. The NASA Contract Officer was Mr. Albert Spence of the NASA Glenn Research Center. This report is for a test program in which NASA funded engine validations of integrated technologies that reduce aircraft engine noise. These technologies address the reduction of engine fan and jet noise, and noise associated with propulsion/airframe integration. The results of these tests will be used by NASA to identify the engineering tradeoffs associated with the technologies that are needed to enable advanced engine systems to meet stringent goals for the reduction of noise. The objectives of this program are to (1) conduct system engineering and integration efforts to define the engine test-bed configuration; (2) develop selected noise reduction technologies to a technical maturity sufficient to enable engine testing and validation of those technologies in the FY06-07 time frame; (3) conduct engine tests designed to gain insight into the sources, mechanisms and characteristics of noise in the engines; and (4) establish baseline engine noise measurements for subsequent use in the evaluation of noise reduction.

Weir, Don↗
NASA NTRS1982

Assessment of MSFC's supervisory training programs and courses

Courses and special programs to train supervisors at Marshall Space Flight Center (MSFC) were to determine the adequacy of the present MSFC Supervisory Training Program and to recommend changes, if appropriate. The content, procedures, and student evaluations of the required Office of Personnel Management (OPM) 80 hours training for supervisors, the optional 120 hours, the MSFC Management Development Program (MDP), NASA's Management Education Program (MEP), various OPM and special contract programs, pertinent procedural guidelines, regulations, and letters, as well as various MSFC computer reports which indicate who took what training were analyzed. Various interviews with MSFC personnel involved in training are included. Recommendations consist of: (1) the choice of courses selected for the basic required OPM 80 hours be improved; (2) the optional 120 hours be discontinued and a shorter module be developed dealing with managerial decision making and human relations skills; (3) the MDP and MEP be continued as at present; and (4) that a broad array of developmental strategies be incorporated to provide a variety of opportunities for supervisory improvement.

Brindley, T. A.↗
NASA NTRS1986

International ultraviolet explorer observatory operations

This volume contains the Final Report for the International Ultraviolet Explorer (IUE) Observatory Operations contract, NAS5-28787. The report summarizes the activities of the IUE Observatory over the 13-month period from November 1985 through November 1986 and is arranged in sections according to the functions specified in the Statement of Work (SOW) of the contract. In order to preserve numerical correspondence between the technical SOW elements specified by the contract and the sections of this report, project management activities (SOW element 0.0.) are reported here in Section 7, following the reports of technical SOW elements 1.0 through 6.0. Routine activities have been summarized briefly whenever possible; statistical compilations, reports, and more lengthy supplementary material are contained in the Appendices.

Source record↗
NASA NTRS1989

The Fifth Annual NASA/Contractors Conference on Quality and Productivity. Quality: A Commitment to the Future

The report is a summary of the 5th NASA/Contractors Conference on Quality and Productivity. The theme was 'Quality - A Commitment to the Future'. The summary report highlights the key points: commitment to quality, strategic and long-range planning, quality commitment, risk management, teaming, quality measurement, creating a quality environment, contract incentives, software quality and reliability.

Source record↗
NASA NTRS2009

From Research to Flight: Surviving the TRL Valley of Death for Robotic and Human Space Exploration

There must be a plan or opportunities for flight validation: a) To reduce the bottleneck of new technologies at the TRL Valley of Death; b) To allow frequent infusion of new technologies into flight missions. Risk must be tolerated for new technology flight experiments. Risk must also be accepted on early-adopting missions to enable new capabilities. Fundamental research is critical to taking the next giant leap in the scientific exploration of space. Technology push is often required to meet current mission requirements. Technology management requires more than issuing NRAs and overseeing contracts.

Johnson, Les↗