Extension card · Fuzzy
Fermatean Fuzzy WPM (based on Senapati and Yager's 2020 foundation)
Fermatean fuzzy WPM is the form of WPM used where criterion evaluations are expressed through the support and rejection degrees given to a judgement. The constraint here is not on the sum of these two degrees but on the sum of their CUBES, and this sum must not exceed 1. The criteria are reduced to a single support-rejection pair by the weighted geometric aggregation operator (FFWG), and this pair is then resolved into a single score.
Base method
WPM →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Fuzzy →
What this data type is, when to use it, how to write it in a cell: the family's full account is here.
What Changes from the Base Method?
Two things change; the multiplicative logic does not.
Cells. In crisp WPM every cell is a single, strictly positive number. Here every cell is a support (μ) and rejection (ν) degree pair given to a judgement. The difference from intuitionistic fuzzy lies in the constraint: intuitionistic fuzzy requires μ+ν≤1, whereas here μ³+ν³≤1; the sum of cubes permits some high (μ,ν) pairs that intuitionistic fuzzy does not allow. Criterion weights are taken from outside as crisp numbers.
Direction handling and aggregation. Crisp WPM ratios every cell against its own column's best value: it divides by the largest for a benefit criterion, and divides the smallest into the cell for a cost criterion. This is WPM's single-step direction handling; it does not group columns and sum them separately. Here too, direction is handled the same way, in a single step, at the cell level: on the cost criterion, the support and rejection degrees swap places, (μ, ν) becomes (ν, μ). This is the Fermatean fuzzy counterpart of crisp WPM's "ratio every cell directly" logic. After this direction correction, every criterion is raised to a power equal to the criterion's weight and combined with the weighted geometric aggregation operator (FFWG): the combined support is computed as Πμ_j^{w_j}, and the combined rejection as the cube root of 1 − Π(1−ν_j³)^{w_j}. Support combines multiplicatively, rejection combines cube-additively; this means WPM's character of not forgiving a weak criterion is preserved in the support component, while the rejection share accumulates.
Result and defuzzification. The combined (μ, ν) pair is reduced to a single number at the final step by the Fermatean score function (s = μ³ − ν³). The score can take a value between −1 and 1; unlike crisp WPM's always-positive score, a negative score is possible here, and, as shown below, this makes it particularly fragile against a single weak criterion.
DecisionMind fixes the Fermatean score function (μ³ − ν³) and the FFWG aggregation operator in this extension. Weights are taken from outside; the method does not generate weights.
How to Read the Output
The score shows a ranking within this set of alternatives; unlike crisp WPM's score, it is not a percentage or a probability, and it can be negative. A negative score does not mean "the alternative has failed," only that the combined rejection share exceeds the combined support share; nor can it be compared with a score from a different Fermatean fuzzy WPM analysis.
The real difference lies here: because the combined support (μ) combines multiplicatively, an alternative whose support degree on a SINGLE criterion is very close to zero has its combined support driven almost to zero. The combined rejection (ν), by contrast, rises only by that criterion's rejection degree; the rejection degrees of the other criteria also enter the share. In the score formula (μ³ − ν³) there is no compensation on the support side for this "zeroing penalty," because neither crisp WPM's normalisation step nor the +1 constant found in the neutrosophic family's score function is present here. A single weak criterion can therefore turn negative the score of an alternative that is otherwise very strong on the remaining criteria.
Thus instead of writing:
"Because A1's score comes out negative, A1 is a weak alternative on every criterion"
the report should read:
"A1's score stems from a single criterion's very low support degree, which, because of multiplicative aggregation, drives the combined support share almost to zero; A1's performance on the other criteria is not visible in this score, and the T components must be examined criterion by criterion"
When to Prefer This over the Base Method
Fermatean fuzzy is used where the criteria come from a judgement rather than a measurement, and where the expert wants both the support and the rejection degree expressed at levels higher than intuitionistic fuzzy allows. That is, this extension applies once μ+ν>1 and intuitionistic fuzzy becomes invalid; where the μ+ν≤1 bound is already sufficient, intuitionistic fuzzy WPM is enough.
Crisp WPM's own exit condition applies here too: the criteria must be on a genuine ratio scale, and the matrix must be of a single type. In addition, no cell's support degree (μ) should be very close to zero; otherwise, whatever that criterion's weight, the combined score is pulled down severely.
Mistakes Specific to This Extension
Feeding an invalid pair with μ³+ν³>1 into the calculation without noticing it. This breaches the Fermatean fuzzy set's definition, and the score becomes meaningless.
Failing to notice that a single low support degree can turn the score negative. The kernel has been tested directly in Python; in the illustrative example, when one criterion's support degree was lowered from 0.7 to 0.02 (holding the rejection degree fixed), that alternative's score fell from +0.062 to −0.123. This drop occurs even if that criterion's weight is only 0.40; the reason is that FFWG combines the support component multiplicatively, and the score function (μ³−ν³) carries no normalisation term as crisp WPM's does.
Silently changing the score function. μ³−ν³ is the fixed rule here. Using μ alone, or adding an indeterminacy term, can produce a different ranking; such a change must not be made without stating it in the report.
Presenting Fermatean fuzzy as a "more advanced version" of intuitionistic fuzzy. The cube constraint only permits a wider (μ,ν) region; which constraint to use depends on the nature of the data, and is not a "better" or "worse" choice.
The governing principle is this:
In Fermatean fuzzy WPM, combined support aggregates multiplicatively; a single criterion's very low support degree can therefore inflict a penalty severe enough to turn the score negative, even where that criterion's weight is small. This is a sharper version, within Fermatean fuzzy, of crisp WPM's own trait of not forgiving a weak criterion.
Cases
The first case is DecisionMind's validation example. For the Fermatean fuzzy set family, no shared WPM application example exists in the literature that can be followed through a page and table. DecisionMind has therefore built a synthetic 3×3 table based on the F.steps formulas, and the kernel has independently recomputed and verified these figures in Python. The second case is an illustrative construction.
1. Illustrative example (DecisionMind's validation example): Scoring three suppliers on three criteria in Fermatean fuzzy terms
A firm assesses three suppliers (A1, A2, A3) on three criteria and gives their scores as support/rejection pairs (the third criterion is cost, less is better).
| Supplier | Criterion 1 | Criterion 2 | Criterion 3 (Cost) |
|---|---|---|---|
| A1 | (0.7, 0.4) | (0.5, 0.5) | (0.6, 0.5) |
| A2 | (0.8, 0.3) | (0.6, 0.4) | (0.4, 0.6) |
| A3 | (0.6, 0.5) | (0.7, 0.4) | (0.5, 0.5) |
| Direction | more is better | more is better | less is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method reverses every pair on the cost criterion to (ν, μ), raises the remaining three pairs to a power equal to their weight, combines them with FFWG, and reduces the combined pair to the μ³−ν³ score.
| Supplier | FF-WPM score | Rank |
|---|---|---|
| A2 | 0.2557 | 1 |
| A3 | 0.1174 | 2 |
| A1 | 0.0617 | 3 |
The result reads as follows: A2 holds the highest support and lowest rejection pair on the first criterion, and is also in the best position on the cost criterion once reversed; this advantage carries A2 clearly ahead once multiplicative aggregation is applied.
The firm's hesitation concerns how fragile this lead is. Whatever value the first criterion's weight is changed to (tried between 0.20 and 0.80), A2 stays first in every case. The second and third places (A1, A3), however, are sensitive to weight: when the weight is lowered below 0.40, A3 keeps second place (at a weight of 0.20, A3=0.1262, A1=0.0079); once the weight exceeds roughly 0.55–0.60, A1 overtakes A3 for second place (at a weight of 0.60, A1=0.1236, A3=0.1085). A more striking test is this: if A1's support degree on the first criterion is lowered from 0.7 to 0.02, that is, if A1 is almost entirely unsupported on this criterion, A1's score falls from +0.0617 to −0.1228, even though A1's values on the other two criteria have not changed at all. All three of these tests were independently computed in Python.
In the report: "A2 leads clearly on the multiplicative score (0.2557). This lead is robust to changes in the weights. In this family, however, a very low support degree on a single criterion can inflict a penalty severe enough to turn the score negative; every criterion's support degree has therefore been checked separately."
Source: DecisionMind's Fermatean fuzzy WPM validation example; since no application with a shared, page-and-table-traceable source exists in the literature, it has been built synthetically on the basis of the F.steps formulas (see the approval notes). The scores and the sensitivity tests were obtained by independently recomputing the kernel logic in Python.
2. Public transport: A municipality's choice of electric bus fleet supplier
A municipality will choose one of three manufacturers' proposals (M1, M2, M3) to renew its public transport fleet with electric buses. Two criteria are "more is better": range performance and ease of maintenance; the third is unit cost (less is better). The municipality's technical team has expressed, as support/rejection pairs, that it feels strong support for the manufacturers' field tests on range performance, yet also carries a degree of rejection under certain climate conditions, and that experience with ease of maintenance is still limited.
The method reverses all three proposals on the cost criterion, combines them with FFWG, and reduces the result to a score. Suppose the proposal with the highest range performance has a low support degree on ease of maintenance, so its score comes out lower than expected; a proposal with mid-range performance but a balanced position on ease of maintenance and cost then moves ahead.
The municipality's hesitation is this: the low support degree on ease of maintenance for the proposal with the highest range may have pulled its overall score down disproportionately. The municipality should not finalise its decision without first distinguishing whether this low support stems from a genuine technical weakness or simply from a lack of sufficient field data yet.
In the report: "The balanced proposal leads on the multiplicative score. The proposal with the highest range trails because of its low support degree on ease of maintenance; whether this degree stems from a lack of field data should be investigated separately."
3. What Not to Do
The first error is marking the direction of the third criterion (cost) in the illustrative example as "more is better"; this would make the most expensive supplier appear advantaged and render the ranking meaningless. A second error is reporting A2's score (0.2557) only as a final figure, without ever testing how resilient this lead is to changes in the weights. A third error is interpreting a negative score for an alternative as "a failure on every criterion"; a negative score can in fact stem from the disproportionate effect of a single weak criterion under multiplicative aggregation, and this cannot be understood without examining the T components criterion by criterion.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/ff-wpm
Senapati, T., & Yager, R. R. (2020). Fermatean fuzzy sets. Journal of Ambient Intelligence and Humanized Computing, 11, 663–674. DOI: 10.1007/s12652-019-01377-0
Miller, D. W., & Starr, M. K. (1969). Executive Decisions and Operations Research. Prentice-Hall. (no DOI; the foundational source for crisp WPM.)
Zadeh, L. A. (1965). Fuzzy sets. Information and Control, 8(3), 338–353. DOI: 10.1016/S0019-9958(65)90241-X