Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “drawings”

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 145 records · Page 8

A 150 and 300 kW lightweight diesel aircraft engine design study

The diesel engine was reinvestigated as an aircraft powerplant through design study conducted to arrive at engine configurations and applicable advanced technologies. Two engines are discussed, a 300 kW six-cylinder engine for twin engine general aviation aircraft and a 150 kW four-cylinder engine for single engine aircraft. Descriptions of each engine include concept drawings, a performance analysis, stress and weight data, and a cost study. This information was used to develop two airplane concepts, a six-place twin and a four-place single engine aircraft. The aircraft study consists of installation drawings, computer generated performance data, aircraft operating costs, and drawings of the resulting airplanes. The performance data show a vast improvement over current gasoline-powered aircraft.

Brouwers, A. P.↗

Lightweight diesel aircraft engines for general aviation

A methodical design study was conducted to arrive at new diesel engine configurations and applicable advanced technologies. Two engines are discussed and the description of each engine includes concept drawings. A performance analysis, stress and weight prediction, and a cost study were also conducted. This information was then applied to two airplane concepts, a six-place twin and a four-place single engine aircraft. The aircraft study consisted of installation drawings, computer generated performance data, aircraft operating costs and drawings of the resulting airplanes. The performance data shows a vast improvement over current gasoline-powered aircraft. At the completion of this basic study, the program was expanded to evaluate a third engine configuration. This third engine incorporates the best features of the original two, and its design is currently in progress. Preliminary information on this engine is presented.

Berenyi, S. G.↗

Orbit Transfer Vehicle (OTV) advanced expander cycle engine point design study. Task 7: Engine data summary

A performance optimized engine system design for a man-rated advanced LOX/hydrogen expander cycle engine was investigated. The data are presented in tables, figures, and drawings. The following categories of data for the advanced expander cycle engine are presented: engine operating specification and pressure schedule; engine system layout drawing; major component layout drawings, including thrust chamber and nozzle, extendible nozzle actuating mechanism and seal, LOX turbopump, LOX boost pump, hydrogen turbopump, hydrogen boost pump, and propellant control valves; engine performance and service life prediction; engine weight; and engine envelope. The data represent updates based upon current results from the design and analyses tasks performed under contract. Futher iterations in the designs and data can be expected as the advanced expander cycle engine design matures.

Christensen, K. L.↗

Stress analysis of the space telescope focal plane structure joint

Two major efforts were begun concerning the Space Telescope focal plane structure joint. The 3-D solid finite element modeling of the bipod flexure plate was carried out. Conceptual models were developed for the load transfer through the three major bolts to the flexure plate. The flexure plate drawings were reconstructed using DADAM for the purpose of developing a file from which the coordinates of any point on the flexure plate could be determined and also to locate the attachment points of the various components which connect with the flexure plate. For modeling convenience the CADAM drawing of the flexure plate has been divided into several regions which will be subdivided into finite elements using MSGMESH, which is a finite element mesh generator available with MSC/NASTRAN. In addition to the CADAM work on the flexure plate, an effort was also begun to develop computer aided drawings of the peripheral beam which will be used to assist in modeling the connection between it and the flexure plate.

Foster, W. A., Jr.↗

Successful expert systems for space shuttle payload integration

Expert systems are successfully applied to solve recurring NASA Space Shuttle orbiter payload integration problems. Recurrence of these problems is the result of each Space Shuttle mission being unique. The NASA Space Shuttle orbiter was designed to be extremely flexible in its ability to handle many types and combinations of satellites and experiments. This flexibility results in different and unique engineering resource requirements for each of the payload satellites and experiments. The first successful expert system to be applied to these problems was the Orbiter Payload Bay Cabling Expert System (EXCABL), developed at Rockwell International Space Transportation Systems Division. The operational version of EXCABL was delivered in 1986 and successfully solved the payload electrical support services cabling layout problem. As a result of this success, a second expert system, Expert Drawing Matching System (EXMATCH), was developed to generate a list of the reusable installation drawings available for each EXCABL solution. EXMATCH went operational in 1987. As a result of these initial successes, the need for a third expert system was defined and is awaiting development. This new Expert System, called Technical Order Listing Expert System (EXTOL), will generate a list of all the applicable reusable installation drawings available to support the total payload bay mission provisioning and installation effort. This paper describes these expert systems, the individual problems that they were designed to solve, their individual solutions, and the degree of success achieved. These expert systems' instantiate the applicability of this technology to the solution of real-world Space Shuttle payload integration problems.

Morris, Keith↗

The 28-entity IGES test file results using ComputerVision CADDS 4X

The investigation was based on the following steps: (1) Read the 28 Entity IGES (Initial Graphics Exchange Specification) Test File into the CAD data base with the IGES post-processor; (2) Make the modifications to the displayed geometries, which should produce the normalized front view and the drawing entity defined display; (3) Produce the drawing entity defined display of the file as it appears in the CAD system after modification to the geometry; (4) Translate the file back to IGES format using IGES pre-processor; (5) Read the IGES file produced by the pre-processor back into the CAD data base; (6) Produce another drawing entity defined display of the CAD display; and (7) Compare the plots resulting from steps 3 and 6 - they should be identical to each other.

Kuan, Anchyi↗

ICADS: A cooperative decision making model with CLIPS experts

A cooperative decision making model is described which is comprised of six concurrently executing domain experts coordinated by a blackboard control expert. The focus application field is architectural design, and the domain experts represent consultants in the area of daylighting, noise control, structural support, cost estimating, space planning, and climate responsiveness. Both the domain experts and the blackboard were implemented as production systems, using an enhanced version of the basic CLIPS package. Acting in unison as an Expert Design Advisor, the domain and control experts react to the evolving design solution progressively developed by the user in a 2-D CAD drawing environment. A Geometry Interpreter maps each drawing action taken by the user to real world objects, such as spaces, walls, windows, and doors. These objects, endowed with geometric and nongeometric attributes, are stored as frames in a semantic network. Object descriptions are derived partly from the geometry of the drawing environment and partly from knowledge bases containing prototypical, generalized information about the building type and site conditions under consideration.

Pohl, Jens↗

NASA's Participation in the National Computational Grid

Over the last several years it has become evident that the character of NASA's supercomputing needs has changed. One of the major missions of the agency is to support the design and manufacture of aero- and space-vehicles with technologies that will significantly reduce their cost. It is becoming clear that improvements in the process of aerospace design and manufacturing will require a high performance information infrastructure that allows geographically dispersed teams to draw upon resources that are broader than traditional supercomputing. A computational grid draws together our information resources into one system. We can foresee the time when a Grid will allow engineers and scientists to use the tools of supercomputers, databases and on line experimental devices in a virtual environment to collaborate with distant colleagues. The concept of a computational grid has been spoken of for many years, but several events in recent times are conspiring to allow us to actually build one. In late 1997 the National Science Foundation initiated the Partnerships for Advanced Computational Infrastructure (PACI) which is built around the idea of distributed high performance computing. The Alliance lead, by the National Computational Science Alliance (NCSA), and the National Partnership for Advanced Computational Infrastructure (NPACI), lead by the San Diego Supercomputing Center, have been instrumental in drawing together the "Grid Community" to identify the technology bottlenecks and propose a research agenda to address them. During the same period NASA has begun to reformulate parts of two major high performance computing research programs to concentrate on distributed high performance computing and has banded together with the PACI centers to address the research agenda in common.

Feiereisen, William J.↗

Information Technology Support in the 8000 Directorate

My summer internship was spent supporting various projects within the Environmental Management Office and Glenn Safety Office. Mentored by Eli Abumeri, I was trained in areas of Information Technology such as: Servers, printers, scanners, CAD systems, Web, Programming, and Database Management, ODIN (networking, computers, and phones). I worked closely with the Chemical Sampling and Analysis Team (CSAT) to redesign a database to more efficiently manage and maintain data collected for the Drinking Water Program. This Program has been established for over fifteen years here at the Glenn Research Center. It involves the continued testing and retesting of all drinking water dispensers. The quality of the drinking water is of great importance and is determined by comparing the concentration of contaminants in the water with specifications set forth by the Environmental Protection Agency (EPA) in the Safe Drinking Water Act (SDWA) and its 1986 and 1991 amendments. The Drinking Water Program consists of periodic testing of all drinking water fountains and sinks. Each is tested at least once every 2 years for contaminants and naturally occurring species. The EPA's protocol is to collect an initial and a 5 minute draw from each dispenser. The 5 minute draw is what is used for the maximum contaminant level. However, the CS&AT has added a 30 second draw since most individuals do not run the water 5 minutes prior to drinking. This data is then entered into a relational Microsoft Access database. The database allows for the quick retrieval of any test@) done on any dispenser. The data can be queried by building number, date or test type, and test results are documented in an analytical report for employees to read. To aid with the tracking of recycled materials within the lab, my help was enlisted to create a database that could make this process less cumbersome and more efficient. The date of pickup, type of material, weight received, and unit cost per recyclable. This information could then calculate the dollar amount generated by the recycling of certain materials. This database will ultimately prove useful in determining the amounts of materials consumed by the lab and will help serve as an indicator potential overuse.

FROM↗

Project Interface Requirements Process Including Shuttle Lessons Learned

Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

Bauch, Garland T.↗

Decal Process Document and Catalog

The Decal Process Document and Catalog, JSC 27260 is the standard flight decal catalog, complete with illustrations and part numbers. As hardware developers identify labels that have common applicability across end items, these labels can be evaluated for "standard decal classification" and entered into the decal catalog for general use. The hardware developer must have a label design that meets current, applicable labeling requirements, and submit to the Decal Design and Production Facility (DDPF) as a standard label candidate. Upon approval, the label will be added to the decal catalog. The Decal Process Document and Catalog provides a selection of decals from which the NASA and NASA contractor customers can easily order. The decals shown in the catalog have been previously produced and have released engineering/fabrication drawings on file in the (DDPF). A released drawing is required before a decal can be produced or placed into the catalog. Some decals included in the catalog have a common applicability and are used in various NASA vehicles/habitats. It is the intent of the DDPF to maintain this catalog as a "living document" to which decals/placards can be added as they are repeatedly used. The advantage of identifYing flight decals in this catalog is that a released drawing is already in place, and the products will be flight certified.

Source record↗

Habitat Utilization Assessment - Building in Behaviors

Habitability, and the associated architectural and design attributes of an environment, is a powerful performance shaping factor. By identifying how inhabitants use an area, we can draw conclusions about what design or architectural attributes cause what behaviors and systematically design in desired human performance. We are analyzing how a crew uses a long duration habitat and work environment during a four-day underwater mission and identifying certain architectural and design attributes that are related to, and potential enablers of, certain crew behaviors. By identifying how inhabitants use the habitat, we can draw conclusions about what habitability attributes cause what behaviors and systematically design in desired human performance (applicable to NASA's Bioastronautics Human Behavior and Performance Critical Path Roadmap question 6.12). This assessment replicates a methodology reported in a chapter titled "Sociokinetic Analysis as a Tool for Optimization of Environmental Design" by C. Adams.' That study collected video imagery of certain areas of a closed habitat during a 91 day test and from that data calculated time spent in different volumes during the mission, and characterized the behaviors occurring in certain habitat volumes thus concluding various rules for design of such habitats. This study assesses the utilization of the Aquarius Habitat, an underwater station, which will support six Aquanauts for a fourteen-day mission during which the crew will perform specific scientific and engineering studies. Video is recorded for long uninterrupted periods of time during the mission and from that data the time spent in each area is calculated. In addition, qualitative and descriptive analysis of the types of behaviors in each area is performed with the purpose of identifying any behaviors that are not typical of a certain area. If a participant uses an area in a way different from expected, a subsequent analysis of the features of that area may result in conclusions of performance shaping factors. With the addition of this study, we can make comparisons between the two different habitats and begin drawing correlation judgments about design features and behavior. Ideally, this methodology should be repeated in additional Aquarius missions and other analog environments because the real information will come from comparisons between habitats.

Whitmore, Mihriban↗

Eliminating crystals in non-oxide optical fiber preforms and optical fibers

A method is provided for eliminating crystals in non-oxide optical fiber preforms as well as optical fibers drawn therefrom. The optical-fiber-drawing axis of the preform is aligned with the force of gravity. A magnetic field is applied to the preform as it is heated to at least a melting temperature thereof. The magnetic field is applied in a direction that is parallel to the preform's optical-fiber-drawing axis. The preform is then cooled to a temperature that is less than a glass transition temperature of the preform while the preform is maintained in the magnetic field. When the processed preform is to have an optical fiber drawn therefrom, the preform's optical-fiber-drawing axis is again aligned with the force of gravity and a magnetic field is again applied along the axis as the optical fiber is drawn from the preform.

LaPointe, Michael R.↗

Ares Upper Stage Processes to Implement Model Based Design - Going Paperless

Computer-Aided Design (CAD) has all but replaced the drafting board for design work. Increased productivity and accuracy should be natural outcomes of using CAD. Going from paper drawings only to paper drawings based on CAD models to CAD models and no drawings, or Model Based Design (MBD), is a natural progression in today?s world. There are many advantages to MBD over traditional design methods. To make the most of those advantages, standards should be in place and the proper foundation should be laid prior to transitioning to MBD. However, without a full understanding of the implications of MBD and the proper control of the data, the advantages are greatly diminished. Transitioning from a paper design world to an electronic design world means re-thinking how information gets controlled at its origin and distributed from one point to another. It means design methodology is critical, especially for large projects. It means preparation of standardized parts and processes as well as strong communication between all parties in order to maximize the benefits of MBD.

Gregory, Melanie↗

Friction modifier using adherent metallic multilayered or mixed element layer conversion coatings

A process for creating conversion coatings and spin, drawing, and extrusion finishes for surfaces, wherein the conversion coatings and spin, drawing, and extrusion finishes contain potassium, phosphorus, nitrogen, silicon, and one or more non-alkaline metals. The process comprises forming a first aqueous solution of silicate, potassium hydroxide, and ammonium hydroxide; forming a second aqueous solution of water, phosphoric acid, ammonium hydroxide, an alkali metal hydroxide, and one or more non-alkaline metals, and then combining the first solution with the second solution to form a final solution. This final solution forms an anti-friction multi-layer conversion coating or a spin, drawing, and extrusion finish on a surface when applied to the surface, either directly or as an additive in lubricating fluids.

Schramm, Harry F.↗

Friction Modifier Using Adherent Metallic Multilayered or Mixed Element Layer Conversion Coatings

A process for creating conversion coatings and spin, drawing, and extrusion finishes for surfaces, wherein the conversion coatings and spin, drawing, and extrusion finishes contain potassium, phosphorus, nitrogen, and one or more non-alkaline metals and/or one or more metalloids. The process comprises forming an aqueous solution of water, phosphoric acid or sulfuric acid, ammonium hydroxide, an alkali metal hydroxide, and one or more non-alkaline metals and/or one or more metalloids. The aqueous solution forms an anti-friction multilayer conversion and/or mixed element coating or a spin, drawing, and extrusion finish on a surface when applied to the surface, either directly without the use of applied external electromotive force, or as an additive in lubricating fluids.

Schramm, Harry F.↗

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗

Lightning Protection and Structural Bonding for the B2 Test Stand

With the privatization of the space industry, NASA has entered a new era. To explore deeper parts of the solar system, NASA is developing a new spacecraft, the Space Launch System (SLS), capable of reaching these destinations, such as an asteroid or Mars. However, the test stand that is capable of testing the stage has been unused for many years. In addition to the updating/repair of the stand, more steel is being added to fully support the SLS. With all these modifications, the lightning protection system must be brought up to code to assure the protection of all personnel and assets. Structural bonding is a part of the lightning protection system. The focus of this project was to assure proper structural bonding. To begin, all relevant technical standards and the construction specifications were reviewed. This included both the specifications for the lightning protection and for general construction. The drawings were reviewed as well. From the drawings, bolted structural joints were reviewed to determine whether bonding was necessary. Several bolted joints were determined to need bonding according to the notes in the drawings. This exceeds the industry standards. The bolted joints are an electrically continuous joint. During tests, the stand experiences heavy vibration that may weaken the continuity of the bolted joint. Therefore, the secondary bonding is implemented to ensure that the structural joint has low resistance. If the structural joint has a high resistance because of corrosion, a potential gradient can occur that can cause a side flash. Damage, injury, or death can occur from a side flash so they are to be prevented. A list of the identified structural joints was compiled and sent to the contractor to be bonded. That covers the scope of this project.

Kinard, Brandon↗