Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “building engineers”

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 397 records · Page 22

Nuclear Thermal Rocket - Arc Jet Integrated System Model

In the post-shuttle era, space exploration is moving into a new regime. Commercial space flight is in development and is planned to take on much of the low earth orbit space flight missions. With the development of a heavy lift launch vehicle, the Space Launch, System, NASA has become focused on deep space exploration. Exploration into deep space has traditionally been done with robotic probes. More ambitious missions such as manned missions to asteroids and Mars will require significant technology development. Propulsion system performance is tied to the achievability of these missions and the requirements of other developing technologies that will be required. Nuclear thermal propulsion offers a significant improvement over chemical propulsion while still achieving high levels of thrust. Opportunities exist; however, to build upon what would be considered a standard nuclear thermal engine to attain improved performance, thus further enabling deep space missions. This paper discuss the modeling of a nuclear thermal system integrated with an arc jet to further augment performance. The performance predictions and systems impacts are discussed.

Taylor, Brian D.↗

Lessons Learned from the Flight Unit Testing of the Near Earth Asteroid Scout Flight System

The Near Earth Asteroid Scout flight mission is set to launch on the maiden voyage of the Space Launch System as a secondary payload. The spacecraft will be jettisoned in cis-lunar space and embark on an ambitious 2.5 year mission to image an asteroid. The spacecraft is uniquely equipped with an 85m2 solar sail as the main propulsion system. The monolithic sail system is designed to package within a 6U volume for launch and then deploy during flight. The NEA Scout team has presented in the past to the International Symposium on Solar Sailing topics related to the engineering development unit and design efforts to achieve flight hardware build. This paper will focus on the lessons learned from building and testing the NEA Scout flight system. Focus will be on the mechanical, software, and electrical interfaces as well as preparation for subsystem environmental tests, including thermal vacuum. Due to the unique design of the spacecraft, the solar sail subsystem was required to be located in the center of the spacecraft. This requirement lead to design challenges such as designing and accommodating critical cable harnesses to run through the center of the sail subsystem, packaging and deployment design of the sail subsystem, and integrated testing efforts through an avionics test bed to verify and validate a complete system architecture.

Lockett, Tiffany Russell↗

Data Science and the Knowledge Discovery Adventure

This talk will cover the important steps involved in the data science and knowledge discovery process: • Initial fact gathering (interview domain experts, review reports, articles, state-of-the-art) • Identify the problem (prediction, classification, statistical analysis, etc.) • Survey supporting data sources • Understand the data (numerical, categorical, text, sampling rate, data quality issues, etc.) • Selecting relevant features and sources • Acquire the data (set up agreements with the data stewards, APIs to download, etc.) • Merge data sources (temporal, spatial, common key, other ontologies...) • Feature Engineering (non linear domain knowledge or physics-based relationships) • Build data processing pipeline (may need to tap into data stream, develop parallel processing algorithm, federated learning etc.) • Build model and test (tune hyper-parameters, cross validation.) • Analyze/Validate results (do the results make sense. Does it answer the original question). • Deploy/Publish (Monitor and assess benefits)

Data science↗

Scalability in SLA lattice through lattice orientation and hybrid frame and plate architectures

Lightweighting has been a key goal for engineers and designers, with lattice structures widely explored as the building blocks for structural components. Cellular structure-inspired lattice truss frame designs made of struts, have been extensively studied. All plate-based lattice designs have superior mechanical performance. Limits in scalability occur from formation of closed pockets limiting uv curing in processes like stereolithography (SLA). We examine hybrid frame and plate body-centered cubic-simply cubic (BCC-SC) lattices under compression. Unit cells and scaled up lattice exhibit an increase in yield stress and modulus with the addition of plates. The loading direction on the hybrid frame and plate unit cells affected the magnitude of improvement. Simulations and measurements indicated that the optimal lightweight lattice was determined to be when two plates were placed opposite each other with plates buttressing the struts, inhibiting buckling of the struts aligned with the loading direction. This lattice resulted in 63% improvement in specific modulus, a 137% improvement in specific yield point, and a 360% improvement in specific energy absorption (SEA) and the scaled up 4 × 4 × 4 scaled-up structures, showed a 107%, 148%, and 297% in specific modulus, specific yield point, and SEA, respectively A combined stretching-bending behavior was identified in optimal orientations reflecting the delayed buckling mechanism paired to a rising stress-strain curve past the elastic yield indicating bending resistance. The mass moment of inertia was found to be a key parameter correlating optimum orientation for the same number of plates added to the BCC-SC frame.

Mahan Ghosh↗

SIG: Multiple Views on Safety-Critical Automation: Aircraft, Autonomous Vehicles, Air Traffic Management and Satellite Ground Segments Perspectives

This SIG focuses on the engineering of automation in interactive critical systems. Automation has already been studied in a number of (sub-) disciplines and application fields: design, human factors, psychology, (software) engineering, aviation, health care, games. One distinguishing feature of the area we are focusing on is that in the field of interactive critical systems properties such as reliability, dependability, fault tolerance are as important as usability, user experience or overall acceptance issues. The SIG targets at two problem areas: first the engineering of the user interaction with (partly-) autonomous systems: how to design, build and assess autonomous behavior, especially in cases where there is a need to represent on the user interface both autonomous and interactive objects. An example of such integration is the representation of an unmanned aerial vehicle (UAV) (where no direct interaction is possible), together with aircrafts (that have to be instructed by an air traffic controller to avoid the UAV). Second the design and engineering of user interaction in general for autonomous objects/systems (for example a cruise control in a car or an autopilot in an aircraft). The goal of the SIG is to raise interest in the CHI community on the general aspects of automation and to identify a community of researchers and practitioners interested in those increasingly prominent issues of interfaces towards (semi)-autonomous systems. The expected audience should be interested in addressing the issues of integration of mainly unconnected research domains to formulate a new joint research agenda.

human-automation interaction↗

Multiple Views on Safety-Critical Automation: Aircraft, Autonomous Vehicles, Air Traffic Management and Satellite Ground Segments Perspectives

This SIG focuses on the engineering of automation in interactive critical systems. Automation has already been studied in a number of (sub-) disciplines and application fields: design, human factors, psychology, (software) engineering, aviation, health care, games. One distinguishing feature of the area we are focusing on is that in the field of interactive critical systems properties such as reliability, dependability, fault-tolerance are as important as usability, user experience or overall acceptance issues. The SIG targets at two problem areas: first the engineering of the user interaction with (partly-) autonomous systems: how to design, build and assess autonomous behavior, especially in cases where there is a need to represent on the user interface both autonomous and interactive objects. An example of such integration is the representation of an unmanned aerial vehicle (UAV) (where no direct interaction is possible), together with aircrafts (that have to be instructed by an air traffic controller to avoid the UAV). Second the design and engineering of user interaction in general for autonomous objects systems (for example a cruise control in a car or an autopilot in an aircraft). The goal of the SIG is to raise interest in the CHI community on the general aspects of automation and to identify a community of researchers and practitioners interested in those increasingly prominent issues of interfaces towards (semi)-autonomous systems. The expected audience should be interested in addressing the issues of integration of mainly unconnected research domains to formulate a new joint research agenda.

safety-critical automation↗

Structural Requirements for the Space Propulsion Engine Systems

In January 2004, the National Aeronautics and Space Administration (NASA) was given a vision for Space Exploration by President Bush, setting our sight on a bold new path to go back to the Moon, then to Mars and beyond. As NASA gets ready to meet the vision set by President Bush, failures are not an option. Reliability of the propulsion engine systems will play an important role in establishing an overall safe and reliable operation of these new space systems. A new standard, NASA-STD-5012, Strength and Life Assessment for Space Propulsion System Engines, has been developed to provide structural requirements for assessment of the propulsion systems engine. This standard is a complement to the current NASA-wide standard NASA-STD-5001, Structural Design and Test Factors of Safety for Spaceflight Hardware, which excluded the requirement for the engine systems (rotatory structures) along with pressure vessels. As developed, this document builds on the heritage of the multiple industrial standards related to strength and life assessment of the structures. For assuring a safe and reliable operation of a product and/or mission, establishing a set of structural assessment requirements is a key ingredient. Hence, a concentrated effort was made to improve the requirements where there are known lessons learned during the design, test, and operation phases of the Space Shuttle Main Engine (SSME) and other engine development programs. Requirements delineated in this standard are also applicable for the reusable and/or human missions. It shall be noted that "reliability of a system cannot be tested and inspected but can only be achieved if it is first designed into a system." Hence, these strength and life assessment requirements for the space propulsion system engines shall be used along with other good engineering practices, requirements, and policies.

Aggarwal, Pravin K.↗

Intelligent Agents for Design and Synthesis Environments: My Summary

This presentation gives a summary of intelligent agents for design synthesis environments. We'll start with the conclusions, and work backwards to justify them. First, an important assumption is that agents (whatever they are) are good for software engineering. This is especially true for software that operates in an uncertain, changing environment. The "real world" of physical artifacts is like that: uncertain in what we can measure, changing in that things are always breaking down, and we must interact with non-software entities. The second point is that software engineering techniques can contribute to good design. There may have been a time when we wanted to build simple artifacts containing little or no software. But modern aircraft and spacecraft are complex, and rely on a great deal of software. So better software engineering leads to better designed artifacts, especially when we are designing a series of related artifacts and can amortize the costs of software development. The third point is that agents are especially useful for design tasks, above and beyond their general usefulness for software engineering, and the usefulness of software engineering to design.

Norvig, Peter↗

1025:1 Area Ratio Nozzle Evaluated at High Combustion Chamber Pressure

A recently completed experimental test program obtained performance data on an optimally contoured nozzle with an exit-to-throat area ratio of 1025:1 and on a truncated version of this nozzle with an area ratio of 440:1. The nozzles were tested with gaseous hydrogen and liquid oxygen propellants at combustion chamber pressures of 12.4 to 16.5 mPa (1800 to 2400 psia). Testing was conducted in the altitude test capsule at the NASA Lewis Research Center's Rocket Engine Test Facility (RETF), and results were compared with analytical performance predictions. This testing builds on previous work with this nozzle at Lewis, where testing was completed at nominal chamber pressure of 350 psia. High-area-ratio nozzles have long been sought as a means to increase the performance of spacebased rocket engines. However, as the area ratio increases, the physical size and weight of the nozzle also increase. As a result, engine and vehicle designers must make tradeoffs between nozzle size and performance enhancement. Until this test program, very little experimental data existed on the performance of the high-area-ratio nozzles used in rocket engine designs. The computer codes being used by rocket engine designers rely on data extrapolated from tests of low-area-ratio nozzles, and these extrapolations do not always provide the accuracy needed for a reliable design assessment. Therefore, we conducted this high-area-ratio nozzle testing program to provide performance data for use in rocket engine design and analysis computer codes. The nozzle had a nominal 2.54-cm- (1-in.-) diameter throat, an exit diameter of 81.3-cm (32.0-in.) at an exit-to-throat area ratio of 1025, and a length of 128.6 cm (50.6 in.). Testing was conducted in an altitude test capsule to simulate the static pressure at altitude by vacuum pumping. Data such as propellant mass flow, oxidizer-to-fuel mixture, and thrust were measured. These measurements were then used to calculate performance factors such as the thrust coefficient, the characteristic exhaust velocity efficiency, and the vacuum specific impulse. In addition, the nozzle temperature was measured to calculate the amount of heat transferred from the combustion gases to the nozzle.

Source record↗

Virtually Out of This World!

Ames Research Center granted Reality Capture Technologies (RCT), Inc., a license to further develop NASA's Mars Map software platform. The company incorporated NASA#s innovation into software that uses the Virtual Plant Model (VPM)(TM) to structure, modify, and implement the construction sites of industrial facilities, as well as develop, validate, and train operators on procedures. The VPM orchestrates the exchange of information between engineering, production, and business transaction systems. This enables users to simulate, control, and optimize work processes while increasing the reliability of critical business decisions. Engineers can complete the construction process and test various aspects of it in virtual reality before building the actual structure. With virtual access to and simulation of the construction site, project personnel can manage, access control, and respond to changes on complex constructions more effectively. Engineers can also create operating procedures, training, and documentation. Virtual Plant Model(TM) is a trademark of Reality Capture Technologies, Inc.

Source record↗

Launching to the Moon, Mars, and Beyond

America is returning to the Moon in preparation for the first human footprint on Mars, guided by the U.S. Vision for Space Exploration. This presentation will discuss NASA's mission today, the reasons for returning to the Moon and going to Mars, and how NASA will accomplish that mission. The primary goals of the Vision for Space Exploration are to finish the International Space Station, retire the Space Shuttle, and build the new spacecraft needed to return people to the Moon and go to Mars. Unlike the Apollo program of the 1960s, this phase of exploration will be a journey, not a race. In 1966, the NASA's budget was 4 percent of federal spending. Today, with 6/10 of 1 percent of the budget, NASA must incrementally develop the vehicles, infrastructure, technology, and organization to accomplish this goal. Fortunately, our knowledge and experience are greater than they were 40 years ago. NASA's goal is a return to the Moon by 2020. The Moon is the first step to America's exploration of Mars. Many questions about the Moon's history and how its history is linked to that of Earth remain even after the brief Apollo explorations of the 1960s and 1970s. This new venture will carry more explorers to more diverse landing sites with more capable tools and equipment. The Moon also will serve as a training ground in several respects before embarking on the longer, more perilous trip to Mars. The journeys to the Moon and Mars will require a variety of vehicles, including the Ares I Crew Launch Vehicle, the Ares V Cargo Launch Vehicle, the Orion Crew Exploration Vehicle, and the Lunar Surface Access Module. The architecture for the lunar missions will use one launch to ferry the crew into orbit on the Ares I and a second launch to orbit the lunar lander and the Earth Departure Stage to send the lander and crew vehicle to the Moon. In order to reach the Moon and Mars within a lifetime and within budget, NASA is building on proven hardware and decades of experience derived from the Apollo Saturn, Space Shuttle, and contemporary commercial launch vehicle programs. Less than one year after the Exploration Launch Projects Office was formed at NASA's Marshall Space Flight Center, engineers are testing engine components, firing test rocket motors, refining vehicle designs in wind tunnel tests, and building hardware for the first flight test of Ares I, scheduled for spring 2009. The Vision for Exploration will require this nation to develop tools, machines, materials, and processes never before invented, technologies and capabilities that can be turned over to the private sector to benefit nearly all aspects of life on Earth. This new pioneering venture, as did the Apollo Program before it, will contribute to America's economic leadership, national security, and technological global competitiveness and serve as an inspiration for all its citizens.

Sumrall, John P.↗

Rocket University at KSC

"Rocket University" is an exciting new initiative at Kennedy Space Center led by NASA's Engineering and Technology Directorate. This hands‐on experience has been established to develop, refine & maintain targeted flight engineering skills to enable the Agency and KSC strategic goals. Through "RocketU", KSC is developing a nimble, rapid flight engineering life cycle systems knowledge base. Ongoing activities in RocketU develop and test new technologies and potential customer systems through small scale vehicles, build and maintain flight experience through balloon and small‐scale rocket missions, and enable a revolving fresh perspective of engineers with hands on expertise back into the large scale NASA programs, providing a more experienced multi‐disciplined set of systems engineers. This overview will define the Program, highlight aspects of the training curriculum, and identify recent accomplishments and activities.

Training↗

Electronics and Software Engineer for Robotics Project Intern

I was assigned to mentor high school students for the 2017 First Robotics Competition. Using a team based approach, I worked with the students to program the robot and applied my electrical background to build the robot from start to finish. I worked with students who had an interest in electrical engineering to teach them about voltage, current, pulse width modulation, solenoids, electromagnets, relays, DC motors, DC motor controllers, crimping and soldering electrical components, Java programming, and robotic simulation. For the simulation, we worked together to generate graphics files, write simulator description format code, operate Linux, and operate SOLIDWORKS. Upon completion of the FRC season, I transitioned over to providing full time support for the LCS hardware team. During this phase of my internship I helped my co-intern write test steps for two networking hardware DVTs , as well as run cables and update cable running lists.

Teijeiro, Antonio↗

A fuzzy case based reasoning tool for model based approach to rocket engine health monitoring

In this system we develop a fuzzy case based reasoner that can build a case representation for several past anomalies detected, and we develop case retrieval methods that can be used to index a relevant case when a new problem (case) is presented using fuzzy sets. The choice of fuzzy sets is justified by the uncertain data. The new problem can be solved using knowledge of the model along with the old cases. This system can then be used to generalize the knowledge from previous cases and use this generalization to refine the existing model definition. This in turn can help to detect failures using the model based algorithms.

Krovvidy, Srinivas↗

Sequencing System Building Blocks: Using a Component Architecture for Sequencing Software

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require a new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group. The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a set of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

multi mission planning↗

Sequence System Building Blocks: Using a Component Architecture for Sequencing Software

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require an new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group . The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a act of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

flexible architectures↗

Geographic Information Systems and Web Page Development

The Facilities Engineering and Architectural Branch is responsible for the design and maintenance of buildings, laboratories, and civil structures. In order to improve efficiency and quality, the FEAB has dedicated itself to establishing a data infrastructure based on Geographic Information Systems, GIS. The value of GIS was explained in an article dating back to 1980 entitled "Need for a Multipurpose Cadastre" which stated, "There is a critical need for a better land-information system in the United States to improve land-conveyance procedures, furnish a basis for equitable taxation, and provide much-needed information for resource management and environmental planning." Scientists and engineers both point to GIS as the solution. What is GIS? According to most text books, Geographic Information Systems is a class of software that stores, manages, and analyzes mapable features on, above, or below the surface of the earth. GIS software is basically database management software to the management of spatial data and information. Simply put, Geographic Information Systems manage, analyze, chart, graph, and map spatial information. GIS can be broken down into two main categories, urban GIS and natural resource GIS. Further still, natural resource GIS can be broken down into six sub-categories, agriculture, forestry, wildlife, catchment management, archaeology, and geology/mining. Agriculture GIS has several applications, such as agricultural capability analysis, land conservation, market analysis, or whole farming planning. Forestry GIs can be used for timber assessment and management, harvest scheduling and planning, environmental impact assessment, and pest management. GIS when used in wildlife applications enables the user to assess and manage habitats, identify and track endangered and rare species, and monitor impact assessment.

Reynolds, Justin↗

Geographic Information Systems and Web Page Development

The Facilities Engineering and Architectural Branch is responsible for the design and maintenance of buildings, laboratories, and civil structures. In order to improve efficiency and quality, the FEAB has dedicated itself to establishing a data infrastructure based on Geographic Information Systems, GIs. The value of GIS was explained in an article dating back to 1980 entitled "Need for a Multipurpose Cadastre which stated, "There is a critical need for a better land-information system in the United States to improve land-conveyance procedures, furnish a basis for equitable taxation, and provide much-needed information for resource management and environmental planning." Scientists and engineers both point to GIS as the solution. What is GIS? According to most text books, Geographic Information Systems is a class of software that stores, manages, and analyzes mapable features on, above, or below the surface of the earth. GIS software is basically database management software to the management of spatial data and information. Simply put, Geographic Information Systems manage, analyze, chart, graph, and map spatial information. At the outset, I was given goals and expectations from my branch and from my mentor with regards to the further implementation of GIs. Those goals are as follows: (1) Continue the development of GIS for the underground structures. (2) Extract and export annotated data from AutoCAD drawing files and construct a database (to serve as a prototype for future work). (3) Examine existing underground record drawings to determine existing and non-existing underground tanks. Once this data was collected and analyzed, I set out on the task of creating a user-friendly database that could be assessed by all members of the branch. It was important that the database be built using programs that most employees already possess, ruling out most AutoCAD-based viewers. Therefore, I set out to create an Access database that translated onto the web using Internet Explorer as the foundation. After some programming, it was possible to view AutoCAD files and other GIS-related applications on Internet Explorer, while providing the user with a variety of editing commands and setting options. I was also given the task of launching a divisional website using Macromedia Flash and other web- development programs.

Reynolds, Justin↗