Extension card · Fuzzy
Fermatean Fuzzy MOORA
The form of MOORA for situations where the sum of the cubes of a judgement's support and rejection degree does not exceed 1. It reduces every cell to a score straightaway and runs the remainder like crisp MOORA's own ratio system.
Base method
MOORA →
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 vector normalisation and ratio-system logic do not.
Cells. In crisp MOORA every cell is a single number. Here every cell is a pair of support (μ) and rejection (ν) degrees given to a judgement. The constraint is μ³+ν³≤1. Criterion weights are taken from outside as crisp numbers.
Defuzzification comes right at the start, and the vector norm is taken over the scores. Every (μ, ν) pair collapses to a single number in the very first step of the calculation, via the Fermatean score function (s = μ³ − ν³). Since the score can range from −1 to 1, 1 is added to shift it to the positive side. Crisp MOORA's vector normalisation, dividing every value by the square root of the sum of squares of the values in its column, is applied to these shifted scores; there is no separate fuzzy normalisation applied to a triangular number or a support-rejection pair.
Ratio system. The normalised scores are multiplied by the weights; for every alternative, the sum of weighted shares on the cost criteria is subtracted from the sum of weighted shares on the benefit criteria. This is exactly the same operation as crisp MOORA's ratio system, except that the input now comes from the Fermatean score.
Reference point. Although it appears as a separate step in the manifest, DecisionMind's engine for this family does not compute the reference-point approach independently of the ratio system; this step simply copies the ratio-system score as it stands. This means the only real number in this extension is the ratio-system score; "cross-checking with the reference point" is not a second, independent calculation here.
DecisionMind holds the Fermatean score function (μ³ − ν³), the +1 shift of the score, and the vector norm over these shifted scores fixed for this extension. Weights are taken from outside; the method does not produce weights.
How to Read the Output
The MOORA score is read as in crisp MOORA: it is an alternative's net advantage on beneficial criteria relative to its share on harmful criteria, and it cannot be compared with a different analysis. The difference is this: this share is not a reversible support-rejection pair, only the shifted and normalised form of the Fermatean score. If, on a given criterion, all alternatives' scores sit close together (even if their μ,ν pairs differ considerably but their scores are equal), that criterion's discriminating power weakens here too, just as in crisp MOORA.
Thus instead of writing:
"According to Fermatean fuzzy MOORA, this is the best alternative, because both the ratio system and the reference point confirmed the same result"
the report should read:
"With these weights and this alternative set, the alternative with the highest net score according to the ratio system is this one; in this family the reference point is not an independent calculation and does not count as a second confirmation"
When to Prefer This over the Base Method
This extension is considered when experts' support-rejection pairs also exceed Pythagorean fuzzy data's squared constraint (where the sum of squares exceeds 1 but the sum of cubes does not); details are on the Pythagorean fuzzy data-type card. If the two degrees already fit within the Pythagorean constraint, moving to Fermatean is not necessary, and only discriminating power is lost. Converting a measured value directly into a support-rejection pair is not modelling uncertainty but manufacturing it. The exit condition of crisp MOORA applies here too: where a criterion admits no compromise, this extension is also compensatory.
Mistakes Specific to This Extension
Violating the value domain. Every cell must satisfy μ³+ν³ ≤ 1; this is checked from the sum of cubes, not squares.
Writing ν as 1 − μ. In that case the sum is always exactly 1, and the extra room the cube constraint provides is never used.
Treating the reference-point row as an independent second result. In this family the reference point is a copy of the ratio-system score. Cross-checking the ranking by claiming "both methods gave the same result" is misleading; crisp MOORA's own warning against relying on a single ranking without testing it against the reference point applies differently in this extension: the test simply is not possible here.
Marking criterion direction wrongly. If a cost criterion is marked as a benefit criterion, that criterion's worst score is pulled towards the ideal and the ranking becomes meaningless.
The governing principle is this:
Fermatean fuzzy MOORA's cube constraint adds something only when experts' pairs genuinely exceed the Pythagorean constraint; in this engine the only real number is the ratio-system score, and the reference point is not an independent verification.
Cases
The first case is DecisionMind's validation example; the synthetic 3x3 table in the manifest has been built faithfully to the formulas and carries no literature page. The same table is also used on the [Fermatean fuzzy EDAS card](ff-edas.md), because DecisionMind's Fermatean family is tested against a shared synthetic fixture. The second case is an illustrative construction.
1. Illustrative example (DecisionMind's validation example): Choosing a raw-material supplier
A manufacturer compares three raw-material suppliers on three criteria: delivery reliability (higher is better), quality consistency (higher is better), and rejected-batch rate (lower is better). Every supplier's support and rejection on every criterion is given as a Fermatean pair (μ,ν).
| Supplier | Delivery reliability | Quality consistency | Rejected-batch rate (lower is better) |
|---|---|---|---|
| T1 | (0.70; 0.40) | (0.50; 0.50) | (0.60; 0.50) |
| T2 | (0.80; 0.30) | (0.60; 0.40) | (0.40; 0.60) |
| T3 | (0.60; 0.50) | (0.70; 0.40) | (0.50; 0.50) |
| Weight | 0.40 | 0.35 | 0.25 |
The method computes every cell's Fermatean score (μ³−ν³), shifts it by adding 1, applies vector normalisation within the column, multiplies by the weights, and subtracts the cost criterion's share from the sum of the benefit criteria's shares.
| Supplier | MOORA score | Rank |
|---|---|---|
| T2 | 0.343 | 1 |
| T3 | 0.273 | 2 |
| T1 | 0.244 | 3 |
The result reads as follows. T2 holds the highest score on delivery reliability, the most heavily weighted criterion, and is also best positioned on rejected-batch rate (lower is better); these two carry T2 ahead. T1 sits in the opposite position and finishes last.
The manufacturer's hesitation is sensitive to weight. If quality consistency's weight is raised from 0.35 to 0.70, with delivery reliability lowered from 0.40 to 0.10 and rejected-batch rate reduced to 0.20, T3 (0.381) overtakes T2 (0.372). T1 (0.281) still finishes last. This shows that T2's first place rests on the weight given to delivery reliability, and that T3 can move ahead once that weight falls.
In the report: "With the given weights, T2 is first (0.343); when quality consistency's weight is raised markedly and delivery reliability's weight lowered (0.10 / 0.70 / 0.20), T3 moves ahead (0.381 / 0.372). T2's first place is sensitive to the weight on delivery reliability."
Source: DecisionMind's Fermatean fuzzy MOORA validation example. The Fermatean score function rests on Senapati and Yager's (2020) definition; the ratio system rests on Brauers and Zavadskas's (2006) definition of MOORA. The appraisal scores and the weight-trade-off scenario have been independently recomputed by this card's author by running the kernel formulas in Python, and match the manifest's expected_primary exactly.
2. Freight: A logistics firm's choice of international carrier
A freight firm will choose among three carriers for international shipments. There are three criteria: on-time delivery rate (higher is better), customs clearance speed (higher is better), and damaged-shipment rate (lower is better). The operations team records, for every carrier, both a support and a reservation degree as a Fermatean pair, drawn from past performance reports. At some carriers both values are high together, because the reports show both strong points and serious disruptions at once.
The method computes every carrier's score, scales it with the vector norm, and computes the benefit-cost ratio. Suppose the carrier with the best customs clearance speed also came in below average (favourably) on the damaged-shipment rate, and finished first.
The firm's hesitation is this: at a carrier where support and reservation are both high, this two-sided information is lost once it collapses to a single score. The firm should carry out a separate reference check for carriers that score highly but also carry a high degree of reservation; looking at the score alone conceals this reservation.
In the report: "A carrier stands out owing to its customs clearance speed and low damage rate; the team's marked reservations about this carrier have also been recorded, and a separate reference check is recommended before contracting."
3. What Not to Do
Had the rejected-batch rate been marked "higher is better" in the illustrative example, the supplier with the most rejects would have been rewarded and the ranking would become meaningless. The second error is presenting the reference-point row in the manifest as an independent second result, claiming "both methods gave the same ranking"; in this family the reference point is a copy of the ratio system. The third error is reading T2's score of 0.343 as "a thirty-four per cent reliable supplier"; the score is only a comparison among these three suppliers.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/ff-moora
Brauers, W. K. M., & Zavadskas, E. K. (2006). The MOORA method and its application to privatization in a transition economy. Control and Cybernetics, 35(2), 445–469. (no DOI)
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
Yager, R. R. (2014). Pythagorean membership grades in multicriteria decision making. IEEE Transactions on Fuzzy Systems, 22(4), 958–965. DOI: 10.1109/TFUZZ.2013.2278989
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3