Extension card · Intuitionistic
Intuitionistic fuzzy EDAS (Yıldırım & Meydan, 2021)
IF-EDAS is the form of EDAS used when criterion values are given as a degree of support for and a degree of rejection of a judgement, working with intuitionistic fuzzy numbers. The method first reduces every cell to a single score, then computes the positive and negative distances from that score against the set's own average.
Base method
EDAS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Intuitionistic →
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 decision logic does not.
Cells. In crisp EDAS every cell is a single number. Here every cell is a pair of numbers: a degree of support (μ) and a degree of rejection (ν), whose sum cannot exceed 1. If there is more than one expert (a group decision), each expert's pair is first reduced to a single pair with a weighted aggregation rule (IFWA); with a single expert this step changes nothing.
Reduction to a score. Crisp EDAS works directly on the number. Here, before the average and deviation are computed, every (μ, ν) pair is converted into a single score. The score is support minus rejection (μ − ν), a number between −1 and 1. In this way, the average-deviation logic of crisp EDAS runs not on the pair itself, but on the single number the pair summarises. The score function used here (Chen-Tan, 1994) is a chosen rule, not the only possible one.
Average solution and deviations. These steps run exactly as in crisp EDAS, but now on the score rather than the raw cell value. The method finds each criterion's average score, and measures each alternative's positive and negative deviation from that average. On a benefit criterion, being above the average is favourable; on a cost criterion, being below it is favourable. The deviation is likewise expressed as a proportion of the average's absolute value.
Result and defuzzification. Because the reduction to a score is done in the first step, the weighted sums, normalisation and assessment score proceed exactly as in crisp EDAS, on a single number. No separate defuzzification step is needed. The uncertainty is consumed at the start, that is, at the step where the μ and ν pair is reduced to a single score, not at the end.
DecisionMind fixes the Chen-Tan (1994) score function and the swapping of the PDA/NDA branches on a cost criterion in this extension. Weights are taken from outside as crisp numbers; the method does not generate weights.
How to Read the Output
The output is an assessment score and a ranking, in the same form as in crisp EDAS, and is read the same way. The score is neither a percentage nor a probability; it is a position relative to the set's own average.
But the score by itself shows only the difference between support and rejection; it does not carry the share of indecision (π = 1 − μ − ν). Two different pairs can give the same score. For example, μ=0.6, ν=0.3 and μ=0.5, ν=0.2 both give a score of 0.3, but the second has a larger share of indecision. For this reason, the report should note not only the assessment score but also the support-rejection pair behind the score.
Thus instead of writing:
"IF-EDAS gives a more reliable result because it accounts for uncertainty"
the report should read:
"Criterion assessments were given as degrees of support and rejection, reduced to a single score and ranked against the average; A3 leads with 0.75, and this ranking could change if the weight of the most heavily weighted criterion rises significantly"
When to Prefer This over the Base Method
Use this method when a criterion assessment can be expressed as a judgement, and support and rejection for this judgement can be derived from separate sources (for example, proportions of evidence for and against, or a distribution of votes). For a measured criterion, crisp EDAS is sufficient; expanding a measured value into an intuitionistic fuzzy pair by writing "ν = 1 − μ" adds no information to the structure. If the table is mixed, DecisionMind requires a single data type; a measured criterion is then also written as a pair, embedded as μ = the value itself and ν = 0. The share of indecision is zero, and no information has been added.
The same exit condition as crisp EDAS applies. If no compromise is acceptable on one criterion, this extension is also compensatory and will not eliminate anything below a threshold. A criterion whose average score is zero creates a division problem in the PDA/NDA calculation and needs separate attention. This arises on criteria where all alternatives are equally balanced between support and rejection.
Mistakes Specific to This Extension
Confusing the IFN pair with a triangular fuzzy number. IF-EDAS values are (μ, ν) pairs, not (a, b, c) triples; the constraint here is μ + ν ≤ 1, not the TFN constraint l ≤ m ≤ u.
Failing to swap branches on a cost criterion. On a cost criterion, the positive deviation is reversed to "average minus score" and the negative deviation to "score minus average." Using the benefit formula on a cost column reverses the ranking.
Forgetting the (1 −) inversion in the NSN. When normalising the negative-side total, a small negative-side total should give a large NSN (1 − ratio). Using the raw ratio directly, without applying (1 −), reverses the ranking.
Dividing by a criterion whose average score is zero. If every alternative gives the same score on a criterion, the average can come out at zero; in this case, rather than a division-by-0 error, PDA=NDA=0 is assumed for that criterion, and the calculation does not stop.
The governing principle is this:
In IF-EDAS, uncertainty enters the calculation by reducing the μ and ν pair to a single score; the score function is a chosen rule, and which rule was used must be stated in the report — changing it means the result should not be wrongly compared with crisp EDAS.
Cases
The first case is DecisionMind's validation example: the literature's IF-EDAS application papers (Yıldırım & Meydan, 2021; Dumrul et al., 2024) use multi-criteria, real financial/environmental data sets and are not hand-traceable; instead, a small single-decision-maker table, faithful to the formulas, was built synthetically and independently verified in Python. The second case is an illustrative fiction.
1. Illustrative example: Three alternatives, two criteria (DecisionMind validation example)
This example is not a literature case; it is a small table built to make IF-EDAS's steps traceable by hand. Three alternatives are assessed on two criteria with intuitionistic fuzzy pairs (support, rejection); the first criterion is "more is better," the second is "less is better" (cost).
| Alternative | K1 (μ, ν) | K2, cost (μ, ν) |
|---|---|---|
| A1 | (0.80; 0.10) | (0.70; 0.20) |
| A2 | (0.60; 0.30) | (0.50; 0.40) |
| A3 | (0.40; 0.50) | (0.30; 0.60) |
| Direction | more is better | less is better |
| Weight | 0.60 | 0.40 |
The method converts every pair to a score (μ − ν): A1 K1=0.70 K2=0.50; A2 K1=0.30 K2=0.10; A3 K1=−0.10 K2=−0.30. It finds each criterion's average score (K1=0.30, K2=0.10), measures each alternative's positive and negative deviation from these averages (reversing the branches for K2 because it is a cost criterion), multiplies by the weights and sums, normalises, and arrives at a single assessment score.
| Alternative | Assessment score | Rank |
|---|---|---|
| A3 | 0.750 | 1 |
| A2 | 0.500 | 2 |
| A1 | 0.250 | 3 |
The result reads as follows. Although A1 scores markedly above the average on K1 (weight 0.60), K2 being a cost criterion means its high support-rejection difference counts against it here, and it ends up last. A3, despite low scores on both criteria, benefits from K2's cost direction and comes first.
The decision carries one hesitation. If K1's weight is raised from 0.60 to 0.75, all three alternatives become exactly equal (all at 0.500). Above 0.75 the ranking reverses completely, with A1 first and A3 last. This shows how fragile the ranking is to K1's weight. The point of equalisation falls at exactly one weight value, 0.75.
In the report: "With the given weights (K1=0.60, K2=0.40), A3 is in the most advantageous position relative to the set's average (0.750); if K1's weight rises above 0.75, the ranking reverses completely and A1 comes first, so K1's weight should be separately justified."
Source: DecisionMind's IF-EDAS validation example; the steps apply the Keshavarz Ghorabaee et al. (2015) EDAS skeleton with the Chen-Tan (1994) score function on intuitionistic fuzzy pairs (the same skeleton as the 8-step algorithm defined by Yıldırım & Meydan, 2021). The assessment scores and the equalisation point were independently recomputed by this card's author in Python.
2. Insurance: A company's choice of reinsurance partner
An insurance company will choose one of three reinsurance partners with which to share major claim risks. Criteria: expert opinion on solvency adequacy, and expert opinion on pricing competitiveness. The second criterion is "less is better," because a high premium demand counts against a partner. The risk committee has derived support and rejection degrees for these two judgements, for each partner, from past claims-payment records and the number of committee members expressing an opposing view.
The method finds each partner's score (support minus rejection) on the two judgements, measures its positive and negative deviation from the average, combines these with the weights, and arrives at a single assessment score. Suppose one partner scores markedly above average on solvency. It also stays above average on pricing competitiveness, but since this criterion is cost-oriented, that counts against it. The partner still comes first, because solvency's weight is set higher than pricing's.
The committee has a hesitation. If a partner with expensive pricing is chosen based only on its solvency, long-term premium cost could rise. The committee should limit this risk not through the EDAS score, but through a separate pre-screening condition on a price ceiling. Otherwise, a highly scored but expensive partner could come out ahead in the ranking.
In the report: "The priority order has been shaped by the partner that scores above average on this judgement due to the high weight given to solvency; because the weight of pricing competitiveness is kept low, this criterion's effect on the ranking is limited, and a separate price ceiling is recommended if the premium budget is fixed."
3. What Not to Do
The first mistake is processing the (μ, ν) pairs in the illustrative example directly as triangular fuzzy numbers and running Fuzzy EDAS; the two data types are subject to different constraints (μ+ν≤1 versus l≤m≤u), and mixing them produces an invalid calculation. The second mistake is ignoring that K2 is a cost criterion and computing the PDA/NDA branches in the same direction as K1; this hides A3's advantage on K2 and artificially inflates A1. The third mistake is writing ν as 1 − μ and zeroing out the share of indecision; in that case the intuitionistic fuzzy structure becomes indistinguishable from crisp EDAS.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/if-edas
Yıldırım, B. F., & Meydan, C. (2021). Sezgisel bulanık EDAS (SB-EDAS) yöntemi ile finansal performans değerlendirme: BİST perakende ticaret sektöründe bir uygulama. Süleyman Demirel Üniversitesi Vizyoner Dergisi, 12(29), 235–251. DOI: 10.21076/vizyoner.734092
Dumrul, C., Bilgili, F., Zarali, F., Dumrul, Y., & Kiliçarslan, Z. (2024). The evaluation of renewable energy alternatives in Turkey using intuitionistic-fuzzy EDAS methodology. Environmental Science and Pollution Research, 31, 15503–15524. DOI: 10.1007/s11356-023-31816-7
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3
Keshavarz Ghorabaee, M., Zavadskas, E. K., Olfat, L., & Turskis, Z. (2015). Multi-criteria inventory classification using a new method of evaluation based on distance from average solution (EDAS). Informatica, 26(3), 435–451. DOI: 10.15388/Informatica.2015.57