Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle”

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 649 records · Page 36
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

The Integration of COTS/GOTS within NASA's HST Command and Control System

NASA's mission critical Hubble Space Telescope (HST) command and control system has been re-engineered with COTS/GOTS and minimal custom code. This paper focuses on the design of this new HST Control Center System (CCS) and the lessons learned throughout its development. CCS currently utilizes 31 COTS/GOTS products with an additional 12 million lines of custom glueware code; the new CCS exceeds the capabilities of the original system while significantly reducing the lines of custom code by more than 50%. The lifecycle of COTS/GOTS products will be examined including the pack-age selection process, evaluation process, and integration process. The advantages, disadvantages, issues, concerns, and lessons teamed for integrating COTS/GOTS into the NASA's mission critical HST CCS will be examined in detail. Command and control systems designed with traditional custom code development efforts will be compared with command and control systems designed with new development techniques relying heavily on COTS/COTS integration. This paper will reveal the many hidden costs of COTS/GOTS solutions when compared to traditional custom code development efforts; this paper will show the high cost of COTS/GOTS solutions including training expenses, consulting fees, and long-term maintenance expenses.

Pfarr, Thomas↗
NASA NTRS2001

Novel Cryogenic Insulation Materials: Aerogel Composites

New insulation materials are being developed to economically and reliably insulate future reusable spacecraft cryogenic tanks over a planned lifecycle of extreme thermal challenges. These insulation materials must prevent heat loss as well as moisture and oxygen condensation on the cryogenic tanks during extended groundhold, must withstand spacecraft launch conditions, and must protect a partly full or empty reusable cryogenic tank from significant reentry heating. To perform over such an extreme temperature range, novel composites were developed from aerogels and high-temperature matrix material such as Space Shuttle tile. These materials were fabricated and tested for use both as cryogenic insulation and as high-temperature insulation. The test results given in this paper were generated during spacecraft re-entry heating simulation tests using cryogenic cooling.

White, Susan↗
NASA NTRS2001

ASK Magazine

Not everyone looks forward to reviews. Dog and pony shows I've heard them called. Exercises in putting together Power Point charts. Other less tasteful descriptions abound, but I won't bother to summarize these. This is a tasteful magazine after all. In this issue, we've assembled a number of articles on the subject of reviews, particularly as they occur in the NASA project world (although we cover the subject from other perspectives too). Veteran NASA Project Manager Marty Davis, in his article Tangled Up in Reviews, writes, "Many people regard reviews as something onerous, but if we can tailor them so that they're not as bad as they have to be, it can be a great benefit to a project manager." Great benefits to the project manager is what you'll find in Marty's story as he describes not only tailoring a single review but the entire lifecycle of reviews in his project. In Jo Gunderson's story, Calling Down the Fire on Yourself, she describes a young NASA Project Manager who does just that because, as he tells her, I needed to know if there was anything that I had overlooked." How he brings fire down on himself at his project review will inspire other young Project Managers, seasoned managers, and anyone else who reads this powerful story. Leave Your Ego at the Door, by Jenny Baer-Reidhart and Ray Morgan, uses reviews to highlight the creative collaboration that existed between NASA and one of its industry partners. The protagonist of this story is a company who took advantage of NASAs expert advice during reviews and accomplished amazing feats as a result. The story also examines how disasters might well have been avoided by two other NASA partners had they been as open-minded as the first company during their reviews. In Roy Malone's story, Standing Offer, a NASA Project Manager describes how he used a crack review team to help him pass a critical certification inspection while he was a Combat Systems Officer in the Navy. Malone invited the reviewers to come back several times so that they would be able to focus in detail on the many areas of the program that would be scrutinized during the certification inspection. These are just a sampling of some of the articles you'll find in this issue of ASK. We believe this issue offers ample evidence that talented Project Managers know how to use reviews to the great benefit of their projects. A talented Project Manager will typically figure out a way to turn any onerous task into a useful learning exercise. These Project Managers demonstrate that the real value of reviews is that they provide a chance to learn something. No dog and pony shows here.

Laufer, Alexander↗
NASA NTRS2001

The Integration of COTS/GOTS within NASA's HST Command and Control System

NASA's mission critical Hubble Space Telescope (HST) command and control system has been re-engineered with commercial-off-the-shelf (COTS/GOTS) and minimal custom code. This paper focuses on the design of this new HST Control Center System (CCS) and the lessons learned throughout its development. CCS currently utilizes more than 30 COTS/GOTS products with an additional 1/2 million lines of custom glueware code; the new CCS exceeds the capabilities of the original system while significantly reducing the lines of custom code by more than 50%. The lifecycle of COTS/GOTS products will be examined including the package selection process, evaluation process, and integration process. The advantages, disadvantages, issues, concerns, and lessons learned for integrating COTS/GOTS into the NASA's mission critical HST CCS will be examined in detail. This paper will reveal the many hidden costs of COTS/GOTS solutions when compared to traditional custom code development efforts; this paper will show the high cost of COTS/GOTS solutions including training expenses, consulting fees, and long-term maintenance expenses.

Pfarr, Thomas↗
NASA NTRS2001

Managing Programmatic Risk for Complex Space System Developments

Risk management strategies have become a recent important research topic to many aerospace organizations as they prepare to develop the revolutionary complex space systems of the future. Future multi-disciplinary complex space systems will make it absolutely essential for organizations to practice a rigorous, comprehensive risk management process, emphasizing thorough systems engineering principles to succeed. Project managers must possess strong leadership skills to direct high quality, cross-disciplinary teams for successfully developing revolutionary space systems that are ever increasing in complexity. Proactive efforts to reduce or eliminate risk throughout a project's lifecycle ideally must be practiced by all technical members in the organization. This paper discusses some of the risk management perspectives that were collected from senior managers and project managers of aerospace and aeronautical organizations by the use of interviews and surveys. Some of the programmatic risks which drive the success or failure of projects are revealed. Key findings lead to a number of insights for organizations to consider for proactively approaching the risks which face current and future complex space systems projects.

Panetta, Peter V.↗
NASA NTRS2001

Automatic Overset Grid Generation with Heuristic Feedback Control

An advancing front grid generation system for structured Overset grids is presented which automatically modifies Overset structured surface grids and control lines until user-specified grid qualities are achieved. The system is demonstrated on two examples: the first refines a space shuttle fuselage control line until global truncation error is achieved; the second advances, from control lines, the space shuttle orbiter fuselage top and fuselage side surface grids until proper overlap is achieved. Surface grids are generated in minutes for complex geometries. The system is implemented as a heuristic feedback control (HFC) expert system which iteratively modifies the input specifications for Overset control line and surface grids. It is developed as an extension of modern control theory, production rules systems and subsumption architectures. The methodology provides benefits over the full knowledge lifecycle of an expert system for knowledge acquisition, knowledge representation, and knowledge execution. The vector/matrix framework of modern control theory systematically acquires and represents expert system knowledge. Missing matrix elements imply missing expert knowledge. The execution of the expert system knowledge is performed through symbolic execution of the matrix algebra equations of modern control theory. The dot product operation of matrix algebra is generalized for heuristic symbolic terms. Constant time execution is guaranteed.

Robinson, Peter I.↗
NASA NTRS1996

Thermal Protection Technology for Access to Space Vehicles

In the next century a new generation of space launch vehicles will be required to replace the Space Shuttle and the current expendable launch vehicle fleet. These new transportation systems must provide much lower lifecycle cost and mission versatility. In order to provide these attributes the vehicles must be designed with large operational margins of safety and weights comparable or lower than current systems. Advancements in Thermal Protection Systems (TPS) will be necessary to obtain these goals. This presentation will describe the thermal protection technology now under development by NASA that will be available for future Access to Space vehicles.

Goldstein, Howard E.↗
NASA NTRS2001

Methodology Development for Assessment of Spaceport Technology Returns and Risks

As part of Kennedy Space Center's (KSC's) challenge to open the space frontier, new spaceport technologies must be developed, matured and successfully transitioned to operational systems. R&D investment decisions can be considered from multiple perspectives. Near mid and far term technology horizons must be understood. Because a multitude of technology investment opportunities are available, we must identify choices that promise the greatest likelihood of significant lifecycle At the same time, the costs and risks of any choice must be well understood and balanced against its potential returns The problem is not one of simply rank- ordering projects in terms of their desirability. KSC wants to determine a portfolio of projects that simultaneously satisfies multiple goals, such as getting the biggest bang for the buck, supporting projects that may be too risky for private funding, staying within annual budget cycles without foregoing the requirements of a long term technology vision, and ensuring the development of a diversity of technologies that, support the variety of operational functions involved in space transportation. This work aims to assist in the development of in methods and techniques that support strategic technology investment decisions and ease the process of determining an optimal portfolio of spaceport R&D investments. Available literature on risks and returns to R&D is reviewed and most useful pieces are brought to the attention of the Spaceport Technology Development Office (STDO). KSC's current project management procedures are reviewed. It is found that the "one size fits all" nature of KSC's existing procedures and project selection criteria is not conducive to prudent decision-making. Directions for improving KSC's - procedures and criteria are outlined. With help of a contractor, STDO is currently developing a tool, named Change Management Analysis Tool (CMAT)/ Portfolio Analysis Tool (PAT), to assist KSC's R&D portfolio determination. A critical review of CMAT/PAT is undertaken. Directions for the improvement of this tool are provided. STDO and KSC intend to follow up on many, if not all, of the recommendations provided.

Joglekar, Prafulla↗
NASA NTRS2002

Pressure Transducer Remote Calibration/Health Check

This presentation reports on efforts to develop an in-situ pressure transducer calibration system for extension of calibration lifecycle and transducer health determination. This system aims to: (1) provide a long term solution to determining the calibration of pressure transducers for gas applications, (2) provide a method of isolating problems in remote measurements, and (3) reduce costs and resources by extending the length of time a transducer may be left in a system without a repeat laboratory calibration. Topic covers include: design requirements, design assumptions and design approach.

Deyoe, Richard↗
NASA NTRS2002

Evaluation of Cirrus Cloud Simulations using ARM Data-Development of Case Study Data Set

Cloud-resolving models (CRMs) are being increasingly used to develop parametric treatments of clouds and related processes for use in global climate models (GCMs). CRMs represent the integrated knowledge of the physical processes acting to determine cloud system lifecycle and are well matched to typical observational data in terms of physical parameters/measurables and scale-resolved physical processes. Thus, they are suitable for direct comparison to field observations for model validation and improvement. The goal of this project is to improve state-of-the-art CRMs used for studies of cirrus clouds and to establish a relative calibration with GCMs through comparisons among CRMs, single column model (SCM) versions of the GCMs, and observations. The objective is to compare and evaluate a variety of CRMs and SCMs, under the auspices of the GEWEX Cloud Systems Study (GCSS) Working Group on Cirrus Cloud Systems (WG2), using ARM data acquired at the Southern Great Plains (SGP) site. This poster will report on progress in developing a suitable WG2 case study data set based on the September 26, 1996 ARM IOP case - the Hurricane Nora outflow case. Progress is assessing cloud and other environmental conditions will be described. Results of preliminary simulations using a regional cloud system model (MM5) and a CRM will be discussed. Focal science questions for the model comparison are strongly based on results of the idealized GCSS WG2 cirrus cloud model comparison projects (Idealized Cirrus Cloud Model Comparison Project and Cirrus Parcel Model Comparison Project), which will also be briefly summarized.

Starr, David OC.↗
NASA NTRS2002

NETMARK

This presentation discuss NASA's proposed NETMARK knowledge management tool which aims 'to control and interoperate with every block in a document, email, spreadsheet, power point, database, etc. across the lifecycle'. Topics covered include: system software requirements and hardware requirements, seamless information systems, computer architecture issues, and potential benefits to NETMARK users.

Maluf, David A.↗
NASA NTRS2003

Cloud Modeling Using Field Project Data for the Study of Precipitation Processes

The use of cloud-resolving models (CRMs) in the study of precipitation process and their relation to the large-scale environment can be generally categorized into two approaches. The first approach is so called "cloud ensemble modeling". In this approach, many clouds of different size in various stages of their lifecycles can be present at any model simulation time. Large-scale effects are derived from observations and imposed into the model as the main forcing. The advantage of this approach is that the modeled convection will be forced to have the same intensity, thermodynamic budget and organization as the obserations.This approach will also allow CRMs to perform multi-day or multi-week time integrations. The second approach usually requires initial temperature and water vapor profiles that have a medium to large CAPE, and open lateral boundary conditions are used. The modeled clouds could be termed "self-forced convection". Model improvements, such as in the microphysics, are achieved using the second approach. In cloud ensemble modeling, accurate large-scale advective tendencies for temperature and water vapor are the main forcing for the CRMs. We found that the large-scale advective terms for temperature and water vapor are not always consistent, For example, large-scale forcing could indicate strong drying which would produce cooling in the model through evaporation but not contain large-scale advective heating to compensate. This discrepancy in forcing would cause differences between the observed and modeled latent heating profiles. Good measurements of other quantities (i.e., surface fluxes and radiation) are also required to perform variational objective analysis that computes and minimizes a "cost function" that constrains the difference between the large-scale advective forcing in temperature and water vapor. With self-forced convection, accurate vertical distributions of temperature, moisture (water vapor), and horizontal winds are required. The timing of the measurements relative to cloud development is crucial (i.e., prior to cloud triggering). Microphysical measurements (i.e., the cloud number concentration and size distribution) can also be used in this second approach but are of secondary importance with cloud ensemble modeling. In this paper, data collected during TRMM field campaigns (FCs; i.e., SCSMEX, LBA and KWAJEX) which were aimed at validating TRMM products (i.e., rainfall and the vertical distribution of latent heating) will be used to examine the impact of errors in the initial conditions (e.g.., soundings an large-scale forcing) on simulated rainfall distributions and brightness. Rainfall and precipitations simulated from a CRM will also be compared with those estimated by a schocastic model.

Tao, W.-K.↗
NASA NTRS2003

Case for Deploying Complex Systems Utilizing Commodity Components

When the International Space Station (ISS) finally reached an operational state, many of the Payload Operations and Integration Facility (POIF) hardware components were reaching end of life, COTS product costs were soaring, and the ISS budget was becoming severely constrained. However, most requirement development was complete. In addition, the ISS program is a fully functioning program with at least fifteen years of operational life remaining. Therefore it is critical that any upgrades, refurbishments, or enhancements be accomplished in realtime with minimal disruptions to service. For these and other reasons, it was necessary to ensure the viability of the POIF. Due to the to the breadth of capability of the POIF (a NASA ground station), it is believed that the lessons to be learned by other complex systems are applicable and any solutions garnered by the POIF are applicable to other complex systems as well. With that in mind, a number of new approaches have been investigated to increase the portability of the POIF and reduce the cost of refurbishment, operations, and maintenance. These new approaches were directed at the Total Cost of Ownership (TCO); not only the refurbishment but also current operational difficulties, licensing, and anticipation of the next refurbishment. Our basic premise is that technology had evolved dramatically since the concept of the POIF ground system and we should leverage our experience on this new technological landscape. Fortunately, Moore's law and market forces have changed the landscape considerably. These changes are manifest in five (5) ways that are particularly relevant to POIF: 1. Complex Instruction Set Computing (CISC) processors have advanced to unprecedented levels of compute capacity with a dramatic cost break, 2. Linux has become a major operating system supported by most vendors on a broad range of platforms, 3. Windows(TradeMark) based desktops are pervasive in the office environment, 4. Stable and affordable WindowsTM development environments and tools are available and offer a rich set of capabilities, 5. The WindowsTM 2000 provides a stable client platform, Therefore, five studies were proposed, developed, and are in the current process of deployment which dramatically reduces the cost of operations, maintenance, refurbishment, and deployment of a ground system. Restating and refining the basic premise stated earlier, it is possible to enhance operations through the replacement of hardware and software components with commodity based items wherever applicable. This will dramatically reduce the overall lifecycle cost of the project. The first study leveraged the POIF S secure, three-tier, web architecture to replace the client workstations with lower cost PC platforms. A second study initiated a review of COTS products to examine the level of added value of each product. This study included replacement of some COTS products with custom code, deletions, substitutions, and consolidation of COTS products. Studies three and four reviewed the server architectures of the data distribution systems and Enhanced HOSC System (EHS) command and telemetry system to propose migration to new platforms, both software and hardware. The final study reviewed current IP communication technologies, developed an operational model for flight operations, and demonstrated that voice over IP was practical and could be integrated into operations.

Bryant, Barry S.↗
NASA NTRS2003

Semantic Metrics for Object Oriented Design

The purpose of this proposal is to research a new suite of object-oriented (OO) software metrics, called semantic metrics, that have the potential to help software engineers identify fragile, low quality code sections much earlier in the development cycle than is possible with traditional OO metrics. With earlier and better Fault detection, software maintenance will be less time consuming and expensive, and software reusability will be improved. Because it is less costly to correct faults found earlier than to correct faults found later in the software lifecycle, the overall cost of software development will be reduced. Semantic metrics can be derived from the knowledge base of a program understanding system. A program understanding system is designed to understand a software module. Once understanding is complete, the knowledge-base contains digested information about the software module. Various semantic metrics can be collected on the knowledge base. This new kind of metric measures domain complexity, or the relationship of the software to its application domain, rather than implementation complexity, which is what traditional software metrics measure. A semantic metric will thus map much more closely to qualities humans are interested in, such as cohesion and maintainability, than is possible using traditional metrics, that are calculated using only syntactic aspects of software.

Etzkorn, Lethe↗
NASA NTRS2003

Requirements UML Tool (RUT) Expanded for Extreme Programming (CI02)

A procedure for capturing and managing system requirements that incorporates XP user stories. Because costs associated with identifying problems in requirements increase dramatically over the lifecycle of a project, a method for identifying sources of software risks in user stories is urgently needed. This initiative aims to determine a set of guide-lines for user stories that will result in high-quality requirement. To further this initiative, a tool is needed to analyze user stories that can assess the quality of individual user stories, detect sources cf software risk's, produce software metrics, and identify areas in user stories that can be improved.

McCoy, James R.↗
NASA NTRS2003

Software Requirements Analysis as Fault Predictor

Waiting until the integration and system test phase to discover errors leads to more costly rework than resolving those same errors earlier in the lifecycle. Costs increase even more significantly once a software system has become operational. WE can assess the quality of system requirements, but do little to correlate this information either to system assurance activities or long-term reliability projections - both of which remain unclear and anecdotal. Extending earlier work on requirements accomplished by the ARM tool, measuring requirements quality information against code complexity and test data for the same system may be used to predict specific software modules containing high impact or deeply embedded faults now escaping in operational systems. Such knowledge would lead to more effective and efficient test programs. It may enable insight into whether a program should be maintained or started over.

Wallace, Dolores↗
NASA NTRS2004

Transitioning to Intel-based Linux Servers in the Payload Operations Integration Center

The MSFC Payload Operations Integration Center (POIC) is the focal point for International Space Station (ISS) payload operations. The POIC contains the facilities, hardware, software and communication interface necessary to support payload operations. ISS ground system support for processing and display of real-time spacecraft and telemetry and command data has been operational for several years. The hardware components were reaching end of life and vendor costs were increasing while ISS budgets were becoming severely constrained. Therefore it has been necessary to migrate the Unix portions of our ground systems to commodity priced Intel-based Linux servers. hardware architecture including networks, data storage, and highly available resources. This paper will concentrate on the Linux migration implementation for the software portion of our ground system. The migration began with 3.5 million lines of code running on Unix platforms with separate servers for telemetry, command, Payload information management systems, web, system control, remote server interface and databases. The Intel-based system is scheduled to be available for initial operational use by August 2004 The overall migration to Intel-based Linux servers in the control center involves changes to the This paper will address the Linux migration study approach including the proof of concept, criticality of customer buy-in and importance of beginning with POSlX compliant code. It will focus on the development approach explaining the software lifecycle. Other aspects of development will be covered including phased implementation, interim milestones and metrics measurements and reporting mechanisms. This paper will also address the testing approach covering all levels of testing including development, development integration, IV&V, user beta testing and acceptance testing. Test results including performance numbers compared with Unix servers will be included. need for a smooth transition while maintaining real-time support. An important aspect of the paper will involve challenges and lessons learned. product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support. This paper will also address the deployment approach including user involvement in testing and the , This includes COTS product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support.

Guillebeau, P. L.↗
NASA NTRS2004

Integrated Risk Management Within NASA Programs/Projects

As NASA Project Risk Management activities continue to evolve, the need to successfully integrate risk management processes across the life cycle, between functional disciplines, stakeholders, various management policies, and within cost, schedule and performance requirements/constraints become more evident and important. Today's programs and projects are complex undertakings that include a myriad of processes, tools, techniques, management arrangements and other variables all of which must function together in order to achieve mission success. The perception and impact of risk may vary significantly among stakeholders and may influence decisions that may have unintended consequences on the project during a future phase of the life cycle. In these cases, risks may be unintentionally and/or arbitrarily transferred to others without the benefit of a comprehensive systemic risk assessment. Integrating risk across people, processes, and project requirements/constraints serves to enhance decisions, strengthen communication pathways, and reinforce the ability of the project team to identify and manage risks across the broad spectrum of project management responsibilities. The ability to identify risks in all areas of project management increases the likelihood a project will identify significant issues before they become problems and allows projects to make effective and efficient use of shrinking resources. By getting a total team integrated risk effort, applying a disciplined and rigorous process, along with understanding project requirements/constraints provides the opportunity for more effective risk management. Applying an integrated approach to risk management makes it possible to do a better job at balancing safety, cost, schedule, operational performance and other elements of risk. This paper will examine how people, processes, and project requirements/constraints can be integrated across the project lifecycle for better risk management and ultimately improve the chances for mission success.

Connley, Warren↗