Common FMEA - Data Traceability Using a Common Database

With the knowledge that different types of Failure Mode and Effect Analysis (FMEA) are performed by different disciplines located in different organizational units, which have a lot of common information, the following conclusions are considered as mandatory in order to avoid duplication of work and traceability of data: ; A common FMEA database shall be used by different disciplines / departments. : The common FMEA database must enable different views - depending on information needed by the relevant user. : The common FMEA database must enable different filtering and grouping capabilities : Clear input responsibilities must be defined such that only the responsible discipline can enter relevant information. : The common FMEA database must enable links or at least easy data transfer to other analyses (such as Reliability Prediction (link), Fault Tree Analysis (FTA) (link), Preventive Maintenance Analysis (PMA) (system part) (link) and Logistic Support Analysis (LSA) (data transfer). The common FMEA database should be realized using Commercial Off-The-Shelf (COTS) software, due to cost saving reasons, and should be integrated in a software landscape including other Reliability, Availability, Maintainability, Testability and Safety (RAMTS) analyses (see last point above) to enable data links and exchange in an easy manner. The FMEA shall become the core database for Reliability, Maintainability, Testability and Safety analyses (similar to the LSA database for Integrated Logistic Support (ILS)). The main contributors to a common FMEA database and a possible workshare between the different concurrent engineering disciplines are shown at the end of the conclusion chapter.