Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Knowledge bases”

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 1,495 records · Page 83

Human Research Program Human Health Countermeasures Element Bone and Muscle Risk Standing Review Panel (SRP)

The Bone and Muscle Risk Standing Review Panel (SRP) met at the NASA Johnson Space Center (JSC) on October 4-6, 2009 to discuss the areas of current and future research targeted by the Human Health Countermeasures (HHC) Element of the Human Research Program (HRP). Using evidence-based knowledge as a background for identified risks to astronaut health and performance, NASA had identified gaps in knowledge to address those risks. Ongoing and proposed tasks were presented to address the gaps. The charge to the Bone and Muscle Risk SRP was to review the gaps, evaluate whether the tasks addressed these gaps and to make recommendations to NASA s HRP Science Management Office regarding the Panel's review. The Bone and Muscle Risk SRP consisted of scientists who are experts in muscle, bone, or both and could evaluate the existing evidence with sufficient knowledge of the potential effects of long duration exposure to microgravity. More important, although expertise in basic science is important, the SRP was requested to evaluate the practicality of the proposed efforts in light of the realistic demands placed on the HRP. In short, all tasks presented in the Integrated Research Plan (IRP) should address specific questions related to the challenges faced by the astronauts as a result of prolonged exposure to microgravity. All tasks proposed to fill the gaps in knowledge should provide applied, translational data necessary to answer the specific questions. Several presentations were made to the SRP during the site visit and the SRP spent sufficient time to address the panel charge, either as a group or in separate sessions for the Bone and Muscle Risk subgroups. The SRP made a final debriefing to the HRP Program Scientist, Dr. John B. Charles, on October 6, 2009. Taking the evidence and identified risks as givens, the SRP concluded that 1) integration of information should lead to a more comprehensive approach to identifying the gaps, 2) not all tasks addressed the gaps as stated in the IRP, 3) better access should be given to the SRP to existing data to include in its review, and 4) there were some missing gaps and tasks. As a result the SRP recommended 1) combining certain gaps, which in some cases were addressed with identical tasks, 2) additional gaps and tasks to address some of the gaps, 3) deleting some gaps and tasks to better focus the efforts of NASA s HRP in prioritizing their efforts, and 4) prioritizing gaps to address significant issues needing resolution in the short term while maintaining an awareness of long-term goals. The SRP commended the efforts by the HHC Element to integrate knowledge gaps and design tasks to address the higher order questions. This integration did not apply to the Bone and Muscle Risk alone, but the musculoskeletal system as its functions integrate with issues in

Glowacki, Julie↗

Integrated System Health Management: Pilot Operational Implementation in a Rocket Engine Test Stand

This paper describes a credible implementation of integrated system health management (ISHM) capability, as a pilot operational system. Important core elements that make possible fielding and evolution of ISHM capability have been validated in a rocket engine test stand, encompassing all phases of operation: stand-by, pre-test, test, and post-test. The core elements include an architecture (hardware/software) for ISHM, gateways for streaming real-time data from the data acquisition system into the ISHM system, automated configuration management employing transducer electronic data sheets (TEDS?s) adhering to the IEEE 1451.4 Standard for Smart Sensors and Actuators, broadcasting and capture of sensor measurements and health information adhering to the IEEE 1451.1 Standard for Smart Sensors and Actuators, user interfaces for management of redlines/bluelines, and establishment of a health assessment database system (HADS) and browser for extensive post-test analysis. The ISHM system was installed in the Test Control Room, where test operators were exposed to the capability. All functionalities of the pilot implementation were validated during testing and in post-test data streaming through the ISHM system. The implementation enabled significant improvements in awareness about the status of the test stand, and events and their causes/consequences. The architecture and software elements embody a systems engineering, knowledge-based approach; in conjunction with object-oriented environments. These qualities are permitting systematic augmentation of the capability and scaling to encompass other subsystems.

Figueroa, Fernando↗

Adaptive Modeling Language and Its Derivatives

Adaptive Modeling Language (AML) is the underlying language of an object-oriented, multidisciplinary, knowledge-based engineering framework. AML offers an advanced modeling paradigm with an open architecture, enabling the automation of the entire product development cycle, integrating product configuration, design, analysis, visualization, production planning, inspection, and cost estimation.

Chemaly, Adel↗

FuzzObserver

Fuzzy Feature Observation Planner for Small Body Proximity Observations (FuzzObserver) is a developmental computer program, to be used along with other software, for autonomous planning of maneuvers of a spacecraft near an asteroid, comet, or other small astronomical body. Selection of terrain features and estimation of the position of the spacecraft relative to these features is an essential part of such planning. FuzzObserver contributes to the selection and estimation by generating recommendations for spacecraft trajectory adjustments to maintain the spacecraft's ability to observe sufficient terrain features for estimating position. The input to FuzzObserver consists of data from terrain images, including sets of data on features acquired during descent toward, or traversal of, a body of interest. The name of this program reflects its use of fuzzy logic to reason about the terrain features represented by the data and extract corresponding trajectory-adjustment rules. Linguistic fuzzy sets and conditional statements enable fuzzy systems to make decisions based on heuristic rule-based knowledge derived by engineering experts. A major advantage of using fuzzy logic is that it involves simple arithmetic calculations that can be performed rapidly enough to be useful for planning within the short times typically available for spacecraft maneuvers.

Howard, Ayanna↗

Rotorcraft Research at the NASA Vertical Motion Simulator

In the 1970 s the role of the military helicopter evolved to encompass more demanding missions including low-level nap-of-the-earth flight and operation in severely degraded visual environments. The Vertical Motion Simulator (VMS) at the NASA Ames Research Center was built to provide a high-fidelity simulation capability to research new rotorcraft concepts and technologies that could satisfy these mission requirements. The VMS combines a high-fidelity large amplitude motion system with an adaptable simulation environment including interchangeable and configurable cockpits. In almost 30 years of operation, rotorcraft research on the VMS has contributed significantly to the knowledge-base on rotorcraft performance, handling qualities, flight control, and guidance and displays. These contributions have directly benefited current rotorcraft programs and flight safety. The high fidelity motion system in the VMS was also used to research simulation fidelity. This research provided a fundamental understanding of pilot cueing modalities and their effect on simulation fidelity.

Aponso, Bimal Lalith↗

Pharmacology Risk Report

It seems very likely that the actions of administered drugs on crewmembers during spaceflight are different than they are on Earth, but even after more than 40 years of spaceflight experience, the answers to most questions about medication use during missions remain unanswered. Use of medications with insufficient knowledge about their actual activities may result in inadequate treatment and may even reduce performance and well-being in particular circumstances. There is evidence that this has already occurred during and immediately after spaceflights. The spaceflight pharmaceutical activity knowledge base must be improved to enable flight surgeons and crewmembers to make better decisions about using pharmaceuticals inflight. The spaceflight environment induces changes in human physiology, and these changes have been the subject of much study over the past few decades. These studies are confounded by the small number of potential subjects, as well by the inability to separate the different stressors of spaceflight (radiation exposure from microgravity, for example). In every physiological system, the details of spaceflight-induced physiological changes are not well understood. Despite this fact, crewmembers are treated with pharmaceuticals to reduce or prevent medical problems, with insufficient information as to drug function on their altered physiological systems. There are two major concerns about pharmaceutical use in the unusual environment of spaceflight. The actions of pharmaceuticals on physiology altered by a spaceflight environment are currently assumed to be the same as the actions in terrestrial use. This has yet to be established. The wide range of physiological systems altered by spaceflight and the degree of change experienced in some of them make it very likely that alterations in pharmaceutical action will be seen. As the duration of missions lengthens to include more distant exploration, it becomes more likely that problems will be encountered. Secondly, the integrity of stored pharmaceuticals must be established to ensure that adequate amounts of active compounds are available in each dose and that degradation to toxic compounds is minimized. This risk is also dependent on mission duration, since longer missions will require that drugs be stored much longer than their usual terrestrial shelf-lives.

Source record↗

Systems Maintenance Automated Repair Tasks (SMART)

SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.

Schuh, Joseph↗

Microbial Contamination in the Spacecraft

Spacecraft and space habitats supporting human exploration contain a diverse population of microorganisms. Microorganisms may threaten human habitation in many ways that directly or indirectly impact the health, safety, or performance of astronauts. The ability to produce and maintain spacecraft and space stations with environments suitable for human habitation has been established over 40 years of human spaceflight. An extensive database of environmental microbiological parameters has been provided for short-term (< 20 days) spaceflight by more than 100 missions aboard the Space Shuttle. The NASA Mir Program provided similar data for long-duration missions. Interestingly, the major bacterial and fungal species found in the Space Shuttle are similar to those encountered in the nearly 15-year-old Mir. Lessons learned from both the US and Russian space programs have been incorporated into the habitability plan for the International Space Station. The focus is on preventive measures developed for spacecraft, cargo, and crews. On-orbit regular housekeeping practices complete with visual inspections are essential, along with microbiological monitoring. Risks associated with extended stays on the Moon or a Mars exploration mission will be much greater than previous experiences because of additional unknown variables. The current knowledge base is insufficient for exploration missions, and research is essential to understand the effects of spaceflight on biological functions and population dynamics of microorganisms in spacecraft.

Pierson, Duane L.↗

AIAA Aerospace America Magazine - Year in Review Article, 2010

NASA Stennis Space Center has implemented a pilot operational Integrated System Health Management (ISHM) capability. The implementation was done for the E-2 Rocket Engine Test Stand and a Chemical Steam Generator (CSG) test article; and validated during operational testing. The CSG test program is a risk mitigation activity to support building of the new A-3 Test Stand, which will be a highly complex facility for testing of engines in high altitude conditions. The foundation of the ISHM capability are knowledge-based integrated domain models for the test stand and CSG, with physical and model-based elements represented by objects the domain models enable modular and evolutionary ISHM functionality.

Figueroa, Fernando↗

Failure Analysis at the Kennedy Space Center

History has shown that failures occur in every engineering endeavor, and what we learn from those failures contributes to the knowledge base to safely complete future missions. The necessity of failure analysis is at its apex at the end of one aged program and at the beginning of a new and untested program. The information that we gain through failure analysis corrects the deficiencies in the current vehicle to make the next generation of vehicles more efficient and safe. The Failure Analysis and Materials Evaluation Branch in the Materials Science Division at the Kennedy Space Center performs metallurgical, mechanical, electrical, and non-metallic materials failure analyses and accident investigations on both flight hardware and ground support equipment for the Space Shuttle, International Space Station, Constellation, and Launch Services Programs. This paper will explore a variety of failure case studies at the Kennedy Space Center and the lessons learned that can be applied in future programs.

Salazar, Victoria L.↗

Current Status of NASA's Heavy Lift Plans

Numerous studies since the Apollo Program of the 1960s have highlighted the benefits of - and the need for - a national heavy lift launch capability to support human exploration, science, national security, and commercial development of space. NASA's most recent and most refined effort to develop that heavy lift capability is the Ares V. Ares V is a key element of NASA's Constellation Program. It s overall goal s part of approved national space policy is to retire the Space Shuttle and develop its successor, complete the International Space Station, and resume human exploration beyond low Earth orbit (LEO), beginning with exploration of the Moon as a step to other destinations in the Solar System. Ares V s first role is that of cargo vehicle to carry a lunar lander into Earth orbit, rendezvous with astronauts launched on the smaller Ares I crew launch vehicle, and perform the trans lunar injection (TLI) mission to send the mated crew and lander vehicles to the Moon. The design reference missions (DRMs) envisioned for it also include direct lunar cargo flights and a human Mars mission. Although NASA's priority from the start of the Constellation Program to the present has been development of the Ares I and Orion crew vehicle to replace the retiring Shuttle fleet, the Ares team has made significant progress in understanding the performance, design trades, technology needs, mission scenarios, ground and flight operations, cost, and other factors associated with heavy lift development. The current reference configuration was selected during the Lunar Capabilities Concept Review (LCCR) in fall 2008. That design has served since then as a point of departure for further refinements and trades among five participating NASA field centers. Ares V development to date has benefited from progress on the Ares I due to commonality between the vehicles. The Ares I first stage completed a successful firing of a 5-segment solid rocket motor. The Ares I-X launch Numerous studies since the Apollo Program of the 1960s have highlighted the benefits of and the need for - a national heavy lift launch capability to support human exploration, science, national security, and commercial development of space. NASA s most recent and most refined effort to develop that heavy lift capability is the Ares V. Ares V is a key element of NASA s Constellation Program. It s overall goal s part of approved national space policy is to retire the Space Shuttle and develop its successor, complete the International Space Station, and resume human exploration beyond low Earth orbit (LEO), beginning with exploration of the Moon as a step to other destinations in the Solar System. Ares V s first role is that of cargo vehicle to carry a lunar lander into Earth orbit, rendezvous with astronauts launched on the smaller Ares I crew launch vehicle, and perform the trans lunar injection (TLI) mission to send the mated crew and lander vehicles to the Moon. The design reference missions (DRMs) envisioned for it also include direct lunar cargo flights and a human Mars mission. Although NASA s priority from the start of the Constellation Program to the present has been development of the Ares I and Orion crew vehicle to replace the retiring Shuttle fleet, the Ares team has made significant progress in understanding the performance, design trades, technology needs, mission scenarios, ground and flight operations, cost, and other factors associated with heavy lift development. The current reference configuration was selected during the Lunar Capabilities Concept Review (LCCR) in fall 2008. That design has served since then as a point of departure for further refinements and trades among five participating NASA field centers. Ares V development to date has benefited from progress on the Ares I due to commonality between the vehicles. The Ares I first stage completed a successful firing of a 5-segment solid rocket motor. The Ares I-X launch successfully demonstrated in suborbital flighhe ability to assemble, prepare, launch, control and recover the Ares I configuration and compare performance to computer models. Component tests continue on the J-2X engine, which will put both the Ares I and Ares V upper stages into orbit. In addition, more than 100,000 parts have been manufactured or on the assembly line for the first J-2X powerpack and the first two development engines, with hot fire tests to begin in 2011. This paper will further detail the progress to date on the Ares V and planned activities for the remainder of 2010. In addition, the Ares V team has continued its outreach to potential user communities in science and national security. Through the Constellation Program, NASA has amassed an enormous knowledge base in the design, technologies, and operations of heavy lift launch vehicles that will be a national asset for any future launch vehicle decision. This early phase of the design presents the best opportunity to incorporate where possible the insights and needs of other users.

Creech, Steve↗

Micro-Scale Distributions of Major and Trace Elements in Chondrites

The Hayabusa spacecraft has successfully returned to Earth after two touchdowns on the surface of Asteroid 25143 Itokawa. This asteroid is classified as an S-type and inferred to consist of materials similar to ordinary chondrites or primitive achondrites [1]. More than 1500 particles have been identified consisting of olivine, pyroxene, plagioclase, Fe sulfide and Fe metal, with compositions consistent with being of LL origin. While the chondritic components are familiar to us, the level of detail to which the Itokawa samples will be exposed to will be unprecedented given that the samples are reasonably large and accessible to a wide variety of techniques. In many ways, we expect that our knowledge base of the comparator chondrites will be found to be wanting. Chondrites are the building blocks of the solar system. However, these rocks are essentially breccias and they are quite variable in bulk element compositions as well as compositions of the individual components. We have initiated a program of analysis for chondrites focusing on major and trace element distributions between the mineral components and the matrix. The issues to be addressed include the homogeneity of matrix and chondrule components and the representivity of any given sample to the bulk meteorite. This may be particularly important given the limited numbers of Itokawa grains that may be available for a specific analysis. As an initial study, we have taken thin sections of carbonaceous chondrites to study the representivity of the matrix compositions. Spot locations were constrained to limited regions of the sections so as to assess the variability of a local scale. Further work will be required to assess variability over a centimeter scale.

Ireland, T. R.↗

AstroBetter: A Blog and Wiki for Professional Astronomers

AstroBetter.com is a multi-contributor blog and wiki website designed for information sharing among professional astronomers. The goal of the site is to increase the productivity of astronomers by creating a centralized location for tips and tools of our multifaceted trade. Our content includes topics related to data reduction and analysis, general computing, writing papers and proposals, giving talks, teaching, career planning, productivity, organization, and diversity and equity in science and education. While we have several contributors, the site is intended to be community driven and we encourage everyone to publish to the wiki, submit guest posts, suggest post ideas, and to comment on blog entries. One of our primary goals is to consolidate and reduce the transient nature of the astronomy community's collective knowledge base by having an active wiki. Currently, the most common way to share astro-centric tools and tips that are not appropriate for a published paper, is to put them on an individual's website. However, the average astronomer's website will have at least four different addresses over the course of their career and only the site owner can edit the content. As a result, information on personal websites goes stale very quickly and deal links to such sites abound. It is our hope that community maintained wikis, such as the one hosted on AstroBetter, will gradually replace the personal website. In this poster we introduce the contributors to AstroBetter, show statistics about our current readership, give excerpts of some of our most popular posts and wiki entries, and show how anyone can add or edit content on the wiki. The goal of this poster is to spread the work about AstroBetter and increase our community of readers and wiki editors, because together, we can AstroBetter.

Rigby, Jane↗

Communicating Medical Needs to Non-Medical Managers

Differences in communication styles and languages between groups often lead to miscommunication, confusion, and/or frustration. Engineers, computer specialists, clinicians, and managers often utilize the English language in very different ways, with different groups using the same words to represent different concepts ("complaint" is a typical example). In addition, medical issues are often perceived as "off-nominal" and not "primary mission tasks" by managers, which can cause them to assign lower priorities to medical training time and resources. Knowledge bases differ due to variations in training and skill sets, and the goals (both immediate and long-term) of the communicators may also vary, with managers being primarily concerned with overall mission objectives, while clinicians focus on individual or group health issues. Furthermore, true communication is only possible when clinicians possess a deep understanding of mission requirements as well as the ability to communicate medical requirements on a priority basis using risk assessment, added value, and cost benefit analysis. These understandable differences may contribute to difficulties in expressing concerns and ideas in an efficient manner, particularly in projects, such as the space program or many military operations, where these varied groups must collaborate, and where the final decisions must be made by fully informed mission commanders. Methods: Three scenario-based approaches were developed utilizing decision trees and problem based learning, to help define and integrate these concepts. Results: Use of these techniques by NASA and military personnel will be presented. Discussion: To enhance communication, particularly of medical needs, one must identify the concerns and motivating factors for the other groups; for example, members of management may focus on financial concerns, a desire for risk mitigation, public perceptions, mission objectives, etc. Training clinicians to frame issues in these terms may lead to better understanding of the medical concerns by other groups.

Bacal, Kira↗

Recent Experiences of the NASA Engineering and Safety Center (NESC) Guidance Navigation and Control (GN and C) Technical Discipline Team (TDT)

The NASA Engineering and Safety Center (NESC) is an independently funded NASA Program whose dedicated team of technical experts provides objective engineering and safety assessments of critical, high risk projects. NESC's strength is rooted in the diverse perspectives and broad knowledge base that add value to its products, affording customers a responsive, alternate path for assessing and preventing technical problems while protecting vital human and national resources. The Guidance Navigation and Control (GN&C) Technical Discipline Team (TDT) is one of fifteen such discipline-focused teams within the NESC organization. The TDT membership is composed of GN&C specialists from across NASA and its partner organizations in other government agencies, industry, national laboratories, and universities. This paper will briefly define the vision, mission, and purpose of the NESC organization. The role of the GN&C TDT will then be described in detail along with an overview of how this team operates and engages in its objective engineering and safety assessments of critical NASA.

Dennehy, Cornelius J.↗

Hypersonic Viscous Flow Over Large Roughness Elements

Viscous flow over discrete or distributed surface roughness has great implications for hypersonic flight due to aerothermodynamic considerations related to laminar-turbulent transition. Current prediction capability is greatly hampered by the limited knowledge base for such flows. To help fill that gap, numerical computations are used to investigate the intricate flow physics involved. An unstructured mesh, compressible Navier-Stokes code based on the space-time conservation element, solution element (CESE) method is used to perform time-accurate Navier-Stokes calculations for two roughness shapes investigated in wind tunnel experiments at NASA Langley Research Center. It was found through 2D parametric study that at subcritical Reynolds numbers, spontaneous absolute instability accompanying by sustained vortex shedding downstream of the roughness is likely to take place at subsonic free-stream conditions. On the other hand, convective instability may be the dominant mechanism for supersonic boundary layers. Three-dimensional calculations for both a rectangular and a cylindrical roughness element at post-shock Mach numbers of 4.1 and 6.5 also confirm that no self-sustained vortex generation from the top face of the roughness is observed, despite the presence of flow unsteadiness for the smaller post-shock Mach number case.

Chang, Chau-Lyan↗

Semantic Metrics for Analysis of Software

A recently conceived suite of object-oriented software metrics focus is on semantic aspects of software, in contradistinction to traditional software metrics, which focus on syntactic aspects of software. Semantic metrics represent a more human-oriented view of software than do syntactic metrics. The semantic metrics of a given computer program are calculated by use of the output of a knowledge-based analysis of the program, and are substantially more representative of software quality and more readily comprehensible from a human perspective than are the syntactic metrics.

Etzkorn, Letha H.↗

Constellation Program Lessons Learned: Detailed Lessons Learned - Volume 2

These lessons learned are part of a suite of hardware, software, test results, designs, knowledge base, and documentation that comprises the legacy of the Constellation Program. The context, summary information, and lessons learned are presented in a factual format, as known and described at the time. While our opinions might be discernable in the context, we have avoided all but factually sustainable statements. Statements should not be viewed as being either positive or negative; their value lies in what we did and what we learned that is worthy of passing on. The lessons include both "dos" and "don ts." In many cases, one person s "do" can be viewed as another person s "don t"; therefore, we have attempted to capture both perspectives when applicable and useful. While Volume I summarizes the views of those who managed the program, this Volume II encompasses the views at the working level, describing how the program challenges manifested in day-to-day activities. Here we see themes that were perhaps hinted at, but not completely addressed, in Volume I: unintended consequences of policies that worked well at higher levels but lacked proper implementation at the working level; long-term effects of the "generation gap" in human space flight development, the need to demonstrate early successes at the expense of thorough planning, and the consequences of problems and challenges not yet addressed because other problems and challenges were more immediate or manifest. Not all lessons learned have the benefit of being operationally vetted, since the program was cancelled shortly after Preliminary Design Review. We avoid making statements about operational consequences (with the exception of testing and test flights that did occur), but we do attempt to provide insight into how operational thinking influenced design and testing. The lessons have been formatted with a description, along with supporting information, a succinct statement of the lesson learned, and recommendations for future programs and projects that may be placed in similar circumstances.

Jennifer Rhatigan↗