Extension card · Fuzzy
Fermatean fuzzy ARAS
Fermatean fuzzy ARAS is the form of ARAS for situations where criterion evaluation is given as both a degree of support and a degree of rejection for a judgement. These two degrees may be jointly high over a wider region than intuitionistic fuzzy allows; the method computes the ratio to the optimal alternative through these two degrees.
Base method
ARAS →
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?
Five things change; the logic of taking a ratio to the optimal alternative does not.
Cells. In crisp ARAS every cell is a single, positive number. Here every cell is a pair: a degree of supporting a judgement (μ) and a degree of rejecting it (ν). In intuitionistic fuzzy, the sum of these two cannot exceed 1; in Fermatean fuzzy the bound is wider, the sum of their cubes cannot exceed 1 (μ³+ν³≤1). This allows pairs such as μ = 0.9 and ν = 0.5, whose sum exceeds 1 but whose cube sum stays below 1, to remain valid too; that is, a judgement can be both strongly supported and strongly rejected at once, which is not possible in intuitionistic fuzzy.
Score and cost direction. A pair's score, corresponding to a single number, is μ³−ν³, ranging between −1 and 1. For a cost criterion, direction reversal is not done with crisp ARAS's 1/x operation but by swapping support and rejection (the complement); this is the same logic as the swap rule in intuitionistic fuzzy ARAS.
The optimal alternative. The optimal-alternative row is built, for every criterion, from the highest support and lowest rejection components observed; crisp ARAS's idea of "the best value on every criterion" is carried here into the support-rejection space.
Scale equalisation (shifting and normalising). Because the score can come out negative, a constant equal to the absolute value of the smallest score is first added to every score so that all become positive. These shifted scores, the optimal alternative included, are then normalised by dividing by the column sum. This is the same as crisp ARAS's dividing-by-column-sum step; only what is being divided is now the shifted score rather than the raw value.
Weighting and the utility degree. The normalised scores are multiplied by the criterion weight and summed along the row; this sum is exactly the same as crisp ARAS's optimality function. The utility degree K is the ratio of the real alternative's sum to the optimal alternative's sum.
DecisionMind fixes, in this classical form, the score function (μ³−ν³), the shifting constant, and the reversal of the support-rejection pair by complement.
How to Read the Output
The utility degree K is read as in crisp ARAS: a percentage-style benefit relative to the optimal alternative, meaningful only for this set of options and these weights. The difference is here: beneath K, a judgement's support and rejection degree first collapse into a single score, which is then shifted and normalised into a ratio. The score function (μ³−ν³) is not the only option; other score definitions exist in the literature, and which one is used affects the result.
Thus instead of writing:
"According to Fermatean fuzzy ARAS, A2 is the best option"
the report should read:
"Relative to the optimal alternative derived from this set of options, A2 has the highest utility degree (K = 0.89); this ratio is meaningful only with these weights and the μ³−ν³ score function, and must be recomputed if the weight distribution changes"
When to Prefer This over the Base Method
This extension is appropriate when criterion evaluation rests on a judgement, and the support and rejection degree of that judgement need to be expressed together more strongly than intuitionistic fuzzy allows. Example: an expert supports a supplier with high confidence while also holding a serious reservation, and these two feelings do not fit within intuitionistic fuzzy's μ+ν≤1 bound. If a criterion only states "how suitable" and there is no separate rejection evidence, this wider bound contributes nothing; intuitionistic fuzzy or plain fuzzy is sufficient. Crisp ARAS's exit condition applies here too: if no compromise is acceptable on one criterion, this extension is also fully compensatory.
Mistakes Specific to This Extension
Entering a cell without checking the cube-sum bound (μ³+ν³≤1). A pair outside this bound is invalid; applying intuitionistic fuzzy's μ+ν≤1 bound here is wrong, Fermatean fuzzy's own bound is wider and must be checked separately.
Applying 1/x instead of the complement for a cost criterion. This breaks the support-rejection pair's cube-sum bound and produces an invalid pair.
Assuming the score function (μ³−ν³) is the only correct choice and not stating it in the report. Different score definitions can give a different ranking; the function used must be stated in the report.
Ignoring the shifting constant and comparing scores directly. If negative scores are normalised without shifting, the column sum can come out negative and the utility degrees become meaningless.
The governing principle is this:
Fermatean fuzzy ARAS exists to carry strong support-rejection combinations that intuitionistic fuzzy cannot accommodate, through to a ratio against the optimal alternative; every application made without checking the cube-sum bound, or without stating the score function, corrupts this information.
Cases
The first case is DecisionMind's validation example: because no shared FF-ARAS application example exists in the literature, a synthetic table of three options and three criteria has been built faithfully to the formula chain. The second case is an illustrative construction.
1. Illustrative example: Three options evaluated on three criteria (DecisionMind validation example)
Three options (A1, A2, A3) are evaluated on three criteria (C1, C2 higher is better; C3 lower is better) with support-rejection pairs. Weights are C1 = 0.40, C2 = 0.35, C3 = 0.25.
| Option | C1 | C2 | C3 |
|---|---|---|---|
| A1 | support 0.70 / rejection 0.40 | support 0.50 / rejection 0.50 | support 0.60 / rejection 0.50 |
| A2 | support 0.80 / rejection 0.30 | support 0.60 / rejection 0.40 | support 0.40 / rejection 0.60 |
| A3 | support 0.60 / rejection 0.50 | support 0.70 / rejection 0.40 | support 0.50 / rejection 0.50 |
The method swaps support and rejection on C3 and builds the optimal option (the highest support/lowest rejection on every criterion). It then computes the scores (μ³−ν³), shifts them, ratios them to the column sum, multiplies by the weights and sums, then divides by the optimal option's sum.
| Option | Utility degree (K) | Rank |
|---|---|---|
| A2 | 0.885 | 1 |
| A3 | 0.561 | 2 |
| A1 | 0.323 | 3 |
The result reads as follows. A2 has the highest support/lowest rejection on C1, the most heavily weighted criterion, and, once its lowest raw support value on C3 (cost-oriented) is reversed, sits in the most advantageous position; being strong on both heavily weighted criteria at once makes it first. A1 is third because it is the weakest option on C1.
The board's hesitation is this: what would happen if the weight shifted to C2? Verified with an independent Python calculation, when the weights are redistributed to C1 = 0.10, C2 = 0.70, C3 = 0.20, the utility degrees come out at 0.789 for A3, 0.770 for A2 and 0.226 for A1. First place moves from A2 to A3; A1 finishes last under both weight distributions.
In the report: "With the given weights (0.40, 0.35, 0.25), A2 has the highest utility degree (K = 0.885). When the weight is shifted markedly towards C2 (0.10, 0.70, 0.20), first place moves to A3; the weight distribution should therefore be separately justified in the report."
Source: DecisionMind's Fermatean fuzzy ARAS engine's validation example; because no shared FF-ARAS application table exists in the literature, it has been constructed synthetically, with the expected results derived from the manifest's own formula chain (support-rejection complement, shifted-score normalisation, weighted sum, ratio). The figures for the weight-change scenario were independently recomputed by this card's author with the same engine.
2. Cybersecurity: Choosing a security-monitoring service provider
An organisation will choose among three external providers to monitor network security 24/7. Three criteria apply: monitoring coverage (higher is better), average incident-response time (lower is better), and annual service fee (lower is better). The organisation's information-security team reported for each firm, separately, both how much they trust it and how much reservation they hold, as a support-rejection pair; for some firms the sum of these two feelings exceeds 1, because the team holds both strong trust and a serious reservation from a past incident towards one firm.
The method compares the three firms: it swaps support and rejection for response time and cost, builds the optimal-firm row, shifts and normalises the scores, and multiplies and sums with the weights. Monitoring coverage carries the highest weight. Suppose the firm with the widest coverage also has the highest annual fee; it still comes out first, because the weight on coverage exceeds that on cost.
The team's hesitation is this: the source of the reservation about this firm is a single incident from two years ago. If the contract is signed without this reservation being confirmed by current references, the risk has been ignored; the team should either verify the reservation from a second source or lower the coverage weight and review the result again.
In the report: "With the high weight given to monitoring coverage, the firm with the widest coverage stands out. Since the reservation about this firm rests on a single past incident, verification with current references before signing the contract is recommended."
3. What Not to Do
In the illustrative example, applying crisp ARAS's 1/x operation instead of swapping support and rejection on criterion C3: this breaks the cube-sum bound (μ³+ν³≤1) and produces an invalid pair. The second error is reporting A2's utility degree of 0.885 as "88.5 per cent likely to be the correct choice"; K only shows these three options' proportional benefit relative to the optimal option, it is not a probability. The third error is skipping the score-shifting step and dividing directly by the column sum using negative values; in that case the utility degrees can change sign and the ranking becomes meaningless.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/ff-aras
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
Senapati, T., & Yager, R. R. (2019). Fermatean fuzzy weighted averaging/geometric operators and its application in multi-criteria decision-making methods. Engineering Applications of Artificial Intelligence, 85, 112–121. DOI: 10.1016/j.engappai.2019.05.012
Zavadskas, E. K., & Turskis, Z. (2010). A new additive ratio assessment (ARAS) method in multicriteria decision-making. Technological and Economic Development of Economy, 16(2), 159–172. DOI: 10.3846/tede.2010.10
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3