Browse Topic: Maintainability and supportability
Many of the “ilities” (Reliability, Maintainability, etc) are afterthoughts in the creation of a specification, and are often relegated to a set of templated boilerplate requirements, that are largely ignored. The Reliability / Robust Design professionals often use a P-Diagram (Parameter Diagram) as a key part of understanding the system under design. A way of integrating the Reliability effort more into the mainstream of the design activity, and give them a stronger voice, is to put their P-Diagram right into the specification, before it gets released to industry. This paper describes the rationale and the manner in which to do this
ABSTRACT In order to assess a design from a supportability perspective early in a technology’s prototyping phase, TARDEC’s Systems Engineering Directorate has established a Design for Supportability (DfS) competency. This competency, under the SE umbrella, encompasses the relationship between Design for Reliability (DfR), Design for Maintainability (DfM), and Design for Logistics (DfL). The combination of DfR, DfM and DfL form a trifecta of knowledge that determines whether a developing technology will: 1) perform its intended function for the complete duration of the mission it’s designed for; 2) be designed in a way to be fixable in a reasonable amount of time using standard tools; 3) be designed to have replaceable parts as accessible as possible; 4) not increase the logistics burden for our men and women in uniform
ABSTRACT Reliability Physics simulations for electronic assemblies has matured to become best practice during specification and design. However, the potential advantages of these simulations to programs and integrators are more far reaching. This paper will explore how the simulations can be used for virtual qualification, reliability assurance, maintenance scheduling and obsolescence management. Citation: Ed Dodd, “Reliability Simulations for Electronic Assemblies: Virtual Qualification, Reliability Assurance, Maintenance Scheduling and Obsolescence Mitigation”, In Proceedings of the Ground Vehicle Systems Engineering and Technology Symposium (GVSETS), NDIA, Novi, MI, Aug. 13-15, 2019
ABSTRACT A toolchain must be functionally cohesive with a business process, especially in technical domains such as complex systems engineering. Despite the industry-wide shift towards model-based digitization within engineering organizations, there is a lack of development in implementing model-based RAMS (Reliability, Availability, Maintenance, Safety) processes. This results in a missed opportunity to create value throughout the entire system lifecycle, from conceptual design to operations. This paper proposes some reasons for this and outlines a framework for evaluating model-based toolchains in the context of the entire Engineering cycle. A model-based architecture for RAMS is proposed and contrastively evaluated with respect to SysML. Key use cases are identified, and benefits are demonstrated using Maintenance Aware Design Environment Software. Citation: J. Langton, S. Hilton, “Iterative Co-Design Of Organizational Processes and Toolchains For Model-Based Reliability
This SAE Aerospace Recommended Practice (ARP) recommends the maintainability features that should be considered in the design of aircraft wheels and brakes. The effect on other factors, such as cost, weight, reliability, and compatibility with other systems, should be weighed before incorporation of any of these maintainability features into the design
The power of advanced driver assistance systems (ADAS) continues to increase alongside vehicle code and software complexity. To ensure ADAS functionality and maximize safety, cost efficiency, and customer satisfaction, original equipment manufacturers (OEMs) must adopt a solution that allows them to mine data, extract meaningful information, send remote software updates and bug fixes, and manage software complexity. All of this is possible with an embedded telematics-based software and data management solution. Event-based logging enables OEMs to actively measure ADAS effectiveness and performance. It allows them to analyze driver behaviors, such as whether response times increase after a certain time of day, and adjust the ADAS settings to increase functionality, such as providing an earlier warning or automated response. A vertically integrated solution also enables the identification and correction of software and calibration defects for the entire vehicle life cycle through over
The Model-Based Development (MBD) paradigm is widely used for embedded controls development, with the MathWorks Simulink modelling environment being extensively used in the automotive industry. As production-scale Simulink models are typically large and complex, there exists a need to decompose them properly in order to facilitate their maintainability, understandability, and evolution. MathWorks recommends the use of three constructs for model “componentization” or decomposition: the Subsystem, Library, and Model Reference. However, a recently added construct introduced in Simulink R2014b, the Simulink Function, can also be used for this purpose, while also supporting information hiding due to the construct’s ability to be scoped and encapsulate data. This paper provides an in-depth comparison of these Simulink constructs to fully understand the differences in their reusability, sharing of program state, encapsulation, and code generation, with the goal of facilitating model evolution
This SAE Recommended Practice applies to all portions of the vehicle, but design efforts should focus on components and systems with the highest contribution to the overall average repair cost (see 3.7). The costs to be minimized include not only insurance premiums, but also out-of-pocket costs incurred by the owner. Damageability, repairability, serviceability and diagnostics are inter-related. Some repairability, serviceability and diagnostics operations may be required for collision or comprehensive loss-related causes only. Some operations may be for non-collision-related causes only (warranty, scheduled maintenance, non-scheduled maintenance, etc.). Some may be required for both causes. The scope of this document deals with only those operations that involve collision and comprehensive insurance loss repairs
Four lasers can be used for micro welding: pulsed neodymium-doped yttrium aluminum garnet (Nd:YAG), continuous wave (CW) fiber, quasi continuous wave (QCW) fiber, and nanosecond fiber. Each laser type offers unique features that work best for specific applications. Here is a comparison of the pulsed Nd:YAG laser with the three fiber laser options, and a discussion of why and when one might be chosen over the other. In some cases, several options may work; in that case, cost of ownership and serviceability can tip the scales
Four lasers can be used for micro welding: pulsed neodymium-doped yttrium aluminum garnet (Nd:YAG), continuous wave (CW) fiber, quasi continuous wave (QCW) fiber, and nanosecond fiber. Each laser type offers unique features that work best for specific applications. This article presents a comparison of the pulsed Nd:YAG laser with the three fiber laser options and discusses why and when one might be chosen over the other. In some cases, several options may work; in that case, cost of ownership and serviceability can tip the scales
This seal features dual sealing capabilities: a face seal and an axial seal. The name swan seal is derived from its cross section, which resembles a swan. Most injector designs require fuel to be delivered from an inlet fitting, through a feed arm, to the injector tip. Temperature variation from the inlet to the tip, from the cool fuel to hot combustion air, and from startup to full power, often poses a challenge due to thermal growth. One of the most challenging areas is accommodating the growth differential between a hot feed arm and a cool fuel delivery tube, which is exacerbated by the relatively long distance. Several methods have been used to allow for this including coiling the fuel tube, utilizing an O-ring sliding seal, metal C-seals, or incorporating stretchable bellows. Some of the drawbacks of these methods include limited space, poor durability at high temperatures, serviceability, long lead times, and cost. The swan seal presents a compact, high-temperature, replaceable
This SAE Aerospace Information Report (AIR) provides an overview of the issues relating to the support and supportability of software in computer-based systems. It has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The software support issues and activities summarized in this report are reasonably easy to comprehend. The reader should not be mislead into believing development of supportable software is easy to achieve. The target audience for the document includes software acquisition organizations, developers, supporters, and end-use customers
This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs
This Aerospace Information Report (AIR) is the primary vehicle for providing the survey results to industry and government. The Institute of Defense Analysis (IDA), has performed a study which concludes that computerized techniques must be developed to integrate RM&S into product design in order to permit design influence from inception throughout the product life cycle. This AIR addresses the DoD initiative for developing Computer Aided Acquisition and Logistic Support (CALS) and industry's role in its evolution. AIR 4276 provides the detailed results of an industry/government survey inquiring into the extent of computerization of RM&S into the design process. Background information describes the evolution of the survey and why it was developed. The results provide demographic information about the respondents, the existence and extent of their CALS policy and plans, the priority placed on each RM&S task, and the extent to which these tasks have been computerized into the design
SAE JA1012 (“A Guide to the Reliability-Centered Maintenance (RCM) Standard”) amplifies and clarifies each of the key criteria listed in SAE JA1011 (“Evaluation Criteria for RCM Processes”), and summarizes additional issues that must be addressed in order to apply RCM successfully
This SAE Standard establishes the requirement for suppliers to plan a maintainability program that satisfies the following three requirements: The supplier shall ascertain customer requirements. The supplier shall meet customer requirements. The supplier shall assure that customer requirements have been met
This SAE Standard for Reliability Centered Maintenance (RCM) is intended for use by any organization that has or makes use of physical assets or systems that it wishes to manage responsibly
This SAE Recommended Practice provides recommended guidelines and best practices for implementing a supportability program to ensure that software is supportable throughout its life cycle. This Implementation Guide is the companion to the Software Supportability Program Standard, SAE JA1004, that describes, within a Plan-Case framework, what software supportability performance requirements are necessary. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented via software. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software. Applicability of specific recommended practices will depend on the support-significance of the software, application domain, and life cycle stage of the software
This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers. This document is intended to be guidance for business purposes and should be applied when it provides a
This SAE Recommended Practice provides recommended guidelines and best practices for implementing a supportability program to ensure that software is supportable throughout its life cycle. This Implementation Guide is the companion to the Software Supportability Program Standard, SAE JA1004, that describes, within a Plan-Case framework, what software supportability performance requirements are necessary. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented via software. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software. Applicability of specific recommended practices will depend on the support-significance of the software, application domain, and life cycle stage of the software
This SAE Standard establishes the requirement for suppliers to plan a maintainability program that satisfies the following three requirements: The supplier and customer shall reach agreement on program requirements. The supplier shall meet customer requirements. The supplier shall assure that customer requirements have been met
This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers. This document is intended to be guidance for business purposes and should be applied when it provides a
This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs
This SAE Recommended Practice covers the use of preferred bolt and capscrew sizes, wherever applicable, on construction and industrial machinery to ease serviceability
Items per page:
50
1 – 50 of 76