Schweitzer Fachinformationen
Wenn es um professionelles Wissen geht, ist Schweitzer Fachinformationen wegweisend. Kunden aus Recht und Beratung sowie Unternehmen, öffentliche Verwaltungen und Bibliotheken erhalten komplette Lösungen zum Beschaffen, Verwalten und Nutzen von digitalen und gedruckten Medien.
This chapter describes what it means to Design for Maintainability (DfMn) and why DfMn is important. This chapter includes maintainability factors for design consideration and 9 DfMn paradigms. The paradigms as shown in this chapter and throughout this book provide the reader with the means to achieve a maintainable design. Using this book as a guide, the reader will be equipped with the basic elements of maintainable design that can be applied to any system or product, given an adequate amount of preparation and forethought, so that the resulting system or product design can be easily and economically maintained to obtain customer satisfaction.
This chapter explores the history, origins, and evolution of maintainability and maintenance engineering. It covers their definitions and the key standards that launched maintainability as an important engineering discipline. This chapter also explains the difference between maintainability and maintenance engineering. It also describes in detail the original maintainability program roadmap that was developed at the advent of DfMn. The various important maintainability-related tasks are described. The chapter concludes with a brief description of MIL-HDBK-470, which provides a culmination of the beneficial standards, requirements, and lessons learned over the last 60 years.
This chapter describes the tasks involved in designing for maintainability, the need for maintainability program management, the basic elements of a maintainability program plan, and the relationship of maintainability engineering to other engineering disciplines. This chapter provides an introduction to the system/product life-cycle and stresses the importance of early considerations of maintainability to ensure proper design. The earlier that the design characteristics are measured against requirements, the less time and funding are required to make changes to the design. This chapter also emphasizes that thorough and thoughtful maintainability program planning is the most effective tool in the maintainability manager's toolkit. It is important to successful design that maintainability engineering be integrated into the overall design team throughout the development program.
This chapter describes the maintenance concept as one of the most basic guiding principles for comprehensive system, subsystem, and component design. This chapter explains how the maintenance concept is central to defining and influencing sustainment plans and capabilities to allow for full life-cycle operability. The chapter includes an introduction to maintainability requirements, the categories of maintenance, the levels of maintenance, and an introduction to Integrated Logistics Support (ILS), along with the 12 elements of Integrated Product Support (IPS).
A full explanation of maintainability requirements, guidelines, and design criteria is provided in this chapter, along with a tie-in to Appendix A, System Maintainability Design Verification Checklist. This chapter describes how requirements are developed and evolve through the systems engineering process. This chapter has focused on developing, implementing, and using maintainability requirements, guidelines, criteria, and checklists. It explains the use of design criteria in the evaluation process and as input to the design process and equipment selection. Application of the design criteria by the design team is emphasized because it will ensure compliance with maintainability requirements and will support the optimization of the system's sustainability. The development of good requirements is strongly emphasized throughout this chapter since they are the key to developing a system that successfully meets the needs of the customer, and they will allow for the efficient and cost-effective maintenance of the system or product.
The chapter describes the various types of maintainability modeling and analysis techniques, including functionality analysis, functional block diagrams, maintainability allocations, maintainability design trade studies, maintainability design evaluations, maintainability task analysis, maintainability modeling, and Level of Repair Analyses (LORAs) as well as numerous additional types of maintainability analyses. The reader will be encouraged to conduct or participate in multiple design iterations in an effort to balance the maintainability, reliability, and cost of the system in the given operating environments.
This chapter describes various methodologies for performing maintainability predictions based on a popular standard, and describes the method for performing a Maintenance Task Analysis (MTA), which is used to support the maintainability prediction process. Maintainability predictions and a detailed MTA are crucial steps to ensuring that the asset will be able to achieve the desired performance objectives over its life-cycle. Using these techniques iteratively, the designer and asset owners can ensure that the best possible design is put forth within the assigned or estimated financial constraints for maintenance and logistics support over the asset's life-cycle.
This chapter discusses the meaning of Machine Learning and Deep Learning, and the differences between Machine Learning (ML), Artificial Intelligence (AI), and Deep Learning (DL). This chapter explains what Machine Learning is and how it supports Design for Maintainability activities that facilitate Preventative Maintenance Checks and Services (PMCS), Digital Prescriptive Maintenance (DPM), Prognostics and Health Management (PHM), Condition-based Maintenance (CBM), Reliability-Centered Maintenance (RCM), Remote Maintenance Monitoring (RMM), Long Distance Support (LDS), and Spares Provisioning (SP).
This chapter explains how Condition-based Maintenance (CBM) is a predictive maintenance technique to enable smart maintenance decisions by monitoring the conditions of an asset and interpreting these data to detect off-nominal behaviors or anomalies. This chapter further explains how CBM is able to dramatically reduce the man-hours needed to maintain an asset by performing maintenance only when it is needed on the specific components of the asset. Several methods are described, which will help the reader identify what maintenance should be performed on the asset. Two methods are discussed in detail in this chapter. One is Failure Modes and Effects Analysis (FMEA), which identifies the failure modes of an asset and is used to develop risk mitigation actions. A second topic is Reliability-centered Maintenance (RCM), which utilizes the FMEA and a logic tree to decide what maintenance or design actions to take.
This chapter is divided into two sections: one section for safety considerations, and a second section for human factors considerations. This chapter provides an understanding of how maintainability, safety, and human factors are intimately related to each other and how they interact to help achieve a successful maintainable design. As with other areas of concern discussed in this book, it is imperative that the human user be considered early and throughout the entire design and development process. This chapter provides a sampling of the considerations needed to ensure that systems are designed to be safe and ergonomically effective to use. This chapter also presents a sampling of the analysis techniques that can be used by the reader to achieve cost-effective maintenance while protecting the maintenance personnel and making their job easier.
This chapter describes what software maintainability is and how maintainability impacts the software design. It also presents three basic types of software maintenance methods and the five primary life-cycle processes that may be performed during the software life-cycle. The chapter also highlights some of the most relevant IEEE standards. The information in this chapter will help the reader in their effort to design for software maintainability so that maintenance will be performed economically, effectively, and efficiently over the system's life-cycle.
This chapter explains the...
Dateiformat: ePUBKopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
Das Dateiformat ePUB ist sehr gut für Romane und Sachbücher geeignet – also für „fließenden” Text ohne komplexes Layout. Bei E-Readern oder Smartphones passt sich der Zeilen- und Seitenumbruch automatisch den kleinen Displays an. Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.