Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Jobs”

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 811 records · Page 45
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Low Velocity Difference Thermal Shear Layer Mixing Rate Measurements

Current CFD modeling techniques are known to do a poor job of predicting the mixing rate and persistence of slot film flow in co-annular flowing ducts with relatively small velocity differences but large thermal gradients. A co-annular test was devised to empirically determine the mixing rate of slot film flow in a constant area circular duct (D approx. 1ft, L approx. 10ft). The axial rate of wall heat-up is a sensitive measure of the mixing rate of the two flows. The inflow conditions were varied to simulate a variety of conditions characteristic of moderate by-pass ratio engines. A series of air temperature measurements near the duct wall provided a straightforward means to measure the axial temperature distribution and thus infer the mixing rate. This data provides a characterization of the slot film mixing rates encountered in typical jet engine environments. The experimental geometry and entrance conditions, along with the sensitivity of the results as the entrance conditions vary, make this a good test for turbulence models in a regime important to modern air-breathing propulsion research and development.

Bush, Robert H.↗
NASA NTRS2006

A Comparative Study of Measuring Devices Used During Space Shuttle Processing for Inside Diameters

During Space Shuttle processing, discrepancies between vehicle dimensions and per print dimensions determine if a part should be refurbished, replaced or accepted "as-is." The engineer's job is to address each discrepancy by choosing the most accurate procedure and tool available, sometimes with up to ten thousands of an inch tolerance. Four methods of measurement are commonly used at the Kennedy Space Center: 1) caliper, 2) mold impressions, 3) optical comparator, 4) dial bore gage. During a problem report evaluation, uncertainty arose between methods after measuring diameters with variations of up to 0.0004" inches. The results showed that computer based measuring devices are extremely accurate, but when human factor is involved in determining points of reference, the results may vary widely compared to more traditional methods. iv

Rodriguez, Antonio↗
NASA NTRS2006

Genetic Algorithm for Optimization: Preprocessor and Algorithm

Genetic algorithm (GA) inspired by Darwin's theory of evolution and employed to solve optimization problems - unconstrained or constrained - uses an evolutionary process. A GA has several parameters such the population size, search space, crossover and mutation probabilities, and fitness criterion. These parameters are not universally known/determined a priori for all problems. Depending on the problem at hand, these parameters need to be decided such that the resulting GA performs the best. We present here a preprocessor that achieves just that, i.e., it determines, for a specified problem, the foregoing parameters so that the consequent GA is a best for the problem. We stress also the need for such a preprocessor both for quality (error) and for cost (complexity) to produce the solution. The preprocessor includes, as its first step, making use of all the information such as that of nature/character of the function/system, search space, physical/laboratory experimentation (if already done/available), and the physical environment. It also includes the information that can be generated through any means - deterministic/nondeterministic/graphics. Instead of attempting a solution of the problem straightway through a GA without having/using the information/knowledge of the character of the system, we would do consciously a much better job of producing a solution by using the information generated/created in the very first step of the preprocessor. We, therefore, unstintingly advocate the use of a preprocessor to solve a real-world optimization problem including NP-complete ones before using the statistically most appropriate GA. We also include such a GA for unconstrained function optimization problems.

Sen, S. K.↗
NASA NTRS2007

A Study to Estimate the Effectiveness of Visual Testing Training for Aviation Maintenance Management

The Air Commerce Act of 1926 set the beginning for standards in aviation maintenance. Even after deregulation in the late l970s, maintenance standards and requirements still have not changed far from their initial criteria. After a potential candidate completes Federal Aviation Administration training prerequisites, they may test for their Airframe and Powerplant (A&P) certificate. Performing maintenance in the aviation industry for a minimum of three years, the technician may then test for their Inspection Authorization (IA). After receiving their Airframe and Powerplant certificate, a technician is said to have a license to perform. At no time within the three years to eligibility for Inspection Authorization are they required to attend higher-level inspection training. What a technician learns in the aviation maintenance industry is handed down from a seasoned technician to the new hire or is developed from lessons learned on the job. Only in Europe has the Joint Aviation Authorities (JAA) required higher-level training for their aviation maintenance technicians in order to control maintenance related accidents (Lu, 2005). Throughout the 1990s both the General Accounting Office (GAO) and the National Transportation Safety Board (NTSB) made public that the FAA is historically understaffed (GAO, 1996). In a safety recommendation the NTSB stated "The Safety Board continues to lack confidence in the FAA's commitment to provide effective quality assurance and safety oversight of the ATC system (NTSB, 1990)." The Federal Aviation Administration (FAA) has been known to be proactive in creating safer skies. With such reports you would suspect the FAA to also be proactive in developing more stringent inspection training for aviation maintenance technicians. The purpose of this study is to estimate the effectiveness of higher-level inspection training, such as Visual Testing (VT) for aviation maintenance technicians, to improve the safety of aircraft and to make recommendations to management with regard to the value of such training.

Law, Lewis Lyle↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRS2013

3D Printed Robotic Hand

Dexterous robotic hands are changing the way robots and humans interact and use common tools. Unfortunately, the complexity of the joints and actuations drive up the manufacturing cost. Some cutting edge and commercially available rapid prototyping machines now have the ability to print multiple materials and even combine these materials in the same job. A 3D model of a robotic hand was designed using Creo Parametric 2.0. Combining "hard" and "soft" materials, the model was printed on the Object Connex350 3D printer with the purpose of resembling as much as possible the human appearance and mobility of a real hand while needing no assembly. After printing the prototype, strings where installed as actuators to test mobility. Based on printing materials, the manufacturing cost of the hand was $167, significantly lower than other robotic hands without the actuators since they have more complex assembly processes.

Pizarro, Yaritzmar Rosario↗
NASA NTRS2013

Modular Connector Keying Concept

For panel-mount-type connectors, keying is usually "built-in" to the connector body, necessitating different part numbers for each key arrangement. This is costly for jobs that require small quantities. This invention was driven to provide a cost savings and to reduce documentation of individual parts. The keys are removable and configurable in up to 16 combinations. Since the key parts are separate from the connector body, a common design can be used for the plug, receptacle, and key parts. The keying can then be set at the next higher assembly.

Ishman, Scott↗
NASA NTRS2012

U.S. Spacesuit Knowledge Capture Series Catalog

The National Aeronautics and Space Administration (NASA) and other organizations have been performing U.S. Spacesuit Knowledge Capture (USSKC) since the beginning of space exploration through published reports, conference presentations, specialized seminars, and classes instructed by veterans in the field. The close physical interaction between spacesuit systems and human beings makes them among the most personally evocative pieces of space hardware. Consequently, spacesuit systems have required nearly constant engineering refinements to do their jobs without impinging on human activity. Since 2008, spacesuit knowledge capture has occurred through video recording, engaging both current and former specialists presenting technical scope specifically to educate individuals and preserve knowledge. These archives of spacesuit legacy reflect its rich history and will provide knowledge that will enhance the chances for the success of future and more ambitious spacesuit system programs. The scope and topics of USSKC have included lessons learned in spacesuit technology; experience from the Gemini, Apollo, Skylab, and Shuttle Programs; the process of hardware certification, design, development, and other program components; spacesuit evolution and experience; failure analysis and resolution; and aspects of program management. USSKC activities have progressed to a level where NASA, the National Air and Space Museum (NASM), Hamilton Sundstrand (HS) and the spacesuit community are now working together to provide a comprehensive way to organize and archive intra-agency information related to the development of spacesuit systems. These video recordings are currently being reviewed for public release using NASA export control processes. After a decision is made for either public or non-public release (internal NASA only), the videos and presentations will be available through the NASA Johnson Space Center Engineering Directorate (EA) Engineering Academy, the NASA Technical Reports Server (NTRS), the NASA Aeronautics & Space Database (NA&SD), or NASA YouTube. Event availability is duly noted in this catalog.

Bitterly, Rose↗
NASA NTRS2014

Coatings Preserve Metal, Stone, Tile, and Concrete

John B. Schutt, a chemist at Goddard Space Flight Center, created a coating for spacecraft that could resist corrosion and withstand high heat. After retiring from NASA, Schutt used his expertise to create new formulations for Daytona Beach, Florida-based Adsil Corporation, which now manufactures a family of coatings to preserve various surfaces. Adsil has created 150 jobs due to the products.

Source record↗
NASA NTRS2014

Shuttle Engine Designs Revolutionize Solar Power

The Space Shuttle Main Engine was built under contract to Marshall Space Flight Center by Rocketdyne, now part of Pratt & Whitney Rocketdyne (PWR). PWR applied its NASA experience to solar power technology and licensed the technology to Santa Monica, California-based SolarReserve. The company now develops concentrating solar power projects, including a plant in Nevada that has created 4,300 jobs during construction.

Source record↗
NASA NTRS2013

Flight Planning Branch NASA Co-op Tour

This semester I worked with the Flight Planning Branch at the NASA Johnson Space Center. I learned about the different aspects of flight planning for the International Space Station as well as the software that is used internally and ISSLive! which is used to help educate the public on the space program. I had the opportunity to do on the job training in the Mission Control Center with the planning team. I transferred old timeline records from the planning team's old software to the new software in order to preserve the data for the future when the software is retired. I learned about the operations of the International Space Station, the importance of good communication between the different parts of the planning team, and enrolled in professional development classes as well as technical classes to learn about the space station.

Marr, Aja M.↗
NASA NTRS2013

Autonomous Control of Space Nuclear Reactors

Nuclear reactors to support future robotic and manned missions impose new and innovative technological requirements for their control and protection instrumentation. Long-duration surface missions necessitate reliable autonomous operation, and manned missions impose added requirements for failsafe reactor protection. There is a need for an advanced instrumentation and control system for space-nuclear reactors that addresses both aspects of autonomous operation and safety. The Reactor Instrumentation and Control System (RICS) consists of two functionally independent systems: the Reactor Protection System (RPS) and the Supervision and Control System (SCS). Through these two systems, the RICS both supervises and controls a nuclear reactor during normal operational states, as well as monitors the operation of the reactor and, upon sensing a system anomaly, automatically takes the appropriate actions to prevent an unsafe or potentially unsafe condition from occurring. The RPS encompasses all electrical and mechanical devices and circuitry, from sensors to actuation device output terminals. The SCS contains a comprehensive data acquisition system to measure continuously different groups of variables consisting of primary measurement elements, transmitters, or conditioning modules. These reactor control variables can be categorized into two groups: those directly related to the behavior of the core (known as nuclear variables) and those related to secondary systems (known as process variables). Reliable closed-loop reactor control is achieved by processing the acquired variables and actuating the appropriate device drivers to maintain the reactor in a safe operating state. The SCS must prevent a deviation from the reactor nominal conditions by managing limitation functions in order to avoid RPS actions. The RICS has four identical redundancies that comply with physical separation, electrical isolation, and functional independence. This architecture complies with the safety requirements of a nuclear reactor and provides high availability to the host system. The RICS is intended to interface with a host computer (the computer of the spacecraft where the reactor is mounted). The RICS leverages the safety features inherent in Earth-based reactors and also integrates the wide range neutron detector (WRND). A neutron detector provides the input that allows the RICS to do its job. The RICS is based on proven technology currently in use at a nuclear research facility. In its most basic form, the RICS is a ruggedized, compact data-acquisition and control system that could be adapted to support a wide variety of harsh environments. As such, the RICS could be a useful instrument outside the scope of a nuclear reactor, including military applications where failsafe data acquisition and control is required with stringent size, weight, and power constraints.

Merk, John↗
NASA NTRS2013

Mobile Thread Task Manager

The Mobile Thread Task Manager (MTTM) is being applied to parallelizing existing flight software to understand the benefits and to develop new techniques and architectural concepts for adapting software to multicore architectures. It allocates and load-balances tasks for a group of threads that migrate across processors to improve cache performance. In order to balance-load across threads, the MTTM augments a basic map-reduce strategy to draw jobs from a global queue. In a multicore processor, memory may be "homed" to the cache of a specific processor and must be accessed from that processor. The MTTB architecture wraps access to data with thread management to move threads to the home processor for that data so that the computation follows the data in an attempt to avoid L2 cache misses. Cache homing is also handled by a memory manager that translates identifiers to processor IDs where the data will be homed (according to rules defined by the user). The user can also specify the number of threads and processors separately, which is important for tuning performance for different patterns of computation and memory access. MTTM efficiently processes tasks in parallel on a multiprocessor computer. It also provides an interface to make it easier to adapt existing software to a multiprocessor environment.

Clement, Bradley J.↗
NASA NTRS2013

Education Office Application Design and Development

The content of this project focuses on designing and implementing a new prototype website for the Kennedy Intern Tracking System (KITS). The goal of the new website is to allow the user to search for interns based on several different categories and fields. In hence, making it easier to find a count of interns matching a set of criteria. The KSC office of education is the primary users of KITS, their job is to recruit interns year-round. As a secondary goal, each user will be able to generate a report of their searches onto a portable document format (PDF) me. The results of each search will be set to a limited amount per page. This site will be used for Kennedy Space Center internal purposes only. After the implementations are done, a visual walk through using screen shots will be used to guide the users through all of the different scenarios that are likely to occur when the users are navigating through the site. In addition, a demo of the site will be presented to the KSC Office of Education. JavaScript and JQuery are the languages that will focus on the functionality of the implementation. Hyper Text Markup Language will be used to form the foundation for the body structure of the website. Ruby will be the programming language used to elevate the prototype to a dynamic website and enable the programmer to finish with in an efficient time frame. Cascading Style Sheet will be the language used for the design and styling purposes. Rails is the framework that the new website will be built upon. By default, the database will be managed by Sequel Lite (SQLite). All users will need to be granted special privileges in order to use the site.

Johnson, Jamie E.↗
NASA NTRS2013

Kennedy Space Center: Swamp Works

When I began my internship with the Granular Mechanics and Regolith Operations laboratory (GMRO), also known as Swamp Works, I was given the unique opportunity to shadow many teams working on various projects, and decide what projects I wanted to take part in. Before I go into details of my experiences at Swamp Works, I would like to take a moment to explain what I discovered Swamp Works to be. Swamp Works is a family of hardworking, dedicated, and driven people from various backgrounds and skill sets. These people all work to advance technologies and make science fiction science fact through means of rapid prototyping. They support and encourage failure as an option when learning new things, as long as lesson learned from said failure. In fact, their motto states "Fail, Fast, Forward." What this means is, not if but when one fails he or she must do so quickly and spring forward from the failure so that his or her progress is not delayed. With this acceptance, it provided me the confidence to dive into a multitude of projects working in various fields and with a wide range of skill sets. The first project I joined was Badger. My motivation for taking on this project was the opportunity I would have to obtain valuable experience working with 3D modeling and 3D printing technologies. Badger was a digging apparatus to be used in a highly dusty environment in a material known as Regolith. Regolith is a scientific term for the dirt or top soil found on planetary bodies. Regolith contains a large quantity of sediments less than lOppm and as a result poses a challenge of keeping it out of any cracks and crevices. Furthermore, regolith can create high levels of electrostatic energy, which can prove damaging to sensitive electrical hardware. With these characteristics in mind, I decided to take on the task of designing and manufacturing a dust proof cover for the sensitive electrical hardware. When I began this project, I did not have the slightest idea as to how to use 3D modeling software or a means of manufacturing a viable product. As I went along with variants of the design, I became very proficient with a 3D modeling program known as CREO 2.0. Upon completion of my 3D design, I then had the task of manufacturing and having, in my hands, a usable model. To do this I had to work with additive printing technologies also known as 3D printing. Through my experiences working with Badger, I realized that 3D modeling is the focal point in much of engineering. With this in mind, I have embraced this fact and decided to further my experience with this software so that I may become a more valuable asset to any firm later in my career. Mid-way through work with Badger, I picked up another project in which I found much interest. I ha~ the opportunity to work side by side with a materials and composites guru in manufacturing carbon composite coupons (test strips) for performing stress, strain, and sheer analysis on. Being from a surfing, kiteboarding, and other water sport background I have always been interested in board design. With this in mind, it is no wonder why I found interest in such a project. I had the opportunity to refine Mold preparatory, composite layup, and composite curing techniques. Following manufacturing of these composite strips, I then performed various stress tests and logged my results. With these results, future teams could create lighter, stronger, and more cost effective composite structures for use in varieties of applications. After my experiences with materials and composites testing, I have obtained crucial appreciation for detailed documentation and analysis that material sciences involve. However, as interesting as composite materials testing has been, I do not feel this is where my future career lies. Another, more on the side, project I have been involved in is building a 626 cubic foot regolith containment chamber for doing full scale testing of robotic systems. This chamber is built of high strength aluminum scaffold materials, 80/20, and massive panels of Lexan. Once the chamber is completed, it is be filled with 120 tons of regolith and dubbed the largest regolith test chamber in the world. Through my experiences with building "Big Bin" as we called it, I discovered my demand for engaging and hands on activities. Through all of my incredible experiences working with the Swamp Works at Kennedy Space Center; I have obtained crucial knowledge, insights, and experiences that have fuelled, shaped, and will continue to drive me toward my ultimate goal of obtaining not only a degree in Engineering, but obtaining a job that I can call a career. I want to give much thanks to all of those who mentored me along my journey, and to all who made this opportunity a reality.

DeFilippo, Anthony Robert↗
NASA NTRS2014

Monitoring for Renal Stone Recurrence in Astronauts With History of Stone

After an initial stone episode persons are at increased risk for future stone formation. A systematic approach is required to monitor the efficacy of treatment and preventive measures, and to assess the risk of developing new stones. This is important for persons working in critical jobs or austere environments, such as astronauts. A literature review of the current standards of care for renal stone monitoring and imaging was done. Military and civil aviation standards were also reviewed, as well as the medical precedents from the space program. Additionally, a new, more effective, renal stone ultrasound protocol has been developed. Using this work, a monitoring algorithm was proposed that takes into consideration the unique mission and operational environment of spaceflight. The approach to imaging persons with history of renal stones varies widely in the literature. Imaging is often done yearly or biannually, which may be too long for mission critical personnel. In the proposed algorithm astronauts with a history of renal stone, who may be under consideration for assignment, are imaged by a detailed, physiciandriven, ultrasound protocol. Unassigned personnel are monitored by yearly ultrasound and urine studies. Any positive ultrasound study is then followed by low-dose renal computed tomography scan. Other criteria are also established. The proposed algorithm provides a balanced approach between efficacy and reduced radiation exposure for the monitoring of astronauts with a renal stone history. This may eventually allow a transition from a risk-averse, to a risk-modifying approach that can enable continued service of individuals with history of renal stone that have adequately controlled risk factors.

Reyes, David P.↗
NASA NTRS2014

Earth Science Informatics Comes of Age

The volume and complexity of Earth science data have steadily increased, placing ever-greater demands on researchers, software developers and data managers tasked with handling such data. Additional demands arise from requirements being levied by funding agencies and governments to better manage, preserve and provide open access to data. Fortunately, over the past 10-15 years significant advances in information technology, such as increased processing power, advanced programming languages, more sophisticated and practical standards, and near-ubiquitous internet access have made the jobs of those acquiring, processing, distributing and archiving data easier. These advances have also led to an increasing number of individuals entering the field of informatics as it applies to Geoscience and Remote Sensing. Informatics is the science and technology of applying computers and computational methods to the systematic analysis, management, interchange, and representation of data, information, and knowledge. Informatics also encompasses the use of computers and computational methods to support decisionmaking and other applications for societal benefits.

Jodha, Siri↗