Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Summary of the technical management process”

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 19 records

Report-reading patterns of technical managers and nonmanagers

A survey to determine the review and reading processes used by technical managers and nonmanagers indicates that the summary, abstract, conclusion, title page, and introduction are the components used most frequently by both groups to decide whether to read a NASA technical report. In the review process, significantly more managers than nonmanagers use the summary and conclusion, whereas significantly more nonmanagers use the abstract and title page. The most common sequence of review consists of the title page, abstract, and summary, in that order, for both groups. In the reading process, the conclusion, results and discussion, and summary are the components read by the highest percentage of both groups.

Pinelli, T. E.↗

Crew Transportation Technical Management Processes

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document, with its sister documents, International Space Station (ISS) Crew Transportation and Services Requirements Document (CCT-REQ-1130), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), Crew Transportation Operations Standards (CCT STD-1150), and ISS to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase.

Summary of the technical management process↗

Technical and Management Information System (TMIS)

The TMIS goals developed to support the Space Station Program (SSP) mission requirements are outlined. The TMIS will provide common capabilities to all SSP centers and facilitate the flow of technical and management information throughout the program as well as SSP decision-making processes. A summary is presented of the various TMIS phases.

Rau, Timothy R.↗

Advanced technology for America's future in space

In response to Recommendation 8 of the Augustine Committee Report, NASA's Office of Aeronautics, Exploration and Technology (OAET) developed a proposed 'Integrated Technology Plan for the Civil Space Program' that entails substantial changes in the processes, structure and the content of NASA's space research and technology program. The Space Systems and Technology Advisory Committee (SSTAC, a subcommittee of the NASA Advisory Committee) and several other senior, expert, informed advisory groups conducted a review of NASA's proposed Integrated Technology Plan (ITP). This review was in response to the specific request in Recommendation 8 that 'NASA utilize an expert, outside review process, managed from headquarters, to assist in the allocation of technology funds'. This document, the final report from that review, addresses: (1) summary recommendations; (2) mission needs; (3) the integrated technology plan; (4) summary reports of the technical panels; and (5) conclusions and observations.

Source record↗

NASA/Navy Benchmarking Exchange (NNBE). Volume 1. Interim Report. Navy Submarine Program Safety Assurance

The NASA/Navy Benchmarking Exchange (NNBE) was undertaken to identify practices and procedures and to share lessons learned in the Navy's submarine and NASA's human space flight programs. The NNBE focus is on safety and mission assurance policies, processes, accountability, and control measures. This report is an interim summary of activity conducted through October 2002, and it coincides with completion of the first phase of a two-phase fact-finding effort.In August 2002, a team was formed, co-chaired by senior representatives from the NASA Office of Safety and Mission Assurance and the NAVSEA 92Q Submarine Safety and Quality Assurance Division. The team closely examined the two elements of submarine safety (SUBSAFE) certification: (1) new design/construction (initial certification) and (2) maintenance and modernization (sustaining certification), with a focus on: (1) Management and Organization, (2) Safety Requirements (technical and administrative), (3) Implementation Processes, (4) Compliance Verification Processes, and (5) Certification Processes.

SUBSAFE PROGRAM↗

Feasibility study of an Integrated Program for Aerospace vehicle Design (IPAD). Volume 1A: Summary

IPAD was defined as a total system oriented to the product design process. This total system was designed to recognize the product design process, individuals and their design process tasks, and the computer-based IPAD System to aid product design. Principal elements of the IPAD System include the host computer and its interactive system software, new executive and data management software, and an open-ended IPAD library of technical programs to match the intended product design process. The basic goal of the IPAD total system is to increase the productivity of the product design organization. Increases in individual productivity were feasible through automation and computer support of routine information handling. Such proven automation can directly decrease cost and flowtime in the product design process.

Miller, R. E., Jr.↗

Space and Earth Sciences, Computer Systems, and Scientific Data Analysis Support, Volume 1

This Final Progress Report covers the specific technical activities of Hughes STX Corporation for the last contract triannual period of 1 June through 30 Sep. 1993, in support of assigned task activities at Goddard Space Flight Center (GSFC). It also provides a brief summary of work throughout the contract period of performance on each active task. Technical activity is presented in Volume 1, while financial and level-of-effort data is presented in Volume 2. Technical support was provided to all Division and Laboratories of Goddard's Space Sciences and Earth Sciences Directorates. Types of support include: scientific programming, systems programming, computer management, mission planning, scientific investigation, data analysis, data processing, data base creation and maintenance, instrumentation development, and management services. Mission and instruments supported include: ROSAT, Astro-D, BBXRT, XTE, AXAF, GRO, COBE, WIND, UIT, SMM, STIS, HEIDI, DE, URAP, CRRES, Voyagers, ISEE, San Marco, LAGEOS, TOPEX/Poseidon, Pioneer-Venus, Galileo, Cassini, Nimbus-7/TOMS, Meteor-3/TOMS, FIFE, BOREAS, TRMM, AVHRR, and Landsat. Accomplishments include: development of computing programs for mission science and data analysis, supercomputer applications support, computer network support, computational upgrades for data archival and analysis centers, end-to-end management for mission data flow, scientific modeling and results in the fields of space and Earth physics, planning and design of GSFC VO DAAC and VO IMS, fabrication, assembly, and testing of mission instrumentation, and design of mission operations center.

Estes, Ronald H.↗

Exploration Studies Technical Report - Volume 1: Technical Summary

The Office of Exploration (OEXP) at NASA Headquarters has been tasked with defining and recommending alternatives for an early 1990's national decision on a focused program of human exploration of the solar system. The Mission Analysis and System Engineering (MASE) group, which is managed by the Exploration Studies Office at the Lyndon B. Johnson Space Center, is responsible for coordinating the technical studies necessary for accomplishing such a task. This technical report, produced by the MASE, describes the process that has been developed in a case study approach. The four case studies developed in FY88 include: 1. Human Expedition to Phobos 2. Human Expedition to Mars 3. Lunar Observatory 4. Lunar Outpost to Early Mars Evolution The final outcome of this effort is a set of programmatic and technical conclusions and recommendations for the following year's work.

Lunar Mining & Oxygen Production↗

Integrated Space Asset Management Database and Modeling

Effective Space Asset Management is one key to addressing the ever-growing issue of space congestion. It is imperative that agencies around the world have access to data regarding the numerous active assets and pieces of space junk currently tracked in orbit around the Earth. At the center of this issues is the effective management of data of many types related to orbiting objects. As the population of tracked objects grows, so too should the data management structure used to catalog technical specifications, orbital information, and metadata related to those populations. Marshall Space Flight Center's Space Asset Management Database (SAM-D) was implemented in order to effectively catalog a broad set of data related to known objects in space by ingesting information from a variety of database and processing that data into useful technical information. Using the universal NORAD number as a unique identifier, the SAM-D processes two-line element data into orbital characteristics and cross-references this technical data with metadata related to functional status, country of ownership, and application category. The SAM-D began as an Excel spreadsheet and was later upgraded to an Access database. While SAM-D performs its task very well, it is limited by its current platform and is not available outside of the local user base. Further, while modeling and simulation can be powerful tools to exploit the information contained in SAM-D, the current system does not allow proper integration options for combining the data with both legacy and new M&S tools. This paper provides a summary of SAM-D development efforts to date and outlines a proposed data management infrastructure that extends SAM-D to support the larger data sets to be generated. A service-oriented architecture model using an information sharing platform named SIMON will allow it to easily expand to incorporate new capabilities, including advanced analytics, M&S tools, fusion techniques and user interface for visualizations. In addition, tight control of information sharing policy will increase confidence in the system, which would encourage industry partners to provide commercial data. Combined with the integration of new and legacy M&S tools, a SIMON-based architecture will provide a robust environment that can be extended and expanded indefinitely.

MacLeod, Todd↗

Wind sensing, analysis, and modeling

The purpose of this task was to begin development of a unified approach to the sensing, analysis, and modeling of the wind environments in which launch systems operate. The initial activity was to examine the current usage and requirements for wind modeling for the Titan 4 vehicle. This was to be followed by joint technical efforts with NASA Langley Research Center to develop applicable analysis methods. This work was to be performed in and demonstrate the use of prototype tools implementing an environment in which to realize a unified system. At the convenience of the customer, due to resource limitations, the task was descoped. The survey of Titan 4 processes was accomplished and is reported in this document. A summary of general requirements is provided . Current versions of prototype Process Management Environment tools are being provided to the customer.

Corvin, Michael A.↗

Wind Sensing, Analysis, and Modeling

The purpose of this task was to begin development of a unified approach to the sensing, analysis, and modeling of the wind environments in which launch system operate. The initial activity was to examine the current usage and requirements for wind modeling for the Titan 4 vehicle. This was to be followed by joint technical efforts with NASA Langley Research Center to develop applicable analysis methods. This work was to be performed in and demonstrate the use of prototype tools implementing an environment in which to realize a unified system. At the convenience of the customer, due to resource limitations, the task was descoped. The survey of Titan 4 processes was accomplished and is reported in this document. A summary of general requirements is provided. Current versions of prototype Process Management Environment tools are being provided to the customer.

Corvin, Michael A.↗

Cost Estimation and Control for Flight Systems

Good program management practices, cost analysis, cost estimation, and cost control for aerospace flight systems are interrelated and depend upon each other. The best cost control process cannot overcome poor design or poor systems trades that lead to the wrong approach. The project needs robust Technical, Schedule, Cost, Risk, and Cost Risk practices before it can incorporate adequate Cost Control. Cost analysis both precedes and follows cost estimation -- the two are closely coupled with each other and with Risk analysis. Parametric cost estimating relationships and computerized models are most often used. NASA has learned some valuable lessons in controlling cost problems, and recommends use of a summary Project Manager's checklist as shown here.

Hammond, Walter E.↗

Handbook for MAP, volume 32. Part 1: MAP summary. Part 2: MAPSC minutes, reading, August 1989. MAP summaries from nations. Part 3: MAP data catalogue

Extended abstracts from the fourth workshop on the technical and scientific aspects of mesosphere stratosphere troposphere (MST) radar are presented. Individual sessions addressed the following topics: meteorological applications of MST and ST radars, networks, and campaigns; the dynamics of the equatorial middle atmosphere; interpretation of radar returns from clear air; techniques for studying gravity waves and turbulence, intercomparison and calibration of wind and wave measurements at various frequencies; progress in existing and planned MST and ST radars; hardware design for MST and ST radars and boundary layer/lower troposphere profilers; signal processing; and data management.

Vincent, R. A.↗

Central Bureau Status and Perspective

The Central Bureau continues to promote the IGS organization, data and data products as setting the world standard for GPS/GNSS geodetic applications as outlined in the IGS Strategic Plan. The Central Bureau was responsible for the organization of the strategic planning process, preparation of all documents, and the editing and publication of the plan. This was a major activity and the Board s consensus on the plan is a significant milestone in the evolution of the IGS. The Central Bureau is responsible for the day-to-day management of the Service. With 200 organizations in over 80 countries and a ground network of approx. 350 stations, this requires daily interfaces on many different levels globally. The separate summary of the IGS Network Coordinator is included in this annual report and demonstrates the vital technical tasks of the Central Bureau. The CB is also responsible to arrange and organize all Board activities and is involved in the supporting the planning and logistics of all IGS workshops and meetings.

Neilan, Ruth↗

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↗

Report to the administrator by the NASA Aerospace Safety Advisory Panel on the Skylab program. Volume 1: Summary report

Contractor and NASA technical management for the development and manufacture of the Skylab modules is reviewed with emphasis on the following management controls: configuration and interface management; vendor control; and quality control of workmanship. A review of the modified two-stage Saturn V launch vehicle which focused on modifications to accommodate the Skylab payload; resolution of prior flight anomalies; and changes in personnel and management systems is presented along with an evaluation of the possible age-life and storage problems for the Saturn 1-B launch vehicle. The NASA program management's visibility and control of contractor operations, systems engineering and integration, the review process for the evaluation of design and flight hardware, and the planning process for mission operations are investigated. It is concluded that the technical management system for development and fabrication of the modules, spacecraft, and launch vehicles, the process of design and hardware acceptance reviews, and the risk assessment activities are satisfactory. It is indicated that checkout activity, integrated testing, and preparations for and execution of mission operation require management attention.

Source record↗

Medical Data Architecture Prototype Development - Summary of Recent Work and Proposed Ideas for Upcoming Work

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions, and in ExMC Gap Med 10: We do not have the capability to provide computed medical decision support during exploration missions. These gaps recognize the need for a comprehensive medical data management system and the accompanying computational support to provide autonomous medical care during long duration exploration missions. As the MDA matures—including the capability to comprehensively process and discover medically-relevant information to support medical operations during exploration missions—project focus will shift to maturing and extending the MDA platform to enable clinical decision support and real-time guidance. To date, the MDA foundational architecture has recommended exploration medical system Level of Care IV requirements through a series of test bed prototype developments and analog demonstrations. The next stage in the development will focus on more autonomous clinical decision making necessary to address challenges in executing a self-contained medical system that enables health care both with and without assistance from ground support. A thorough understanding of current state of medical decision support systems, advanced machine learning algorithms and vast and varied data sources is required. The development of a clinical decision support for exploration missions (Level of Care V) roadmap is needed: one that assesses of current state of the art of clinical decision support systems (CDSS), interoperability issues, identification of challenges in health and performance monitoring, obtaining and processing information from biosensors, knowledge and data management, data integration and fusion, and advanced algorithm development. This roadmap must also include rapid prototype development in the areas of data processing, advanced analysis and prediction of medical events, and treatment based on medically relevant information processing and evidence-based best practices. In this presentation, an overview of the relevant issues and the beginning framework of a Level of Care V CDSS development roadmap will be provided.

Krihak, M.↗

TA-13: Ground and Launch Systems, 2015 NASA Technology Roadmaps

This presentation is a summary of new content contained in the 2015 update of Technology Area-13, Ground and Launch Systems technology roadmap beyond the content contained in the 2010 version. Also included are brief assessments of benefits, alignments, challenges, technical risk and reasonableness, sequencing and timing, and time and effort to achieve goals. This presentation is part of overall presentations of new content only for the 2015 update of the 15 NASA Technology Roadmaps that will be conducted in a public forum managed by the National Research Council on September 28-29, 2015. The 15 roadmaps have already been publically released via the STI process.

decision-making tools↗