Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “WBS”

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.

77 records · Page 5

Rule-Based Flight Software Cost Estimation

This paper discusses the fundamental process for the computation of Flight Software (FSW) cost estimates. This process has been incorporated in a rule-based expert system [1] that can be used for Independent Cost Estimates (ICEs), Proposals, and for the validation of Cost Analysis Data Requirements (CADRe) submissions. A high-level directed graph (referred to here as a decision graph) illustrates the steps taken in the production of these estimated costs and serves as a basis of design for the expert system described in this paper. Detailed discussions are subsequently given elaborating upon the methodology, tools, charts, and caveats related to the various nodes of the graph. We present general principles for the estimation of FSW using SEER-SEM as an illustration of these principles when appropriate. Since Source Lines of Code (SLOC) is a major cost driver, a discussion of various SLOC data sources for the preparation of the estimates is given together with an explanation of how contractor SLOC estimates compare with the SLOC estimates used by JPL. Obtaining consistency in code counting will be presented as well as factors used in reconciling SLOC estimates from different code counters. When sufficient data is obtained, a mapping into the JPL Work Breakdown Structure (WBS) from the SEER-SEM output is illustrated. For across the board FSW estimates, as was done for the NASA Discovery Mission proposal estimates performed at JPL, a comparative high-level summary sheet for all missions with the SLOC, data description, brief mission description and the most relevant SEER-SEM parameter values is given to illustrate an encapsulation of the used and calculated data involved in the estimates. The rule-based expert system described provides the user with inputs useful or sufficient to run generic cost estimation programs. This system's incarnation is achieved via the C Language Integrated Production System (CLIPS) and will be addressed at the end of this paper.

computational intelligence↗

Designing and Developing Web-Based Administrative Tools for Program Management

The task assigned for this internship was to develop a new tool for tracking projects, their subsystems, the leads, backups, and other employees assigned to them, as well as all the relevant information related to the employee (WBS (time charge) codes, time distribution, certifications, and assignments). Currently, this data is tracked manually using a number of different spreadsheets and other tools simultaneously by a number of different people; some of these documents are then merged into one large document. This often leads to inconsistencies and loss in data due to human error. By simplifying the process of tracking this data and aggregating it into a single tool, it is possible to significantly decrease the potential for human error and time spent collecting and checking this information. II. Objective The main objective of this internship is to develop a web-based tool using Ruby on Rails to serve as a method of easily tracking projects, subsystems, and points of contact, along with employees, their assignments, time distribution, certifications, and contact information. Additionally, this tool must be capable of generating a number of different reports based on the data collected. It was important that this tool deliver all of this information using a readable and intuitive interface.

Material↗

WindBots: A Concept for Persistent In-Situ Science Explorers for Gas Giants

This report summarizes the study of a mission concept to Jupiter with one or multiple Wind Robots able to operate in the Jovian atmosphere, above and below the clouds - down to 10 bar, for long durations and using energy obtained from local sources. This concept would be a step towards persistent exploration of gas giants by robots performing in-situ atmospheric science, powered by locally harvested energy. The Wind Robots, referred in this report as WindBots (WBs), would ride the planetary winds and transform aeolian energy into kinetic energy of flight, and electrical energy for on-board equipment. Small shape adjustments modify the aerodynamic characteristics of their surfaces, allowing for changes in direction and a high movement autonomy. Specifically, we sought solutions to increase survivability to strong/turbulent winds, and mobility and autonomy compared to passive balloons.

WindBots↗

In-Situ Surface Construction of Infrastructure

In situ resources offer an opportunity to reduce the amount of items brought from Earth when exploring moons and planets. Utilizing those resources requires energy that comes with a cost. In the case of human missions to Mars, trading surface power for launch mass is beneficial for propellant and consumables required to sustain human pioneering and settlement on the planet’s surface. However, In Situ Resource Utilization (ISRU) can mean far more than propellant production and consumables replacement for missions beyond Low Earth Orbit. NASA’s Systems Capability Leader-ship Team (SCLT) for ISRU created a work break-down structure based on functions identified in roadmaps pertaining to human exploration. That WBS includes Prospecting, Extraction, Processing, Construction, Manufacturing, and Energy. Over the years, NASA has developed some capabilities and technologies for prospecting, extraction, and processing carbon dioxide and water on Mars into propellants and life support consumables. However, that is a small subset of the ISRU needs that are coming to light with NASA’s push to return to the Moon for extended periods of time. For instance, astronauts require shielding from Ga-lactic Cosmic Rays and nuclear radiation and protection from the low temperatures and pressures in Space. Surface assets including crew, landers, and ascent modules can be damaged by surface ejecta during landing and launch operations on the Moon and Mars. Creating shielding, berms, and pads requires movement of large volumes and stabilization of regolith in the context of a civil engineering construction project. Because of the multi-disciplinary nature of the aerospace systems needed for human exploration, SCLT on ISRU created an ISRU Construction Integrated Steering Group that combines expertise among several NASA Principal Technologists and Capabilities Leaders for exploring options, assessing opportunities, and developing requirements for construction and manufacturing on the Moon and Mars NASA’s new program to develop Lunar landers for small, mid, and large payload deliveries to the Lunar surface leading to human missions by 2025 spawned an investigation into plume surface interactions caused by the lander during descent and ascent. The trade space to resolve this issue includes regolith stabilization via landing pad construction techniques and lander nozzles characteristics due to vehicle systems design. Some data exists from the Apollo missions but more is required for the missions ahead. The purpose of this paper [1] is to outline an approach for developing requirements that can guide systems designs while taking advantage of flight opportunities in NASA’s plans to return to the Moon.

In-Situ↗

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. Because NASA implements a diverse and unique portfolio of projects, those projects have traditionally created project-specific systems to manage planning and performance analysis. However, establishment and implementation of a project management system that is common across all centers and mission directorates will facilitate the adoption of best business practices. In addition, the application of timely and predictive analysis, as well as, providing all stakeholders with greater insight into project performance will enhance opportunities for project success. For more detailed information, refer to the NASA EVM System Description; Integrated Baseline Review (IBR) Handbook; EVM Implementation Handbook; Schedule Management Handbook; Work Breakdown Structure (WBS) Handbook; and other agency/industry documentation. In addition, you may contact your local center’s EVM Focal Points. All this information and more can be found at and/or the NASA Engineering Network located at https://nen.nasa.gov/web/pm.

Christopher Lewis Sadler↗