Search NASA⌕ Search

SEARCH · Search NASA

Results for “Statement of Feasibility”

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.

33 records · Page 2

Applications of fuzzy theories to multi-objective system optimization

Most of the computer aided design techniques developed so far deal with the optimization of a single objective function over the feasible design space. However, there often exist several engineering design problems which require a simultaneous consideration of several objective functions. This work presents several techniques of multiobjective optimization. In addition, a new formulation, based on fuzzy theories, is also introduced for the solution of multiobjective system optimization problems. The fuzzy formulation is useful in dealing with systems which are described imprecisely using fuzzy terms such as, 'sufficiently large', 'very strong', or 'satisfactory'. The proposed theory translates the imprecise linguistic statements and multiple objectives into equivalent crisp mathematical statements using fuzzy logic. The effectiveness of all the methodologies and theories presented is illustrated by formulating and solving two different engineering design problems. The first one involves the flight trajectory optimization and the main rotor design of helicopters. The second one is concerned with the integrated kinematic-dynamic synthesis of planar mechanisms. The use and effectiveness of nonlinear membership functions in fuzzy formulation is also demonstrated. The numerical results indicate that the fuzzy formulation could yield results which are qualitatively different from those provided by the crisp formulation. It is felt that the fuzzy formulation will handle real life design problems on a more rational basis.

Rao, S. S.↗

Knowledge-Based Manufacturing and Structural Design for a High Speed Civil Transport

The aerospace industry is currently addressing the problem of integrating manufacturing and design. To address the difficulties associated with using many conventional procedural techniques and algorithms, one feasible way to integrate the two concepts is with the development of an appropriate Knowledge-Based System (KBS). The authors present their reasons for selecting a KBS to integrate design and manufacturing. A methodology for an aircraft producibility assessment is proposed, utilizing a KBS for manufacturing process selection, that addresses both procedural and heuristic aspects of designing and manufacturing of a High Speed Civil Transport (HSCT) wing. A cost model is discussed that would allow system level trades utilizing information describing the material characteristics as well as the manufacturing process selections. Statements of future work conclude the paper.

Marx, William J.↗

Feasibility study for a numerical aerodynamic simulation facility. Volume 3: FMP language specification/user manual

The manual is intended to show the revisions and additions to the current STAR FORTRAN. The changes are made to incorporate an FMP (Flow Model Processor) for use in the Numerical Aerodynamic Simulation Facility (NASF) for the purpose of simulating fluid flow over three-dimensional bodies in wind tunnel environments and in free space. The FORTRAN programming language for the STAR-100 computer contains both CDC and unique STAR extensions to the standard FORTRAN. Several of the STAR FORTRAN extensions to standard FOR-TRAN allow the FORTRAN user to exploit the vector processing capabilities of the STAR computer. In STAR FORTRAN, vectors can be expressed with an explicit notation, functions are provided that return vector results, and special call statements enable access to any machine instruction.

Kenner, B. G.↗

ATD-1 Avionics Phase 2: Post-Flight Data Analysis Report

This report aims to satisfy Air Traffic Management Technology Demonstration - 1 (ATD-1) Statement of Work (SOW) 3.6.19 and serves as the delivery mechanism for the analysis described in Annex C of the Flight Test Plan. The report describes the data collected and derived as well as the analysis methodology and associated results extracted from the data set collected during the ATD-1 Flight Test. All analyses described in the SOW were performed and are covered in this report except for the analysis of Final Approach Speed and its effect on performance. This analysis was de-prioritized and, at the time of this report, is not considered feasible in the schedule and costs remaining.

Scharl, Julien↗

A continuing program for technology transfer to the apparel industry

A six month program has been carried out to investigate various mechanisms for transferring technology to industry. This program has focused on transfer to the apparel industry through the Apparel Research Foundation. The procedure was to analyze the problem, obtain potentially relevant aerospace technology, and then transfer this technology to the industry organization. This was done in a specific case. Technology was identified relevant to stitchless joining, and this technology was transferred to the Apparel Research Foundation. The feasibility and ground rules for carrying out such activities on a broader scale were established. A specific objective was to transfer new technology from the industry organization to the industry itself. This required the establishment of an application engineering program. Another transfer mechanism tested was publication of solutions to industry problems in a format familiar to the industry. This is to be distinguished from circulating descriptions of new technology. Focus is on the industry problem and the manager is given a formula for solving it that he can follow. It was concluded that this mechanism can complement the problem statement approach to technology transfer. It is useful in achieving transfer when a large amount of application engineering is not necessary. A wide audience is immediately exposed to the technology. On the other hand, the major manufacturing problems which require a sophisticated technical solution integrating many innovations are less likely to be helped.

Clingman, W. H.↗

Reduction of Subjective and Objective System Complexity

Occam's razor is often used in science to define the minimum criteria to establish a physical or philosophical idea or relationship. Albert Einstein is attributed the saying "everything should be made as simple as possible, but not simpler". These heuristic ideas are based on a belief that there is a minimum state or set of states for a given system or phenomena. In looking at system complexity, these heuristics point us to an idea that complexity can be reduced to a minimum. How then, do we approach a reduction in complexity? Complexity has been described as a subjective concept and an objective measure of a system. Subjective complexity is based on human cognitive comprehension of the functions and inter relationships of a system. Subjective complexity is defined by the ability to fully comprehend the system. Simplifying complexity, in a subjective sense, is thus gaining a deeper understanding of the system. As Apple's Jonathon Ive has stated," It's not just minimalism or the absence of clutter. It involves digging through the depth of complexity. To be truly simple, you have to go really deep". Simplicity is not the absence of complexity but a deeper understanding of complexity. Subjective complexity, based on this human comprehension, cannot then be discerned from the sociological concept of ignorance. The inability to comprehend a system can be either a lack of knowledge, an inability to understand the intricacies of a system, or both. Reduction in this sense is based purely on a cognitive ability to understand the system and no system then may be truly complex. From this view, education and experience seem to be the keys to reduction or eliminating complexity. Objective complexity, is the measure of the systems functions and interrelationships which exist independent of human comprehension. Jonathon Ive's statement does not say that complexity is removed, only that the complexity is understood. From this standpoint, reduction of complexity can be approached in finding the optimal or 'best balance' of the system functions and interrelationships. This is achievable following von Bertalanffy's approach of describing systems as a set of equations representing both the system functions and the system interrelationships. Reduction is found based on an objective function defining the system output given variations in the system inputs and the system operating environment. By minimizing the objective function with respect to these inputs and environments, a reduced system can be found. Thus, a reduction of the system complexity is feasible.

Watson, Michael D.↗

The science of computing - Parallel computation

Although parallel computation architectures have been known for computers since the 1920s, it was only in the 1970s that microelectronic components technologies advanced to the point where it became feasible to incorporate multiple processors in one machine. Concommitantly, the development of algorithms for parallel processing also lagged due to hardware limitations. The speed of computing with solid-state chips is limited by gate switching delays. The physical limit implies that a 1 Gflop operational speed is the maximum for sequential processors. A computer recently introduced features a 'hypercube' architecture with 128 processors connected in networks at 5, 6 or 7 points per grid, depending on the design choice. Its computing speed rivals that of supercomputers, but at a fraction of the cost. The added speed with less hardware is due to parallel processing, which utilizes algorithms representing different parts of an equation that can be broken into simpler statements and processed simultaneously. Present, highly developed computer languages like FORTRAN, PASCAL, COBOL, etc., rely on sequential instructions. Thus, increased emphasis will now be directed at parallel processing algorithms to exploit the new architectures.

Denning, P. J.↗

Economic Metrics for Commercial Reusable Space Transportation Systems

The success of any effort depends upon the effective initial definition of its purpose, in terms of the needs to be satisfied and the goals to be fulfilled. If the desired product is "A System" that is well-characterized, these high-level need and goal statements can be transformed into system requirements by traditional systems engineering techniques. The satisfaction of well-designed requirements can be tracked by fairly straightforward cost, schedule, and technical performance metrics. Unfortunately, some types of efforts, including those that NASA terms "Programs," tend to resist application of traditional systems engineering practices. In the NASA hierarchy of efforts, a "Program" is often an ongoing effort with broad, high-level goals and objectives. A NASA "project" is a finite effort, in terms of budget and schedule, that usually produces or involves one System. Programs usually contain more than one project and thus more than one System. Special care must be taken in the formulation of NASA Programs and their projects, to ensure that lower-level project requirements are traceable to top-level Program goals, feasible with the given cost and schedule constraints, and measurable against top-level goals. NASA Programs and projects are tasked to identify the advancement of technology as an explicit goal, which introduces more complicating factors. The justification for funding of technology development may be based on the technology's applicability to more than one System, Systems outside that Program or even external to NASA. Application of systems engineering to broad-based technology development, leading to effective measurement of the benefits, can be valid, but it requires that potential beneficiary Systems be organized into a hierarchical structure, creating a "system of Systems." In addition, these Systems evolve with the successful application of the technology, which creates the necessity for evolution of the benefit metrics to reflect the changing baseline. Still, economic metrics for technology development in these Programs and projects remain fairly straightforward, being based on reductions in acquisition and operating costs of the Systems. One of the most challenging requirements that NASA levies on its Programs is to plan for the commercialization of the developed technology. Some NASA Programs are created for the express purpose of developing technology for a particular industrial sector, such as aviation or space transportation, in financial partnership with that sector. With industrial investment, another set of goals, constraints and expectations are levied on the technology program. Economic benefit metrics then expand beyond cost and cost savings to include the marketability, profit, and investment return requirements of the private sector. Commercial investment criteria include low risk, potential for high return, and strategic alignment with existing product lines. These corporate criteria derive from top-level strategic plans and investment goals, which rank high among the most proprietary types of information in any business. As a result, top-level economic goals and objectives that industry partners bring to cooperative programs cannot usually be brought into technical processes, such as systems engineering, that are worked collaboratively between Industry and Government. In spite of these handicaps, the top-level economic goals and objectives of a joint technology program can be crafted in such a way that they accurately reflect the fiscal benefits from both Industry and Government perspectives. Valid economic metrics can then be designed that can track progress toward these goals and objectives, while maintaining the confidentiality necessary for the competitive process.

Shaw, Eric J.↗

The NASA Continuous Risk Management Process

As an intern this summer in the GRC Risk Management Office, I have become familiar with the NASA Continuous Risk Management Process. In this process, risk is considered in terms of the probability that an undesired event will occur and the impact of the event, should it occur (ref., NASA-NPG: 7120.5). Risk management belongs in every part of every project and should be ongoing from start to finish. Another key point is that a risk is not a problem until it has happened. With that in mind, there is a six step cycle for continuous risk management that prevents risks from becoming problems. The steps are: identify, analyze, plan, track, control, and communicate & document. Incorporated in the first step are several methods to identify risks such as brainstorming and using lessons learned. Once a risk is identified, a risk statement is made on a risk information sheet consisting of a single condition and one or more consequences. There can also be a context section where the risk is explained in more detail. Additionally there are three main goals of analyzing a risk, which are evaluate, classify, and prioritize. Here is where a value is given to the attributes of a risk &e., probability, impact, and timeframe) based on a multi-level classification system (e.g., low, medium, high). It is important to keep in mind that the definitions of these levels are probably different for each project. Furthermore the risks can be combined into groups. Then, the risks are prioritized to see what risk is necessary to mitigate first. After the risks are analyzed, a plan is made to mitigate as many risks as feasible. Each risk should be assigned to someone in the project with knowledge in the area of the risk. Then the possible approaches to choose from are: research, accept, watch, or mitigate. Next, all risks, mitigated or not, are tracked either individually or in groups. As the plan is executed, risks are re-evaluated, and the attribute values are adjusted as necessary. Metrics are established and monitored as tools for risk tracking. Also a trigger or threshold should be set on the metric data that indicates when an action is needed. Results of this tracking are usually evaluated and reported in a relevant format at weekly or monthly meetings. Choosing controls is the subsequent step, which involves the effects of the tracking. The three basic controls are: close, continue tracking, and re- plan. Finally communicate & document is the last step, but occurs throughout the process. It is vital that main risks, plans, changes, and progress are known by everyone in the project. A good way to keep everyone updated and inform other projects of common issues is by thoroughly documenting project risks. NASA sees value in risk management and believes that projects have greater probability or success by using the NASA Continuous Risk Management Process.

Pokorny, Frank M.↗

Cross-calibration survey (VISNIR)

Included in the summary of the VISNIR survey is (1) a statement of the preferred cross-calibration approach, as endorsed by select members of the VISNIR group, (2) two viewgraphs which summarize the wavelength and fields-of-view of the various instruments, and (3) a listing of these same data, as given by the respective calibration representatives in the survey responses. The Earth Observing System (EOS) Project is fundamentally committed to the acquisition of data which can be reduced to geophysical data products of high and known accuracy. One possible method of insuring the primary data products are of known accuracy is to use the instruments themselves against the same sources to provide an independent check that a common understanding of accuracy exists. The goal then of the radiometric 'Cross-Calibration' at the integrator facility (GE) would be to convincingly establish as late as feasible in the Integration and Test (I&T) cycle that, when stimulated with common sources, the appropriate EOS instrument measurements agree within their previously established accuracy estimates across a useful radiance range, accounting for the additional uncertainty associated with the unique properties of the test set-up itself.

Bruegge, Carol J.↗

Automatic data partitioning on distributed memory multicomputers

Distributed-memory parallel computers are increasingly being used to provide high levels of performance for scientific applications. Unfortunately, such machines are not very easy to program. A number of research efforts seek to alleviate this problem by developing compilers that take over the task of generating communication. The communication overheads and the extent of parallelism exploited in the resulting target program are determined largely by the manner in which data is partitioned across different processors of the machine. Most of the compilers provide no assistance to the programmer in the crucial task of determining a good data partitioning scheme. A novel approach is presented, the constraints-based approach, to the problem of automatic data partitioning for numeric programs. In this approach, the compiler identifies some desirable requirements on the distribution of various arrays being referenced in each statement, based on performance considerations. These desirable requirements are referred to as constraints. For each constraint, the compiler determines a quality measure that captures its importance with respect to the performance of the program. The quality measure is obtained through static performance estimation, without actually generating the target data-parallel program with explicit communication. Each data distribution decision is taken by combining all the relevant constraints. The compiler attempts to resolve any conflicts between constraints such that the overall execution time of the parallel program is minimized. This approach has been implemented as part of a compiler called Paradigm, that accepts Fortran 77 programs, and specifies the partitioning scheme to be used for each array in the program. We have obtained results on some programs taken from the Linpack and Eispack libraries, and the Perfect Benchmarks. These results are quite promising, and demonstrate the feasibility of automatic data partitioning for a significant class of scientific application programs with regular computations.

Gupta, Manish↗

Modification of Altitude Wind Tunnel for Icing and Propulsion Research Study, Part B

This report describes the results of an engineering study conducted for NASA-Lewis Research Center on Modifications to the Altitude Wind Tunnel (AWT) for Icing and Propulsion Research by DSW Engineering Corporation, Orlando, Florida and DSMA International Inc., Toronto, Canada. The engineering study referred to as study 'Part B' has been carried out under authorization of NASA Contract NAS 3-22933 (Ref. 1). The scope of work defined in the Statement of Work 3-169855 (Ref. 2) Revised 2/20/81 was discussed in detail with NASA on October 2, 1981 and covers the following areas: - Fan and Fan Housing. This includes assessment of circuit loss analyses, fan aerodynamics and mechanical conceptual design of variable and fixed pitch fans considering fixed and variable inlet guide vanes. - Fan Drive Systems - considering fixed and variable speed drives with continuous rating of 30,000 HP with overload capability of 45,000. The drive shaft between the motor and fan is to be considered and also the existing foundations for the main drive motor. - 20 ft.Test Section Arrangement - having slotted wall configurations suitable for testing at transonic velocities, with various model support systems required for the anticipated models and tests. A model handling concept aimed for high productivity testing and means for quick access to the model in the test section between test runs. - 45 ft. Test Section - feasible and practical approach for model installation and removal.

Leonard, H. Wayne↗

Final Environmental Impact Statement for the Ulysses Mission (Tier 2)

This Final (Tier 2) Environmental Impact Statement (FEIS) addresses the environmental impacts which may be caused by implementation of the Ulysses mission, a space flight mission to observe the polar regions of the Sun. The proposed action is completion of preparation and operation of the Ulysses spacecraft, including its planned launch at the earliest available launch opportunity on the Space Transportation System (STS) Shuttle in October 1990 or in the backup opportunity in November 1991. The alternative is canceling further work on the mission. The Tier 1 EIS included a delay alternative which considered the Titan 4 launch vehicle as an alternative booster stage for launch in 1991 or later. This alternative was further evaluated and eliminated from consideration when, in November 1988, the U.S. Air Force, which procures the Titan 4, notified that it could not provide a Titan 4 vehicle for the 1991 launch opportunity because of high priority Department of Defense requirements. The Titan 4 launch vehicle is no longer a feasible alternative to the STS/Inertial Upper Stage (IUS)/Payload Assist Module-Special (PAM-S) for the November 1991 launch opportunity. The only expected environment effects of the proposed action are associated with normal launch vehicle operation and are treated elsewhere. The environmental impacts of normal Shuttle launches were addressed in existing NEPA documentation and are briefly summarized. These impacts are limited largely to the near-field at the launch pad, except for temporary stratospheric ozone effects during launch and occasional sonic boom effects near the landing site. These effects were judged insufficient to preclude Shuttle launches. There could also be environmental impacts associated with the accidental release of radiological material during launch, deployment, or interplanetary trajectory injection of the Ulysses spacecraft. Intensive analysis indicates that the probability of release is small. There are no environmental impacts in the no-action alternative; however, the U.S. Government and the European Space Agency would suffer adverse fiscal and programmatic impacts if this alternative were adopted. The scientific benefits of the mission would be delayed and possibly lost. There could be significant impacts on the ability of the U.S. to negotiate international agreements for cooperative space activities.

Source record↗

Integrating Design and Manufacturing for a High Speed Civil Transport Wing

The aerospace industry is currently addressing the problem of integrating design and manufacturing. Because of the difficulties associated with using conventional, procedural techniques and algorithms, it is the authors' belief that the only feasible way to integrate the two concepts is with the development of an appropriate Knowledge-Based System (KBS). The authors propose a methodology for an aircraft producibility assessment, including a KBS, that addresses both procedural and heuristic aspects of integrating design and manufacturing of a High Speed Civil Transport (HSCT) wing. The HSCT was chosen as the focus of this investigation since it is a current NASA/aerospace industry initiative full of technological challenges involving many disciplines. The paper gives a brief background of selected previous supersonic transport studies followed by descriptions of key relevant design and manufacturing methodologies. Georgia Tech's Concurrent Engineering/Integrated Product and Process Development methodology is discussed with reference to this proposed conceptual producibility assessment. Evaluation criteria are presented that relate pertinent product and process parameters to overall product producibility. In addition, the authors' integration methodology and reasons for selecting a KBS to integrate design and manufacturing are presented in this paper. Finally, a proposed KBS is given, as well as statements of future work and overall investigation objectives.

Marx, William J.↗

Final Environmental Impact Statement for the Galileo Mission (Tier 2)

This Final Environmental Impact Statement (FEIS) addresses the proposed action of completing the preparation and operation of the Galileo spacecraft, including its planned launch on the Space Transportation System (STS) Shuttle in October 1989, and the alternative of canceling further work on the mission. The Tier 1 (program level) EIS (NASA 1988a) considered the Titan IV launch vehicle as an alternative booster stage for launch in May 1991 or later. The May 1991 Venus launch opportunity is considered a planetary back-up for the Magellan (Venus Radar Mapper) mission, the Galileo mission, and the Ulysses mission. Plans were underway to enable the use of a Titan IV launch vehicle for the planetary back-up. However, in November 1988, the U.S. Air Force, which procures the Titan IV for NASA, notified NASA that it could not provide a Titan IV vehicle for the May 1991 launch opportunity due to high priority Department of Defense requirements. Consequently, NASA terminated all mission planning for the Titan IV planetary back-up. A minimum of 3 years is required to implement mission-specific modifications to the basic Titan IV launch configuration; therefore, insufficient time is available to use a Titan IV vehicle in May 1991. Thus, the Titan IV launch vehicle is no longer a feasible alternative to the STS/Inertial Upper Stage (IUS) for the May 1991 launch opportunity.

Source record↗