Search NASA⌕ Search

SEARCH · Search NASA

Results for “technical 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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

State Technical Assistance - New Mexico Energy and Conservation Management Division Report [Slides]

The New Mexico Energy and Conservation Management Division (ECMD) sought technical assistance to enhance their ability to evaluate program impacts using the Low-Income Energy Affordability Data (LEAD) tool. NLR assisted ECMD in leveraging the LEAD tool to calculate and analyze energy burden across electric utility service areas, enabling them to assess program outcomes more effectively. To meet ECMD's goals, NLR developed a customized methodology to calculate utility-specific energy burden metrics using census tract data and available utility service area information from the Energy Information Administration (EIA). While acknowledging some limitations in the EIA dataset, NLR estimated the percentage of households within each service territory and incorporated relevant filters such as income, housing characteristics, and other demographics from the LEAD tool. The analysis provided ECMD with a new capability to evaluate program success based on energy savings, reductions in energy burden, and other performance indicators. The data and methodology also support discussions with utilities to improve the accuracy of service territory datasets. ECMD can use the outputs to track program effectiveness and plan future initiatives. NLR offered the possibility of follow-on work, including capacity-building for ECMD to repeat the analysis independently and the option to refine the analysis with updated service.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
NASA NTRS2017

Extension of MBSE for Project Programmatics Management on the Asteroid Redirect Robotic Mission

Model-based Systems Engineering can be employed beyond management of the technical architecture development of a system to also manage the programmatics associated with Systems Engineering activities of a project. On NASA’s Asteroid Redirect Robotic Mission, MBSE has been successfully employed to manage, generate, and interact with the documentation-based deliverables associated with System Engineering activities. This has been involved in defining and tracking project document, milestone, and personnel metadata via the same modeling framework used for the technical architecture management. Additionally, it has focused on improving overall user experiences through linkage of documentation to technical content in the system model, automation of manually intensive tasks, and others stakeholderoriented features.

Mozafari, Tanaz↗
NASA NTRS2005

Emerging Sealing Technologies Development

Under this Cooperative Agreement, the objective was to investigate several emerging sealing technologies of interest to the Mechanical Components Branch of National Aeronautics and Space Administration Glenn Research Center at Lewis Field (NASA GRC). The majority of the work conducted was to support the development of Solid Oxide Fuel Cells for application to aeronautic auxiliary power units, though technical investigations of interest to other groups and projects were also conducted. In general, accomplishments and results were periodically reported to the NASA Technical Monitor, the NASA GRC Seal Team staff, and NASA GRC project management. Several technical reports, journal articles, and presentations were given internally to NASA GRC and to the external public.

Source record↗
NASA NTRS2011

An Interview with Joe McMann: His Life Lessons

Pica Kahn conducted "An Interview with Joe McMann: His Life Lessons" on May 23, 2011. With over 40 years of experience in the aerospace industry, McMann has gained a wealth of knowledge. Many have been interested in his biography, progression of work at NASA, impact on the U.S. spacesuit, and career accomplishments. This interview highlighted the influences and decision-making methods that impacted his technical and management contributions to the space program. McMann shared information about the accomplishments and technical advances that committed individuals can make.

McMann, Joe↗
NASA NTRS1972

Report of the Tape Recorder Action Plan Committee, 21 March 1972

A NASA/AF Tape Recorder Action Plan Committee was formed in January 1972 to investigate tape recorder problems and to recommend an action plan to NASA management. The committee collected data on tape recorder failure history, pinpointed problem areas, discussed needed technical and management changes, and proposed an action plan for the recommended approaches.

Source record↗
NASA NTRS1992

Reducing the complexity of software systems - A strategic software perspective

The results of a combined management and technical initiative aimed at reducing the size and complexity associated with developing operations planning, scheduling, and resource management software systems are presented. The initiative has produced operations concepts, functional requirements, system architectures, a comprehensive lexicon, and software tools to revolutionize the traditional software technology and development practices for planning, scheduling, and resource management systems used in space operations control centers. Examples of technology and practices to reduce complexity include a method for projecting design consequences from an operations concept, a universal architecture for heuristic algorithms, an object-oriented framework for describing large classes of problems that parametrically adapt to all domain peculiarities, the identification of general approaches which respond to changes with minimum impact on systems implementations, and a management structure for prototyping to minimize the risks of ill-conceived designs.

Hornstein, Rhoda S.↗
NASA NTRS1983

Automation pilot

An important concept of the Action Information Management System (AIMS) approach is to evaluate office automation technology in the context of hands on use by technical program managers in the conduct of human acceptance difficulties which may accompany the transition to a significantly changing work environment. The improved productivity and communications which result from application of office automation technology are already well established for general office environments, but benefits unique to NASA are anticipated and these will be explored in detail.

Source record↗
NASA NTRS1989

Space station attached payload program support

The USRA is providing management and technical support for the peer review of the Space Station Freedom Attached Payload proposals. USRA is arranging for consultants to evaluate proposals, arranging meeting facilities for the reviewers to meet in Huntsville, Alabama and management of the actual review meetings. Assistance in developing an Experiment Requirements Data Base and Engineering/Technical Assessment support for the MSFC Technical Evaluation Team is also being provided. The results of the project will be coordinated into a consistent set of reviews and reports by USRA. The strengths and weaknesses analysis provided by the peer panel reviewers will by used NASA personnel in the selection of experiments for implementation on the Space Station Freedom.

Estes, Maurice G., Jr.↗
NASA NTRS2008

Best Practices for Researching and Documenting Lessons Learned

Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.

Goodman, John L.↗
NASA NTRS2010

Lessons Learned in Launching Ares I-X

The Ares I-X flight test, scheduled for 2009, is the first opportunity for the Constellation Program and Ares Projects to obtain important data on the in-flight loads, first stage recovery, and ground-handling characteristics of the Ares I crew launch vehicle. The flight test vehicle will incorporate a mix of flight and mockup hardware, reflecting an acceptable representation of the mass and outer mold line characteristics of the operational Ares I vehicle. It will be powered by a four-segment solid rocket motor from the Space Shuttle inventory and will include a fifth, inert spacer segment and new forward structures to make it the same shape as the Ares I first stage. The vehicle also includes mass simulators for the upper stage, Orion crew module, and launch abort system to match the outer mold line of Ares I; an active roll control system; and avionics derived from Shuttle and Atlas hardware. This suborbital mission will take the flight test vehicle from stacking in the Vehicle Assembly Building (VAB) at Kennedy Space Center (KSC) through liftoff, maximum dynamic pressure, first stage separation, and recovery. Ares I-X presented NASA with unique project management challenges. This presentation will address those unique challenges, including managing a virtual nationwide team under a constrained timeline; designing and building the launch vehicle and ground systems; working concurrently with Space Shuttle activities; and integrating technical and management functions. It also will identify key data collected and lessons learned from the flight that will be applied to future exploration missions.

Davis, Stephan R.↗
NASA NTRS2022

Aggregate Risk Tool for Human Space Flight

This tool utilizes Data fusion capabilities developed from the 2020-2022 Information Fusion (IFDA) IRAD to enhance functionality of a Human Spaceflight (HSF) Aggregate Risk Product developed by the JSC Flight Safety Office. The tool compiles and present risk data from multiple Program and Commercial Provider sources to provide a holistic assessment for Program Managers and Technical Authorities to evaluate residual risk prior to HSF Launches. The aggregation, or coupling of risks from multiple sources (Ex: PRA, variances, anomaly data bases, CRM data, technical review board minutes, Hazard Analysis, etc.) identifies areas of elevated risk in components, systems or mission phases that would otherwise be undetected by non-integrated program risk management tools and possesses. Data is then displayed in an interactive user interface/dashboard that enables users to see potential areas of concern requiring more in-depth analysis.

Patrick M Huckaby↗
NASA NTRS1980

Future integrated design process

The design process is one of the sources used to produce requirements for a computer system to integrate and manage product design data, program management information, and technical computation and engineering data management activities of the aerospace design process. Design activities were grouped chronologically and explored for activity type, activity interface, data quantity, and data flow. The work was based on analysis of the design process of several typical aerospace products, including both conventional and supersonic airplanes and a hydrofoil design. Activities examined included research, preliminary design, detail design, manufacturing interface, product verification, and product support. The design process was then described in an IPAD environment--the future.

Meyer, D. D.↗
NASA NTRS2012

Personal Background Interview of Jim McBarron

Jim McBarron exhibits a wealth of knowledge gathered from more than 40 years of experience with NASA, EVA, and spacesuits. His biography, progression of work at NASA, impact on EVA and the U.S. spacesuit, and career accomplishments are of interest to many. Wright, from the JSC History Office, conducted a personal background interview with McBarron. This interview highlighted the influences and decision-making methods that impacted McBarron's technical and management contributions to the space program. Attendees gained insight on the external and internal NASA influences on career progression within the EVA and spacesuit, and the type of accomplishments and technical advances that committed individuals can make. He concluded the presentation with a question and answer period that included a brief discussion about close calls and Russian spacesuits.

McBarron, Jim↗
NASA NTRSDate not supplied

Lessons Learned from NASA Goddard Space Flight Center’s Product Development Lead Training Schedule and Cost Development Workshop: Continuous Improvement

This presentation provides a status of the Goddard Space Flight Center (GSFC) effort to increase foundational knowledge of Product Development Leads (PDLs) in schedule and cost management including earned value management (EVM). In 2012, GSFC’s Engineering and Technology Directorate (ETD) implemented an in-house training program to prepare PDLs for managing the technical, cost, schedule, and risk aspects of spaceflight systems to meet their subsystem commitments. Developed in-house, the PDL training program provides an integrated approach to requirements development, risk, schedule and cost management, EVM, performance tracking, and other areas. The program has been held twice yearly since its inception with 531 participating and 451 completing the curriculum. In 2017, the program won the Robert H. Goddard award for Quality and Process Improvement. Program development and evolution were presented in the 2018 NASA Schedule and Cost Symposium. The presentation was so well received that this year we focus on one workshop within the program: Schedule and Cost Development, including EVM. We examine the on-going logic modeling process and how participant and stakeholder data influence workshop content and design, and how the disciplines of schedule and cost contribute to mission success. In this presentation we refresh you on how the approach integrates lecture, small group discussion, estimating, case study exercises, and problem solving. We update you on the data collected from participants and stakeholders, and we discuss how we use these data to measure training effectiveness. Specific topics include: • How the logic model is used as the backbone for continuous program improvement, • How feedback influences implementation and curriculum updates, • How data collection and analysis inform workshop content and development, including participant discoveries of EVM data, • How including the resource analyst and planner in the product development team supports project success.

Lessons Learned↗