Standards Development

Scope

This document provides guidance to manage Dependability in Realization and Utilization in the case of low volume production and not-tested or partly testable items (DRU_TBD).

The Dependability in Realization and Utilization studies presented in this standard are based on the critical parameters (CP) identified in the design dependability studies. The identification and ranking of the CPs are not strictly within the scope of Dependability in Realization and Utilization, but they are described in this standard so that the input data is formally defined, to enable the standard to be applied correctly.

For sectors where there are existing standards, methods, or processes that serve a similar purpose, it is recommended that they are checked to determine whether the standards, methods, or processes are more relevant.

Software activities that are considered as manufacturing are manufacturing process activities related to the integration of the software on the product to be delivered: Software development is essentially a design activity. The dependability of software design is guaranteed by applying specific methods. The dependability in realization approach only applies to the copying (loading and verification) of the software and any tables or libraries of data/parameters in the final product, for example to the selection of the right software version and to the integrity of the copied software.

DRU_TBD is about assessing and limiting non-compliances related to manufacturing and operational use. It is not about analyzing field data and implementing corrective actions. The continuous improvement process during realization and operation is covered by the FRACAS process which addresses all causes of failures (whereas DRU only addresses non-compliances identified as critical parameters due to manufacturing and operations).

This document addresses the non-technical aspects of manufacturing processes. It proposes a structured methodology to proportionate the manufacturing quality effort to the dependability issues.

Dependability in Realization and Utilization does not cover malicious actions.

Dependability in Realization and Utilization approach may be implemented consistently with IEC/ISO 15026 and IEC 62741.This document applies to industrial projects, in which a customer orders from a supplier a specific system that meets certain dependability requirements or where the supplier defines himself these dependability requirements. The customer may be external to the company that supplies the system or part of it.

This guide on Dependability in Realization and Utilization applies to low volume production and not-tested or partly testable items. These can include pyrotechnical, electrical, electronic, electromechanical and mechanical items.

Purpose

No relevant international standard exists about Dependability in Realization and Utilization.

DRU_TBD has been mostly implemented in France where it is considered that it significantly increases confidence in the dependability of complex systems that are not or partially tested.

A preliminary draft has been elaborated by PWI 56-27 (V0.4 – 2024-12-10) which met 7 times from June 2023 to Dec. 2024:

- DRU_TBD Scope has been discussed and improved;

- A new section of the draft addressing Dependability in Utilization has been added