Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “custom”

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

The Applied Meteorology Unit: Nineteen Years Successfully Transitioning Research into Operations for America's Space Program

The Applied Meteorology Unit (AMU) provides technology transition and technique development to improve operational weather support to the Space Shuttle and the entire American space program. The AMU is funded and managed by NASA and operated by a contractor that provides five meteorologists with a diverse mix of advanced degrees, operational experience, and associated skills including data processing, statistics, and the development of graphical user interfaces. The AMU's primary customers are the U.S. Air Force 45th Weather Squadron at Patrick Air Force Base, the National Weather Service Spaceflight Meteorology Group at NASA Johnson Space Center, and the National Weather Service Melbourne FL Forecast Office. The AMU has transitioned research into operations for nineteen years and worked on a wide range of topics, including new forecasting techniques for lightning probability, synoptic peak winds,.convective winds, and summer severe weather; satellite tools to predict anvil cloud trajectories and evaluate camera line of sight for Space Shuttle launch; optimized radar scan strategies; evaluated and implemented local numerical models; evaluated weather sensors; and many more. The AMU has completed 113 projects with 5 more scheduled to be completed by the end of 2010. During this rich history, the AMU and its customers have learned many lessons on how to effectively transition research into operations. Some of these lessons learned include collocating with the operational customer and periodically visiting geographically separated customers, operator submitted projects, consensus tasking process, use of operator primary advocates for each project, customer AMU liaisons with experience in both operations and research, flexibility in adapting the project plan based on lessons learned during the project, and incorporating training and other transition assistance into the project plans. Operator involvement has been critical to the AMU's remarkable success and many awards from NASA, the National Weather Association, and two citations from the Navy's Center of Excellence for Best Manufacturing Practices. This paper will present the AMU's proven methods and explain how they may be applied by other organizations to effectively transition research into operations.

Madura, John T.↗
NASA NTRS2001

Challenges and Lessons Learned in the Application of Autonomy to Space Operations

NASA's Space Operations Management Office (SOMO) is working toward a goal of providing an integrated infrastructure of mission and data services for space missions undertaken by NASA enterprises. A significant portion of this effort is focused on reducing the cost of these services. We are interested in the potential of autonomy to reduce operations costs. SOMO services support space missions, but are not part of the mission objectives; therefore the level of acceptable risk is very low. In fact, SOMO could be effective ly prevented from applying autonomy if customers merely perceive it as adding risk to their mission(s). We are interested in this workshop from the standpoint of understanding what can be done to realize the potential cost savings due to autonomy while maintaining acceptable risk and serving the needs of our customers. We would like to present our lessons learned so far in adopting autonomy and automation, which we think will contribute to clarifying the challenges facing the use of such technology. SOMO provides services to a diverse and ambitious set of mission customers. Many of these missions are groundbreaking missions for which communications, data, and other operations requirements sometimes cannot be clearly articulated early in the program. This motivates a need for systems that are robust in the face of unanticipated situations so that customer missions are not unreasonably constrained or impacted by "shortcomings" in SOMO services. One of SOMO's primary goals is to realize a paradigm in which SOMO acts as a service provider to organizations that fly space missions for NASA, other government agencies, and even the commercial sector. These organizations purchase SOMO services "by the pound" as customers. We have to provide systems that are not experiments themselves, but rather stable bases from which to do bold experiments. To this end, SOMO also seeks to work closely with industry to see that robust autonomy technology gets infused into products and services for the space industry and beyond. The potential for application of these technologies spans space-based communications networks (e.g. TDRSS) and ground-based assets including communication and tracking antenna systems, data networks, and control centers. There are several problems that are candidates for the application of autonomy, if it can be made reliable enough, including: antenna control, antenna scheduling, communication link scheduling and operation, navigation, attitude determination, fault detection, isolation, and reconfiguration (for spacecraft or ground assets), and mission-level planning and scheduling. Some attempts have been made to apply autonomy and automation in these areas in the past with varying degrees of success. We will present relevant case histories and the lessons inferred from them. Combining this past experience with anticipated future needs, we can clarify the challenges that must be met in order to realize the benefits of autonomy.

Forrest, David J.↗
NASA NTRS2011

Reinventing the International Space Station Payload Integration Processes and Capabilities

The fundamental ISS payload integration philosophy, processes and capabilities were established in the context of how NASA science programs were conducted and executed in the early 1990 s. Today, with the designation of the United States (US) portion of ISS as a National Lab, the ISS payload customer base is growing to include other government agencies, private and commercial research. The fields of research are becoming more diverse expanding from the NASA centric physical, materials and human research sciences to test beds for exploration and technology demonstration, biology and biotechnology, and as an Earth and Space science platform. This new customer base has a broader more diverse set of expectations and requirements for payload design, verification, integration, test, training, and operations. One size fits all processes are not responsive to this broader customer base. To maintain an organization s effectiveness it must listen to its customers, understand their needs, learn from its mistakes, and foster an environment of continual process improvement. The ISS Payloads office is evolving to meet these new customer expectations.

Jones, Rod↗
NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗
NASA NTRS2008

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

It is essential that management and engineering understand the need for an availability requirement for the customer's space transportation system as it enables the meeting of his needs, goal, and objectives. There are three types of availability, e.g., operational availability, achieved availability, or inherent availability. The basic definition of availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. The major difference is the inclusiveness of the functions within the mean downtime and the mean uptime. This paper will address tIe inherent availability which only addresses the mean downtime as that mean time to repair or the time to determine the failed article, remove it, install a replacement article and verify the functionality of the repaired system. The definitions of operational availability include the replacement hardware supply or maintenance delays and other non-design factors in the mean downtime. Also with inherent availability the mean uptime will only consider the mean time between failures (other availability definitions consider this as mean time between maintenance - preventive and corrective maintenance) that requires the repair of the system to be functional. It is also essential that management and engineering understand all influencing attributes relationships to each other and to the resultant inherent availability requirement. This visibility will provide the decision makers with the understanding necessary to place constraints on the design definition for the major drivers that will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system provided the customer. This inherent availability requirement may be driven by the need to use a multiple launch approach to placing humans on the moon or the desire to control the number of spare parts required to support long stays in either orbit or on the surface of the moon or mars. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability, but also provide the capability to bound the variables providing engineering the insight required to control the system's engineering solution. An example of this visibility will be the need to provide integration of similar discipline functions to allow control of the total parts count of the space transportation system. Also the relationship visibility of selecting a reliability requirement will place a constraint on parts count to achieve a given inherent availability requirement or accepting a larger parts count with the resulting higher reliability requirement. This paper will provide an understanding for the relationship of mean repair time (mean downtime) to maintainability, e.g., accessibility for repair, and both mean time between failure, e.g., reliability of hardware and the system inherent availability. Having an understanding of these relationships and resulting requirements before starting the architectural design concept definition will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russel E.↗
NASA NTRS2009

Recent Weather Technologies Delivered to America's Space Program by the Applied Meteorology Unit

The Applied Meteorology Unit (AMU) is a unique joint venture of NASA, the Air Force and the National Weather Service (NWS) and has been supporting the Space Program for nearly two decades. The AMU acts as a bridge between the meteorological research community and operational forecasters by developing, evaluating and transitioning new technology and techniques to improve weather support to spaceport operations at the Eastern Range (ER) and Kennedy Space Center. Its primary customers are the 45th Weather Squadron at Cape Canaveral Air Force Station (CCAFS), the Spaceflight Meteorology Group at Johnson Space Center and the National Weather Service Office in Melbourne, FL. Its products are used to support NASA's Shuttle and ELV programs as well as Department of Defense and commercial launches from the ER. Shuttle support includes landing sites beyond the ER. The AMU is co-located with the Air Force operational forecasters at CCAFS to facilitate continuous two-way interaction between the AMU and its operational customers. It is operated under a NASA, Air Force, and NWS Memorandum of Understanding (MOU) by a competitively-selected contractor. The contract, which is funded and managed by NASA, provides five full time professionals with degrees in meteorology or related fields, some of whom also have operational experience. NASA provides a Ph.D.- level NASA civil service scientist as Chief of the AMU. The AMU is tasked by its customers through a unique, nationally recognized process. The tasks are limited to development, evaluation and operational transition of technology to improve weather support to spaceport operations and providing expert advice to the customers. The MOU expressly forbids using the AMU resources to conduct operations or do basic research. The presentation will provide a brief overview of the AMU and how it is tasked by its customers to provide high priority products and services. The balance of the presentation will cover a sampling of products delivered over the last 18 years that are currently in operational use. Each example will describe the problem to be solved, the solution provided, and the operational benefits of implementing that solution.

Bauman, WIlliam, H., III↗
NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗
NASA NTRS1983

Design of a high-speed digital processing element for parallel simulation

A prototype of a custom designed computer to be used as a processing element in a multiprocessor based jet engine simulator is described. The purpose of the custom design was to give the computer the speed and versatility required to simulate a jet engine in real time. Real time simulations are needed for closed loop testing of digital electronic engine controls. The prototype computer has a microcycle time of 133 nanoseconds. This speed was achieved by: prefetching the next instruction while the current one is executing, transporting data using high speed data busses, and using state of the art components such as a very large scale integration (VLSI) multiplier. Included are discussions of processing element requirements, design philosophy, the architecture of the custom designed processing element, the comprehensive instruction set, the diagnostic support software, and the development status of the custom design.

Milner, E. J.↗
NASA NTRS1983

Control of a heterogeneous two-server exponential queueing system

A dynamic control policy known as 'threshold queueing' is defined for scheduling customers from a Poisson source on a set of two exponential servers with dissimilar service rates. The slower server is invoked in response to instantaneous system loading as measured by the length of the queue of waiting customers. In a threshold queueing policy, a specific queue length is identified as a 'threshold,' beyond which the slower server is invoked. The slower server remains busy until it completes service on a customer and the queue length is less than its invocation threshold. Markov chain analysis is employed to analyze the performance of the threshold queueing policy and to develop optimality criteria. It is shown that probabilistic control is suboptimal to minimize the mean number of customers in the system. An approximation to the optimum policy is analyzed which is computationally simple and suffices for most operational applications.

Larsen, R. L.↗
NASA NTRS1991

Information logistics: A production-line approach to information services

Logistics can be defined as the process of strategically managing the acquisition, movement, and storage of materials, parts, and finished inventory (and the related information flow) through the organization and its marketing channels in a cost effective manner. It is concerned with delivering the right product to the right customer in the right place at the right time. The logistics function is composed of inventory management, facilities management, communications unitization, transportation, materials management, and production scheduling. The relationship between logistics and information systems is clear. Systems such as Electronic Data Interchange (EDI), Point of Sale (POS) systems, and Just in Time (JIT) inventory management systems are important elements in the management of product development and delivery. With improved access to market demand figures, logisticians can decrease inventory sizes and better service customer demand. However, without accurate, timely information, little, if any, of this would be feasible in today's global markets. Information systems specialists can learn from logisticians. In a manner similar to logistics management, information logistics is concerned with the delivery of the right data, to the ring customer, at the right time. As such, information systems are integral components of the information logistics system charged with providing customers with accurate, timely, cost-effective, and useful information. Information logistics is a management style and is composed of elements similar to those associated with the traditional logistics activity: inventory management (data resource management), facilities management (distributed, centralized and decentralized information systems), communications (participative design and joint application development methodologies), unitization (input/output system design, i.e., packaging or formatting of the information), transportations (voice, data, image, and video communication systems), materials management (data acquisition, e.g., EDI, POS, external data bases, data entry) and production scheduling (job, staff, and project scheduling).

Adams, Dennis↗
NASA NTRS1992

Optimal routing and buffer allocation for a class of finite capacity queueing systems

The problem of routing jobs to K parallel queues with identical exponential servers and unequal finite buffer capacities is considered. Routing decisions are taken by a controller which has buffering space available to it and may delay routing of a customer to a queue. Using ideas from weak majorization, it is shown that the shorter nonfull queue delayed (SNQD) policy minimizes both the total number of customers in the system at any time and the number of customers that are rejected by that time. The SNQD policy always delays routing decisions as long as all servers are busy. Only when all the buffers at the controller are occupied is a customer routed to the queue with the shortest queue length that is not at capacity. Moreover, it is shown that, if a fixed number of buffers is to be distributed among the K queues, then the optimal allocation scheme is the one in which the difference between the maximum and minimum queue capacities is minimized, i.e., becomes either 0 or 1.

Towsley, Don↗
NASA NTRS1993

Software synthesis using generic architectures

A framework for synthesizing software systems based on abstracting software system designs and the design process is described. The result of such an abstraction process is a generic architecture and the process knowledge for customizing the architecture. The customization process knowledge is used to assist a designer in customizing the architecture as opposed to completely automating the design of systems. Our approach using an implemented example of a generic tracking architecture which was customized in two different domains is illustrated. How the designs produced using KASE compare to the original designs of the two systems, and current work and plans for extending KASE to other application areas are described.

Bhansali, Sanjay↗
NASA NTRS1994

Scientific and technical photography at NASA Langley Research Center

As part of my assignment connected with the Scientific and Technical Photography & Lab (STPL) at the NASA Langley Research Center I conducted a series of interviews and observed the day to day operations of the STPL with the ultimate objective of becoming exposed first hand to a scientific and technical photo/imaging department for which my school prepares its graduates. I was also asked to share my observations with the staff in order that these comments and observations might assist the STPL to better serve its customers. Meetings with several individuals responsible for various wind tunnels and with a group that provides photo-optical instrumentation services at the Center gave me an overview of the services provided by the Lab and possible areas for development. In summary form these are some of the observations that resulted from the interviews and daily contact with the STPL facility. (1) The STPL is perceived as a valuable and almost indispensable service group within the organization. This comment was invariably made by everyone. Everyone also seemed to support the idea that the STPL continue to provide its current level of service and quality. (2) The STPL generally is not perceived to be a highly technically oriented group but rather as a provider of high quality photographic illustration and documentation services. In spite of the importance and high marks assigned to the STPL there are several observations that merit consideration and evaluation for possible inclusion into the STPL's scope of expertise and future operating practices. (1) While the care and concern for artistic rendition of subjects is seen as laudable and sometimes valuable, the time that this often requires is seen as interfering with keeping the tunnels operating at maximum productivity. Tunnel managers would like to shorten down-time due to photography, have services available during evening hours and on short notice. It may be of interest to the STPL that tunnel managers are incorporating ever greater imaging capabilities in their facilities. To some extent this could mean a reduced demand for traditional photographic services. (2) The photographic archive is seen as a Center resource. Archiving of images, as well as data, is a matter of concern to the investigators. The early holdings of the Photographic Archives are quickly deteriorating. The relative inaccessibility of the material held in the archives is problematic. (3) In certain cases delivery or preparation of digital image files instead of, or along with, hardcopy is already being perceived by the STPL's customers as desirable. The STPL should make this option available, and the fact that it has, or will have this capability widely known. (4) The STPL needs to continue to provide expert advice and technical imaging support in terms of application information to users of traditional photographic and new electronic imaging systems. Cooperative demo projects might be undertaken to maintain or improve the capabilities of the Lab. (5) STPL personnel do not yet have significant electronic imaging or electronic communication skills and improvements in this is an area could potentially have a positive impact on the Center. (6) High speed photographic or imaging services are often mentioned by the STPL as being of primary importance to their mission but the lab supports very few projects calling for high speed imaging services. Much high speed equipment is in poor state of repair. It is interesting to note that when the operation of lasers, digital imaging or quantitative techniques are requested these are directed to another NASA department. Could joint activities be initiated to solve problems? (7). The STPL could acquire more technical assignments if examples of the areas where they posses expertise would be circulated around the center. The fact that the STPL owns high speed video capability could be 'advertised' among its customer base if there truly was an interest in building up a customer base in this area. The STPL could participate in events like TOPS as an exhibitor, as well as a documenter, of the event.

Davidhazy, Andrew↗
NASA NTRS1994

Software agents for the dissemination of remote terrestrial sensing data

Remote terrestrial sensing (RTS) data is constantly being collected from a variety of space-based and earth-based sensors. The collected data, and especially 'value-added' analyses of the data, are finding growing application for commercial, government, and scientific purposes. The scale of this data collection and analysis is truly enormous; e.g., by 1995, the amount of data available in just one sector, NASA space science, will reach 5 petabytes. Moreover, the amount of data, and the value of analyzing the data, are expected to increase dramatically as new satellites and sensors become available (e.g., NASA's Earth Observing System satellites). Lockheed and other companies are beginning to provide data and analysis commercially. A critical issue for the exploitation of collected data is the dissemination of data and value-added analyses to a diverse and widely distributed customer base. Customers must be able to use their computational environment (eventually the National Information Infrastructure) to obtain timely and complete information, without having to know the details of where the relevant data resides and how it is accessed. Customers must be able to routinely use standard, widely available (and, therefore, low cost) analyses, while also being able to readily create on demand highly customized analyses to make crucial decisions. The diversity of user needs creates a difficult software problem: how can users easily state their needs, while the computational environment assumes the responsibility of finding (or creating) relevant information, and then delivering the results in a form that users understand? A software agent is a self-contained, active software module that contains an explicit representation of its operational knowledge. This explicit representation allows agents to examine their own capabilities in order to modify their goals to meet changing needs and to take advantage of dynamic opportunities. In addition, the explicit representation allows agents to advertize their capabilities and results to other agents, thereby allowing the collection of agents to reuse each others work.

Toomey, Christopher N.↗
NASA NTRS1996

Experiences in Interagency and International Interfaces for Mission Support

The Flight Dynamics Division (FDD) of the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GFSC) provides extensive support and products for Space Shuttle missions, expendable launch vehicle launches, and routine on-orbit operations for a variety of spacecraft. A major challenge in providing support for these missions is defining and generating the products required for mission support and developing the method by which these products are exchanged between supporting agencies. As interagency and international cooperation has increased in the space community, the FDD customer base has grown and with it the number and variety of external interfaces and product definitions. Currently, the FDD has working interfaces with the NASA Space and Ground Networks, the Johnson Space Center, the White Sands Complex, the Jet propulsion Laboratory (including the Deep Space Network), the United States Air Force, the Centre National d'Etudes Spatiales, the German Spaceflight Operations Center, the European Space Agency, and the National Space Development Agency of Japan. With the increasing spectrum of possible data product definitions and delivery methods, the FDD is using its extensive interagency experience to improve its support of established customers and to provide leadership in adapting/developing new interfaces. This paper describes the evolution of the interfaces between the FDD and its customers, discusses many of the joint activities ith these customers, and summarizes key lessons learned that can be applied to current and future support.

Dell, G. T.↗
NASA NTRS1997

Developing Tools and Techniques to Increase Communication Effectiveness

The Public Affairs Office (PAO) of the Johnson Space Center (JSC) is responsible for communicating current JSC Space Program activities as well as goals and objectives to the American Public. As part of the 1996 Strategic Communications Plan, a review of PAO' s current communication procedures was conducted. The 1996 Summer Faculty Fellow performed research activities to support this effort by reviewing current research concerning NASA/JSC's customers' perceptions and interests, developing communications tools which enable PAO to more effectively inform JSC customers about the Space Program, and proposing a process for developing and using consistent messages throughout PAO. Note that this research does not attempt to change or influence customer perceptions or interests but, instead, incorporates current customer interests into PAO's communication process.

Hayes, Linda A.↗
NASA NTRS1998

Sensor/Actuator Selection for Gust and Turbulence Control

From aircraft fuselages and space stations to vacuum cleaners and automobiles, active control of noise and/or vibration has come of age. Determining the number of active control devices (e.g. actuators) to be placed and where they are to be placed is the prototypical location problem. However, unlike typical location problems, where the customer is readily identified and is actively engaged in the assessment of the performance of the chosen locations, the customers that active control devices serve are not so easily identified and their impact on system performance issues may be unclear. For example, consider the problem of where to locate actuators to attenuate cabin noise in a propeller driven aircraft. Clearly, the ultimate customers are the passengers who will travel in these aircraft. But to decide whether one set of actuator locations is better than another it is unlikely we will ask passengers to fly in the aircraft and fill out a questionnaire about noise levels. Instead a set of sensors (pseudo-customers) are placed and the system performance of the actuators, as measured by these sensors, is recorded. Hence, we have yet another location problem. How many sensors should there be and where should they be located? In many instances collocation of sensors and actuators is the answer but in other instances it is not. A variety of approaches have been taken to address these sensor/actuator location problems. With regard to damping vibrations in truss structures (space station prototypes) it was formulated a new noxious location problem and generated high-quality solutions with a combination of LP-relaxations and heuristic search procedures. Other related efforts are summarized the actuator location problem for a single frequency interior noise control problem was examined for an idealized aircraft cabin. A tabu search procedure was shown to generate better locations for the actuators than a modal decomposition approach. The model was extended to include multi-frequency information. The sensor location problem is addressed. In the latter article a reactive tabu search scheme was shown to dominate a static tabu search approach. Our focus here is to determine locations to control and/or sense vibrations on a truss structure. However, instead of using one of the earlier optimization models referenced in the above paragraph we adopt an experimental design approach.

Kincaid, Rex K.↗
NASA NTRS1999

The Hitchhiker's Guide to I&T

With over two dozen missions since the first in 1986, the Hitchhiker project has a reputation for providing quick-reaction, low-cost flight services for Shuttle Small Payloads Project (SSPP) customers. Despite the successes, several potential improvements in customer payload integration and test (I&T) deserve consideration. This paper presents suggestions to Hitchhiker customers on how to help make the I&T process run smoother. Included are: customer requirements and interface definition, pre-integration test and evaluation, configuration management, I&T overview and planning, problem mitigation, and organizational communication. In this era of limited flight opportunities and new ISO-based requirements, issues such as these have become more important than ever.

Wright, Michael R.↗