MADE Module Guides > PHM Module > Nomenclature and Introduction
PHM Module User Manual: Nomenclature and Introduction
Subtitle: "Sensor Analyses & Optimization"
1. Nomenclature
| Term/Acronym | Definition |
|---|---|
| ACC | Accuracy |
| BACC | Balanced Accuracy |
| CSV | Comma Separate Values |
| TP | Component Test Point (also used elsewhere for True Positive — see context) |
| FAR | False Alarm Rate |
| FBD | Functional Block Diagram |
| FCM | Fuzzy Cognitive Mapping |
| FN | False Negative |
| FNR | False Negative Rate |
| FP | False Positive |
| LRN | Likelihood Ratio Negative |
| LRP | Likelihood Ratio Positive |
| MADE | Maintenance Aware Design Ecosystem |
| MCC | Matthews Correlation Coefficient |
| MTTF | Mean Time to Failure |
| NPV | Negative Predictive Value |
| PHM | Prognostics and Health Management |
| POD | Probability of Detection |
| PPV | Positive Predictive Value |
| SPC | Specificity |
| TN | True Negative |
| TP | True Positive |
| XML | Extensible Mark-up Language |
Note: the source nomenclature table lists "TP" twice — once for "Component Test Point" and once for "True Positive" — this is preserved from the original document; context in later sections disambiguates which meaning applies.
2. Introduction
2.1 Overview
This manual provides information about the features and processes required for a user to analyze diagnostics designs for a system using the PHM Module. The purpose of this manual is to familiarize the user with the Prognostics and Health Management (PHM) module and its functionality. The Vehicle Platform (an exemplar model and should not be used for commercial purposes) located in the MADE Example Systems Library is used throughout this manual.
2.2 Objectives
The main objective of this manual is to describe how the PHM module is used for the following:
- Analyzing a Functional Block Diagram (FBD) system to determine sensor test points
- Modify existing sensor arrangements based on user knowledge or trade-offs
- Optimizing sensor coverage using Sensor Sets
- Enter or customize sensor information into a Sensor Library
2.3 System Example
This manual requires the Vehicle System model obtained from the MADE Example Systems library viewer (Mechanical > Vehicle System). Using a different model will result in different analysis times, hierarchical structures, and may not feature all the necessary data to fully demonstrate all features in the PHM module.
2.4 User Workflows
The workflows explain the steps required to:
- Define item test point sensors (Figure 1)
- Analyze diagnostic capability for inherent and/or design sensors (Figure 2)
- Optimize diagnostic capabilities using user sensor sets (Figure 3)
(Figures 1-3 are workflow diagrams/images with no additional extractable text beyond their captions: "Defining Item Test Point Sensors"; "Analyze diagnostic capability for inherent and/or design sensors Workflow"; "Optimize Diagnostic Capability workflow".)
Source: Local MADE 3.9.1 installation: com.phm.made.help.plugin/documents/help/pdf/PHM Module Guide.pdf · retrieved 2026-07-09