ALBERT

Description: Variants of fibrinogen A α-chain (AFib) cause the most common type of hereditary renal amyloidosis in Europe and, possibly, the United States as well. Variant fibrinogen is produced in the liver, and solitary renal allografts fail within 1 to 7 years with recurrent amyloidosis. We assessed 22 AFib patients for combined liver and kidney transplantation (LKT) and report the clinical features and outcome. Twenty-one had E526V and 1, the R554L variant. Coronary atherosclerosis was identified in 68% and systemic atheromatosis in 55%. Vascular atheroma excised at endarterectomy and endomyocardial biopsies contained purely variant fibrinogen amyloid. Half had autonomic neuropathy. Six of 9 patients who underwent LKT are alive (67%), with good allograft function and no amyloidosis at median 67 months (range, 33-155 months) of follow-up. Serial technetium-99m–labeled dimercaptosuccinic acid (99mTc-DMSA) renal scintigraphy in 2 cases of preemptive LKT demonstrated preserved native kidney residual function at 5 years. Four explanted livers were used successfully for domino transplantation. Fibrinogen amyloidosis is a systemic amyloid disease with visceral, vascular, cardiac, and neurologic involvement. LKT is curative; however, cardiovascular amyloidosis may preclude this option. Our data encourage evaluation of preemptive solitary liver transplantation early in the course of amyloid nephropathy to prevent hemodialysis and kidney transplantation.

Description: This paper will describe the methodology used to allocate Reliability and Maintainability (R&M) goals to Ground Systems Development and Operations (GSDO) subsystems currently being designed or upgraded.

Description: During the shuttle era NASA utilized a failure reporting system called the Problem Reporting and Corrective Action (PRACA) it purpose was to identify and track system non-conformance. The PRACA system over the years evolved from a relatively nominal way to identify system problems to a very complex tracking and report generating data base. The PRACA system became the primary method to categorize any and all anomalies from corrosion to catastrophic failure. The systems documented in the PRACA system range from flight hardware to ground or facility support equipment. While the PRACA system is complex, it does possess all the failure modes, times of occurrence, length of system delay, parts repaired or replaced, and corrective action performed. The difficulty is mining the data then to utilize that data in order to estimate component, Line Replaceable Unit (LRU), and system reliability analysis metrics. In this paper, we identify a methodology to categorize qualitative data from the ground system PRACA data base for common ground or facility support equipment. Then utilizing a heuristic developed for review of the PRACA data determine what reports identify a credible failure. These data are the used to determine inter-arrival times to perform an estimation of a metric for repairable component-or LRU reliability. This analysis is used to determine failure modes of the equipment, determine the probability of the component failure mode, and support various quantitative differing techniques for performing repairable system analysis. The result is that an effective and concise estimate of components used in manned space flight operations. The advantage is the components or LRU's are evaluated in the same environment and condition that occurs during the launch process.

Description: This paper is to address the basics, the limitations and the relationship between component reliability and system reliability through a study of flight computing architectures and related avionics components for NASA future missions. Component reliability analysis and system reliability analysis need to be evaluated at the same time, and the limitations of each analysis and the relationship between the two analyses need to be understood.

Description: 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.

Description: A National Aeronautics and Space Administration (NASA) supported Reliability, Maintainability, and Availability (RMA) analysis team developed a unique RMA analysis methodology using cut set and importance measure analysis in order to comparison model proposed avionics computing architectures. In this paper we will present this efficient application of the RMA analysis methodology for importance measures that includes Reliability Block Diagram (RED) Analysis, Comparison modeling, Cut Set Analysis, and Importance Measure Analysis. We will also demonstrate that integrating RMA early in the system design process as a key to success by providing a fundamental decision metric supporting design selection. The RMA analysis methodology presented in this paper and applied to the avionics architectures enhances the usual way of predicting the need for redundancy based on failure rates or subject matter expert opinion. Using the REDs and the minimal cut sets, along with the Fussell-Vesely (FV) factors, importance measures are calculated for each functional element in the architectures. This paper presents an application of the FV importance measures and presents an improved methodology for using importance measures in success space (instead of failure space) to compare architectures. These importance measures are used to determine which functional element would be most likely to cause a system failure, thus, quickly identifying the path to increase the overall system reliability by either procuring more reliable functional elements or adding redundancy. This application of the RMA analysis methodology, using RBD analysis, cut set analysis, and the importance measure analysis, allows the avionics design team to better understand and compare the vulnerabilities in each of the architectures, enabling them to address the deficiencies in the design architectures more efficiently, while balancing the need to design for optimum weight and space allocations.

Description: 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.