Extension card · Fuzzy
Fermatean Fuzzy PROMETHEE (Akram and Bibi, 2023)
Fermatean fuzzy PROMETHEE is the form of PROMETHEE for situations where multiple decision-makers' judgements are expressed with a linguistic term and a shift, and where support and rejection are also stated separately. It combines the judgements into a single number, then ranks alternatives with crisp PROMETHEE's own preference function 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)
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?
Four things change; the logic of the preference function and the flows does not.
Cells. In crisp PROMETHEE every cell is a single number. Here every cell consists of four parts: a term and a small shift for the support side, and a separate term and shift for the rejection side. The term is chosen from a pre-declared, nine-term linguistic scale (from weakest to best); the shift is the same 2-tuple idea found on the linguistic data-type card, and it prevents information loss. The sum of the cubes of the numerical counterparts of the support and rejection terms cannot exceed 1; this admits a wider region than intuitionistic fuzzy data, so a judgement can be both strongly supported and strongly rejected. This extension directly supports group decisions: judgements given in this form by multiple decision-makers are combined, each with its own weight, into a single shared judgement. Criterion weights can likewise be collected from multiple decision-makers in the same form; DecisionMind combines them and then converts them into a single number for use.
Reducing the difference to a single number. In crisp PROMETHEE the difference between two alternatives on a criterion is a straight subtraction. Here every shared judgement is first reduced to a single number by a score function (in the logic of the support side's cube minus the rejection side's cube); the difference is then taken between these reduced numbers. This does the same job as the centroid reduction in fuzzy PROMETHEE: it produces a real number that can be compared against the preference function's thresholds. Everything after this step, the preference function, the entering and leaving flows and the net flow, is exactly the same as crisp PROMETHEE's own steps.
Preference function and flows. The default preference function is the thresholdless Gaussian form (spread 0.5); crisp PROMETHEE's simplest, absolute, function can also be chosen. The function type and spread are settings exposed to the user. The reduced difference is passed through this function, multiplied by the criterion weight and summed; the entering and leaving flows are computed with the same average definition as crisp PROMETHEE.
Result and defuzzification. The output, as in crisp PROMETHEE, is directly a single net flow number. The uncertainty, that is, the term-shift and support-rejection structure, has already been consumed by the score function before the pairwise comparison; it is not carried through to the result in layered form.
DecisionMind holds fixed, for this entry point, the combination of multiple decision-makers' judgements and weights, the early defuzzification through the score function that follows, and crisp PROMETHEE's own preference-function/flow mechanics.
How to Read the Output
The net flow is read as in crisp PROMETHEE: it is assessed together with the entering and leaving flows, and it cannot be compared with a score from a different method. See the PROMETHEE card.
The difference is here: this net flow has already reduced both the views of multiple decision-makers and every judgement's term-shift and support-rejection structure to a single number at the very first step. In the literature example below, the gap between the highest net-flow candidate and the second is large, and this gap is preserved even when the preference function is changed from Gaussian to the simplest type; the position of the second- and third-ranked candidates, however, is sensitive to this choice.
Thus instead of writing:
"According to FF-PROMETHEE, T5 is the best candidate"
the report should read:
"Four decision-makers' term-shift and support-rejection judgements have been combined and processed with the Gaussian preference function; T5's net flow of 4.51 is clearly first, and this first place is preserved even when the preference function type is changed; the position of the second- and third-ranked candidates, however, is sensitive to this choice"
When to Prefer This over the Base Method
Use this when multiple decision-makers' judgements need to be combined, and these judgements are expressed both with a linguistic term and with a separate support-rejection split. This is Akram and Bibi's (2023) own field of application: a corporate personnel selection in which several assessors report, separately, how strongly they support and how much reservation they hold on criteria such as "leadership" and "technical skill".
If the criteria are measured, or if there is only one decision-maker, this layered structure adds no information; a measured criterion could be pinned to the highest term with zero shift and its rejection side set to the lowest term, but this only repeats crisp PROMETHEE in a more complicated form. Crisp PROMETHEE's own exit conditions apply here too: if the number of alternatives exceeds fifty, the pairwise-comparison burden grows; if a full ranking is not needed but an honest partial relation is, PROMETHEE I's reading should be considered.
Mistakes Specific to This Extension
Violating the value space. The sum of the cubes of the numerical counterparts of the support and rejection terms must not exceed 1; otherwise the score function is pushed into an invalid range.
Taking decision-maker weights as equal without question. If multiple decision-makers' judgements are combined with equal weight, this is an assumption; if one decision-maker is less familiar with the subject, equal weighting can give that person's view undue prominence.
Leaving the preference function type and spread at their defaults without question. The Gaussian spread (default 0.5) determines how much a small difference is treated as a preference; this value should be calibrated to the criterion's own scale, and the choice should be stated in the report.
Passing over the direction of the difference on a cost criterion without confirming it. According to the founding paper, the sign of the difference must be reversed on cost criteria. In the example below, this step does not come into play because all the criteria are "higher is better"; if a "lower is better" criterion is to be added, whether the direction reversal has been applied correctly must be separately tested before the calculation.
The governing principle is this:
FF-PROMETHEE's contribution is to reduce multiple decision-makers' linguistic, support-rejection judgements honestly to a single number and carry it into PROMETHEE's own preference mechanics; if the assumptions behind this reduction (decision-maker weight, preference function, direction) are not stated, the result is left unjustified.
Cases
The first case is a literature case: the bank branch manager selection example from Akram and Bibi's (2023) paper. The second case is an illustrative construction.
1. HR: Choosing a bank branch manager among seven candidates (Akram and Bibi, 2023)
A bank is assessing seven candidates (T1-T7) for a branch manager position on six criteria: leadership, personal qualities, managerial competence, technical skill, customer service and experience; all six are "higher is better". Four assessors participate with equal weight (0.25 each); each assessor scores every candidate on every criterion with a nine-term linguistic scale, stating the support and rejection side separately. Weights, too, have been collected from the assessors and combined: leadership 0.167, personal qualities 0.169, managerial competence 0.190, technical skill 0.107, customer service 0.169, experience 0.199. The four assessors' separate judgements and the full decision matrix appear at decisionmind.app/library/ff-promethee; the combined shared judgement of the four assessors is used here.
The method reduces every shared judgement to a single number with the score function, processes the pairwise differences with the Gaussian preference function (spread 0.5), combines them with the weights, and computes the entering and leaving flows. This calculation has been independently reproduced in Python and matches DecisionMind's own verification values to a tolerance of 1e-9, and the ranking in the paper's Table 16 exactly.
| Candidate | Net flow (Φ) | Rank |
|---|---|---|
| T5 | 4.505 | 1 |
| T4 | 2.042 | 2 |
| T6 | 1.988 | 3 |
| T3 | 1.774 | 4 |
| T2 | -1.400 | 5 |
| T1 | -4.151 | 6 |
| T7 | -4.758 | 7 |
The result reads as follows. T5 is a candidate strongly supported on almost every criterion in the four assessors' shared judgement, and its net flow is more than double that of T4, the second-placed candidate; this first place is robust by a clear margin. The gap between T4 and T6, however, is small (2.042 against 1.988).
The bank's hesitation is this: when the preference function is changed from Gaussian to the simplest type (computed by independently rerunning the same algorithm in Python), T5 is still first. But T4 and T6 swap places; T6 becomes second and T4 third. This shows that T5's first place is independent of the preference-function choice, whereas the T4-T6 ordering is sensitive to it.
In the report: "With the four assessors' combined judgement, T5 is clearly the first candidate with a net flow of 4.505, and this result is independent of the preference-function type. The second-third ranking between T4 and T6, however, swaps when the preference function is changed from Gaussian to the simplest type."
Source: Akram, M., & Bibi, R. (2023). Multi-criteria group decision-making based on an integrated PROMETHEE approach with 2-tuple linguistic Fermatean fuzzy sets. Granular Computing, 8, 917–941, pages 927-933 (the bank manager selection application). The net flow values are taken from the paper's Table 16; DecisionMind's kernel code has been verified by independently reproducing these figures line by line in Python.
2. Higher education: A university's assessment of dean candidates
A university will choose among four candidates (T1, T2, T3, T4) to appoint a new dean to a faculty. The criteria are academic leadership, institutional relationship management and strategic vision, all "higher is better". Three assessors, two members of the university senate and one external consultant, score every candidate on every criterion with a nine-term scale, stating the support and rejection side separately; the external consultant's view is given a lower weight than the senate members' because they know the candidate pool less well.
The method combines the three assessors' judgements with their own weights, reduces them with the score function, processes the pairwise differences with the Gaussian preference function, and finds the net flows. Suppose the candidate most strongly supported on academic leadership is the candidate assessed with the weakest support on institutional relationship management. Even so, this candidate comes first on net flow, because the weight on academic leadership exceeds that of the other two criteria.
The senate's hesitation is this: because the external consultant's weight is kept low, the consultant's reservation about institutional relationships may not show up sufficiently in the net flow. The senate should not finalise the decision without raising the consultant's weight and recalculating.
In the report: "With the high weight given to academic leadership, one candidate stands out clearly. The external consultant's reservation about institutional relationships has limited effect owing to its low weight, and reviewing this weight is recommended."
3. What Not to Do
In the first case, combining none of the four assessors' judgements and instead using only one assessor's scores as the "representative view" silently discards the information held by the other three assessors. The second error is using the Gaussian preference function's spread (0.5) unchanged when the criteria's actual scale differs greatly, for example a 0-100 scoring system; in that case almost every difference is treated as negligible and the idea of graded preference disappears. The third error is reporting the small gap between T4 and T6 as "T4 is definitely better" without checking the preference-function choice; this ranking is sensitive to the preference-function type.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/ff-promethee
Akram, M., & Bibi, R. (2023). Multi-criteria group decision-making based on an integrated PROMETHEE approach with 2-tuple linguistic Fermatean fuzzy sets. Granular Computing, 8, 917–941. DOI: 10.1007/s41066-022-00359-6
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
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
Herrera, F., & Martínez, L. (2000). A 2-tuple fuzzy linguistic representation model for computing with words. IEEE Transactions on Fuzzy Systems, 8(6), 746–752. DOI: 10.1109/91.890332
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