Extension card · Hesitant
Hesitant fuzzy linguistic PROMETHEE (Liang, Wang and Zhang, 2018)
Hesitant fuzzy linguistic PROMETHEE is the form of PROMETHEE for situations where a judgement is given not as a single verbal term but as more than one possible term (such as "between good and very good"). It reduces every cell to a closeness degree relative to the best term, then ranks alternatives with crisp PROMETHEE's same pairwise comparison and flow logic.
Base method
PROMETHEE →
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?
Three things change; the logic of the preference function and the flows stays the same.
Cells. In crisp PROMETHEE every cell is a single number. Here every cell is more than one term given together, chosen from a linguistic term set announced in advance (from "very bad" to "very good," terms ordered s₀ to s₆). This honestly carries situations such as the decision-maker being unable to decide between "good" and "very good," or several experts proposing different terms; it does not reduce them to a single term too early. Criterion weights remain crisp; this extension carries more than one decision-maker's judgement not through a separate aggregation step, but directly through the multi-term set in the cell itself.
Reduction to a closeness degree. In crisp PROMETHEE, the difference between two alternatives on a criterion is a direct subtraction. Here, the set carrying the highest term among all alternatives is first declared the "positive ideal" for each criterion. The average of every cell's terms is then scaled against this ideal; this ratio is combined with a parameter called "risk attitude" (risk-seeking, risk-averse or neutral) and converted into a single closeness degree (RC) between 0 and 1. The difference is taken between these closeness degrees and passed through the preference function; everything after this, that is the positive and negative flows and the net flow, is identical, step for step, to crisp PROMETHEE.
Cost direction. In crisp PROMETHEE, the difference is reversed on a cost criterion. Here the term set itself is reversed: every term in the sequence is moved to its mirror position in the term order (on a seven-term scale, for example, s₁ becomes s₅). This preserves the criterion's lower-is-better meaning at the linguistic-term level.
For this entry, DecisionMind fixes the derivation of the positive ideal from all alternatives, and the closeness-degree formula. The default preference function and risk attitude (neutral, 0.5) are the engine's own defaults; neither is currently offered as a setting adjustable from the interface, and both can only be changed through advanced input.
How to Read the Output
The net flow is read as in crisp PROMETHEE: it is assessed together with the positive and negative flows, and it cannot be compared with another method's score. See the PROMETHEE card.
The difference is this: the net flow has already reduced both the term uncertainty and the risk attitude to a single closeness degree at the first step. The default preference function ("usual") looks only at the sign of the difference between two alternatives, not its magnitude. So if an alternative is already ahead by a clear margin, widening that margin further does not change the net flow; the method gives no extra credit to an alternative that is "already winning." This is confirmed in the illustrative example below: if A1's advantage on one criterion is widened further, the net flow stays the same, but when A3, already behind, is improved on the same criterion, its net flow genuinely rises.
Thus instead of writing:
"According to HFL-PROMETHEE, A1 is by far the best alternative"
the report should read:
"With the 'usual' preference function chosen, A1 ranks first with a net flow of 0.80; this superiority shows only which alternative is ahead on which criterion, not the size of the gap"
When to Prefer This over the Base Method
Use this extension where the decision-maker expresses a judgement not as a single verbal term but with several terms, as in "between this term and that term," or where several experts propose different terms. A typical setting is a board decision where experts cannot agree on a single term for an unmeasurable criterion such as service quality or organisational fit.
Where criteria are already measured or can be comfortably expressed with a single term, this layered structure adds no information; a single term can be written as a one-element set, but this only repeats crisp or linguistic PROMETHEE in a more complicated form. Crisp PROMETHEE's exit conditions apply here too: if the number of alternatives exceeds fifty, the pairwise-comparison burden grows; where an honest partial relation rather than a full ranking is needed, PROMETHEE I's reading should be considered.
Mistakes Specific to This Extension
Changing the term-set size from expert to expert. If one expert uses a seven-term scale and another a five-term scale, the same term ("good," say) corresponds to a different numerical value, and the cost-direction reversal is thrown off too. The scale must be declared once, before the analysis.
Leaving the risk attitude at its default (neutral) without ever questioning it. This attitude only changes the result together with a magnitude-sensitive preference function (other than usual); when working with the usual function, the attitude has no effect on the result at all, and this should be reported.
Assuming that widening an "already winning" alternative's gap will also widen its net flow. This is not true under the usual preference function; the net flow looks only at who outranks whom, not by how much.
Not equalising hesitant sets of different sizes (two terms in one cell, four in its neighbour, say) before comparing them. The averaging step does this implicitly, but if the sets were built inconsistently (not drawn from the same scale), the average becomes meaningless.
The governing principle is this:
Hesitant fuzzy linguistic PROMETHEE's contribution is to carry a judgement set honestly, without asking too early which term is exactly right. If which scale the set was drawn from, and which preference function processed it, are not stated, the net flow is left unjustified.
Cases
The first case is DecisionMind's validation example: it is a small table built by hand, following the formulas in Liang, Wang and Zhang's (2018) paper step by step, and it is not carried over from the paper's own table. The second case is an illustrative construction.
1. Illustrative example: Choosing a licence among three software vendors (DecisionMind validation example)
An organisation will choose among three software vendors. Three criteria apply: integration speed, support quality and data security; all three are higher is better and are assessed on a seven-term linguistic scale (s₀ to s₆, s₆ best). The board could not settle on a single term in some cells, and gave several adjoining terms together. The criteria are weighted 0.4 / 0.3 / 0.3, the risk attitude is set to neutral (0.5), and the preference function is "usual."
| Vendor | Integration speed | Support quality | Data security |
|---|---|---|---|
| A1 | s₄–s₆ | s₃–s₄ | s₅–s₆ |
| A2 | s₃–s₄ | s₅–s₆ | s₄–s₅ |
| A3 | s₂–s₃ | s₄–s₅–s₆ | s₃–s₄ |
| Direction | higher is better | higher is better | higher is better |
| Weight | 0.4 | 0.3 | 0.3 |
The method declares the set carrying the highest term on each criterion as the positive ideal, scales every cell's average term against this ideal and combines it with the risk attitude to derive a closeness degree (RC), then passes the difference between these degrees through the "usual" preference function.
| Vendor | RC (E1, E2, E3) | Φ⁺ (positive) | Φ⁻ (negative) | Φ (net flow) | Rank |
|---|---|---|---|---|---|
| A1 | 0.833 / 0.583 / 0.917 | 1.4 | 0.6 | 0.8 | 1 |
| A2 | 0.583 / 0.917 / 0.750 | 1.3 | 0.7 | 0.6 | 2 |
| A3 | 0.417 / 0.833 / 0.583 | 0.3 | 1.7 | -1.4 | 3 |
The result reads as follows. A1 has the highest closeness degree on integration speed, and although it trails on support quality, it comes out first on net flow. A3 reaches a good closeness degree on support quality, but has the lowest degree on the other two criteria, and is the only vendor with a negative net flow.
The organisation's hesitation is this: if A1's advantage on integration speed were exaggerated further (its term raised from s₄–s₆ to s₅–s₆), would the net flow change? Calculated by running the same algorithm independently in Python: it does not, because the "usual" preference function looks only at which vendor is ahead, not by how much. By contrast, if A3's integration-speed term is raised by one step (from s₂–s₃ to s₃–s₄), A3's net flow rises from -1.4 to -1.0; the order does not change, but the gap narrows. When the board changes the preference function to a magnitude-sensitive type (v-shape, say), the risk attitude (risk-averse at 0.8, instead of neutral) is then seen to affect the size of the net flows too; this setting can currently only be changed through advanced input.
In the report: "With a neutral risk attitude and the 'usual' preference function, A1 ranks first with a net flow of 0.80. This ranking rests on the direction of A1's advantage, not its magnitude; if a magnitude-sensitive preference function is chosen, the result should be recalculated."
Source: This case is DecisionMind's validation example for the HFL-PROMETHEE engine. It has been built as a small, hand-computable table by following, step by step, the formulas in Liang, Wang and Zhang's (2018) paper (the projection-based closeness degree, Equations 10-21); it is not a worked example from the paper. The RC values and the net flow were independently recalculated with the same algorithm by this card's author, and matched the manifest's expected values within a tolerance of 1e-9.
2. Public transport: A municipality choosing a new electric-bus fleet supplier
A municipal company will choose among three suppliers for an electric-bus fleet. Three criteria apply: range performance, ease of maintenance and local-parts ratio; all three are higher is better. The technical panel assessed range performance not with measured data but with field-test impressions, and therefore with multi-term linguistic expressions such as "between good and very good." The weights are distributed so that range performance carries the most weight.
The method compares the three suppliers two at a time, calculates the closeness degrees on every criterion, and finds the net flows. Suppose the supplier with the highest local-parts ratio also has the lowest closeness degree on range performance, and finishes third on net flow, because the weight on range performance is close to the combined weight of the other two criteria.
The panel's hesitation is this: because the range-performance assessment rests on field-test impressions, there is a one-step uncertainty over whether to say "between good and very good" or "very good." If the lowest-ranked supplier's order does not change when this step is raised, the result is robust to this uncertainty; if it does change, the panel should request further field testing.
In the report: "With the high weight given to range performance, one supplier comes out clearly ahead; the supplier with the high local-parts ratio falling behind is sensitive to a one-step change in the linguistic assessment of range performance, and further field testing is therefore recommended."
3. What Not to Do
In the illustrative example, reporting that "raising A1's integration-speed term from s₄–s₆ to s₅–s₆ also increases the net flow" is wrong under the usual preference function; the net flow does not change. The second error is allowing one expert to use a seven-term scale and another a five-term scale, and comparing the terms directly; the scale is singular and announced in advance. The third error is passing over the risk attitude without stating it, on the grounds that "the default is already correct"; the attitude only matters together with a magnitude-sensitive preference function, and this choice must be written in the report.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/hfl-promethee
Liang, R. X., Wang, J. Q., & Zhang, H. Y. (2018). Projection-based PROMETHEE methods based on hesitant fuzzy linguistic term sets. International Journal of Fuzzy Systems, 20(7), 2161–2174. DOI: 10.1007/s40815-017-0418-7
Brans, J. P., & Vincke, Ph. (1985). A preference ranking organisation method (The PROMETHEE method for multiple criteria decision-making). Management Science, 31(6), 647–656. DOI: 10.1287/mnsc.31.6.647
Brans, J. P., Vincke, P., & Mareschal, B. (1986). How to select and how to rank projects: The PROMETHEE method. European Journal of Operational Research, 24(2), 228–238. DOI: 10.1016/0377-2217(86)90044-5
Rodriguez, R. M., Martinez, L., & Herrera, F. (2012). Hesitant fuzzy linguistic term sets for decision making. IEEE Transactions on Fuzzy Systems, 20(1), 109–119. DOI: 10.1109/TFUZZ.2011.2170076
Torra, V. (2010). Hesitant fuzzy sets. International Journal of Intelligent Systems, 25(6), 529–539. DOI: 10.1002/int.20418