Extension card · Hesitant
Hesitant Fuzzy ARAS (Mishra, Rani, Krishankumar, Ravichandran and Kar, 2021)
Hesitant Fuzzy ARAS is the form of ARAS for situations where an assessment on a criterion holds more than one plausible value at once. It weights these sets, reduces them to a single number by averaging, and computes the ratio to the optimal alternative.
Base method
ARAS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Hesitant →
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 set that holds, for the same criterion-alternative pair, more than one plausible degree; for example {0.3; 0.3; 0.4; 0.5}. In the same column, different alternatives' sets can have different lengths; unlike HF-TOPSIS, no length-equalisation step is needed here, because the set is processed by averaging rather than by distance.
Optimal alternative. The optimal-alternative row is built, for each criterion, from whichever set is best according to the average of the observed sets. For a benefit criterion the set with the highest average is chosen, for a cost criterion the one with the lowest average, and it is carried into this row unchanged; this row is then added among the real alternatives.
Scale equalisation. For a benefit criterion, every element of every set is divided by the highest average in the column (including the optimal row). For a cost criterion, this ratio is subtracted from 1. This operation is applied to each element of the set separately; once normalised, the set remains a set, and has not yet been reduced to a single number.
Weighting. Every element of the normalised set goes through an operation in which the criterion weight becomes an exponent: 1 minus (1 minus the element) raised to the power of the weight. This magnifies or shrinks every element of the set separately; the set itself still carries more than one value. Unlike HF-TOPSIS, weighting here is accepted only fully and from outside; there is no option to derive it from the data or to supply it only partially.
Result and defuzzification. Only after this step is the weighted set reduced to a single number, by taking the arithmetic mean of its own elements. These single numbers are summed across the row (over the criteria), divided by the optimal row's sum, and give the utility degree (U). The order matters here: averaging first and weighting afterwards gives a different number from weighting first and averaging afterwards, because the weighting operation is not linear.
DecisionMind holds fixed, in this classical form, the selection of the optimal row by average score, the normalise-then-weight-then-average order, and the requirement of a fully external weight.
How to Read the Output
The utility degree U carries the same meaning as K in crisp ARAS: a percentage-like benefit relative to the optimal alternative, meaningful only for this alternative set and these weights. The difference is this: beneath U now lies a set that once held more than one plausible value, first weighted and then reduced to a single number by averaging. The width of the set, that is, the agreement or disagreement among sources, becomes invisible in that single number.
Thus instead of writing:
"According to Hesitant ARAS, A1 is the best alternative"
the report should read:
"Relative to the optimal alternative derived from this alternative set, A1 has the highest utility degree (U=0.75); this ratio rests on the average of the set of plausible values on each criterion, and the width of these sets should be stated separately in the report"
When to Prefer This over the Base Method
This extension is suitable when more than one plausible and defensible value exists for the same criterion-alternative pair, for instance when several experts or several scenarios have produced this value separately. The principle on the Hesitant data-type card applies here too: the set must rest on a genuine source, and width should not be added, without justification, to a single measured value. Crisp ARAS's exit condition applies here too: this extension is also fully compensatory and performs no elimination if no compromise is acceptable on one criterion.
Mistakes Specific to This Extension
Applying crisp ARAS's 1/x operation to a cost criterion. Here the cost direction is reversed by subtracting the ratio from 1; the 1/x operation does not hold here and can push the set outside [0,1].
Averaging the set first and only then weighting. The correct order is to normalise, weight, and only then average. If the order is reversed, a different utility degree results, because the weighting operation is not linear.
Assuming the weight can be partial or derived from the data. Unlike HF-TOPSIS, this classical form accepts the weight only fully and from outside; an incomplete or interval-form weight is not an option here.
Never reporting the width of the set. When two alternatives' utility degrees come out close, whether that closeness depends on narrow or wide sets should be stated separately; U alone does not show this.
The governing principle is this:
In Hesitant ARAS, a set is normalised and weighted before it is reduced to a single number by averaging; if this order is reversed, or if the width of the set is never reported, part of the information it carries is lost.
Cases
The first case is DecisionMind's validation example: because the source paper's (Mishra et al., 2021) real example, with five drugs, seven symptoms and three experts, is too intertwined to verify by hand, a small, closed-form table showing the same formula chain has been built instead. The second case is an illustrative fiction.
1. Illustrative example: Two alternatives assessed on two criteria (DecisionMind validation example)
Two alternatives (A1, A2) are assessed with single-element sets on two criteria, one benefit (C1) and one cost (C2): A1 is {0.75} on C1 and {0} on C2; A2 is {1} on C1 and {1} on C2. Weights are equal (0.5; 0.5).
| Alternative | C1 (benefit) | C2 (cost) |
|---|---|---|
| A1 | {0.75} | {0} |
| A2 | {1} | {1} |
The method builds the optimal row from the best value on each criterion (A2's 1 on C1, A1's 0 on C2). It then normalises and weights the sets, reduces them to single numbers by averaging, and takes the ratio of the total to the optimal row's total.
| Alternative | Utility degree (U) | Rank |
|---|---|---|
| A1 | 0.75 | 1 |
| A2 | 0.50 | 2 |
The result reads as follows. Although A2 holds a perfect score (1) on C1, it also holds the worst raw value (1) on C2; these two extremes cancel each other out, pinning A2's utility degree at 0.50. A1, though not perfect on C1 (0.75), comes out ahead because it holds the best raw value (0) on C2.
The board's hesitation is this: does the ranking change if the weight distribution changes? Verified with an independent Python computation, as the weights are tried across the range from (0.1; 0.9) to (0.9; 0.1), A2's utility degree stays at exactly 0.50 every time; this is because A2 sits, on both criteria, at the extreme end of its own column (best on one, worst on the other). A1's degree varies between 0.56 and 0.86 across this range, but never falls below 0.50 at any weighting. In this example the ranking (A1≻A2) is entirely robust to the weights.
In the report: "With the given weights (0.50; 0.50), A1 has the highest utility degree (U=0.75). In this table, A2's utility degree stays fixed at 0.50 regardless of the weight distribution, because it sits at the extreme end of its column on both criteria; A1's first place is therefore preserved under every weight distribution."
Source: DecisionMind's validation example for the Hesitant ARAS engine; because Mishra and colleagues' (2021) COVID-19 drug-selection example, with five drugs, seven symptoms and three experts, is too intertwined for manual verification, a small, closed-form table has been used instead to show the same formula chain (ideal row, normalisation, scaled weighting, averaging, ratio). The utility degrees and weight sweep were independently computed by this card's author.
2. Public transport: Choosing a new bus model
A municipality will choose a new bus model for its fleet from among three candidates. Two criteria: fuel efficiency (more is better) and annual maintenance-cost score (less is better, a low score meaning less maintenance is needed). The municipality's technical team has recorded results from pilot tests under different field conditions as sets, without reducing them to single numbers.
| Model | Fuel efficiency | Maintenance-cost score |
|---|---|---|
| B1 | {0.70; 0.75; 0.80} | {0.55; 0.60} |
| B2 | {0.50; 0.55} | {0.50; 0.55; 0.60} |
| B3 | {0.60; 0.65} | {0.25; 0.30} |
The team gives fuel efficiency a weight of 0.6 and maintenance cost 0.4. The method builds the optimal model, normalises and weights the sets, and computes the utility degrees.
| Model | Utility degree (U) | Rank |
|---|---|---|
| B1 | 0.792 | 1 |
| B3 | 0.770 | 2 |
| B2 | 0.453 | 3 |
The result reads as follows. B1 has the best set on fuel efficiency, the more heavily weighted criterion; B3's clear advantage on maintenance cost (0.25–0.30 against 0.55–0.60) is not enough to overtake B1, but the gap is small (0.022).
The team's hesitation is this: what if B1's maintenance cost had come out two notches worse in the pilot tests, that is, the set {0.55; 0.60} instead of {0.65; 0.70}? Verified with an independent Python computation, under the same weights (0.6; 0.4) this would drop B3 to 0.778 and B1 to 0.762, reversing the ranking: B3 would move into first place.
In the report: "With the high weight given to fuel efficiency, B1 comes out ahead (U=0.792), but its gap to B3 is small (0.022). If B1's maintenance-cost pilot data had come out two notches worse, the ranking would reverse; B1's maintenance data should therefore be verified with further field testing."
3. What Not to Do
In the illustrative example, applying crisp ARAS's 1/x operation to C2 is wrong; this amounts to trying to invert A1's set {0} directly. Division by zero is undefined, and this does not fit at all with how the method treats the cost direction. The second error is, in the bus example, taking the average of B1's maintenance-cost set {0.55; 0.60}, namely 0.575, first and only then weighting this single number; the correct order is to normalise and weight first, leaving the average for last. The third error is writing the 0.022 gap between B1 and B3 as "B1 is definitely better"; as Case 2's hesitation shows, this gap can reverse with a single small change in one criterion's set.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/hf-aras
Mishra, A. R., Rani, P., Krishankumar, R., Ravichandran, K. S., & Kar, S. (2021). An extended fuzzy decision-making framework using hesitant fuzzy sets for the drug selection to treat the mild symptoms of Coronavirus Disease 2019 (COVID-19). Applied Soft Computing, 103, 107155. DOI: 10.1016/j.asoc.2021.107155
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
Torra, V. (2010). Hesitant fuzzy sets. International Journal of Intelligent Systems, 25(6), 529–539. DOI: 10.1002/int.20418
Xia, M., & Xu, Z. (2011). Distance and similarity measures for hesitant fuzzy sets. Information Sciences, 181(11), 2128–2138. DOI: 10.1016/j.ins.2011.01.028