Extension card · Fuzzy
Interval-valued intuitionistic fuzzy EDAS (DecisionMind derivation)
Interval-valued intuitionistic fuzzy EDAS is the form of EDAS for situations where the degree of support and rejection given to a judgement is itself not a single number but an interval. The method first reduces every cell to a single score, then measures positive and negative deviation from the set's average through that score.
Base method
EDAS →
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 locating position relative to the average does not.
Cells. In crisp EDAS every cell is a single number. Here every cell consists of four numbers: the lower and upper bound of the degree of support, and the lower and upper bound of the degree of rejection. The sum of the upper bounds cannot exceed 1. A judgement such as "my confidence in this supplier is between 0.65 and 0.75, my reservation between 0.15 and 0.20" corresponds to these four numbers.
Early reduction to a score. DecisionMind's engine here follows a different route from IV-ARAS. In IV-ARAS the support-rejection interval passes through a weighted aggregation and descends to a score only in the final step. In IV-EDAS, every cell is reduced to a single score in the very first step of the calculation, before the average is even built. The score is found by subtracting the sum of the lower and upper rejection bounds from the sum of the lower and upper support bounds, then dividing by two. On a cost criterion, the support and rejection intervals are swapped before this reduction.
The average solution and the deviations. The average is the arithmetic mean of every column's scores and is now a single exact number. The positive and negative deviations are computed with the same rule as in crisp EDAS: above the average is favourable on a benefit criterion, below the average is favourable on a cost criterion. Since cost direction has already been reversed once, on the way to the score, direction is not reversed again here.
Result and defuzzification. Defuzzification happens at the start, not at the end. The assessment score is a number between 0 and 1, exactly as in crisp EDAS. The width of the support-rejection interval is not reflected in any later step of the calculation; from the moment the score is taken, the interval itself is forgotten.
DecisionMind fixes, in this extension, the score function and the order of early reduction to a score. Weights are taken from outside as crisp numbers; the method does not generate weights.
How to Read the Output
The assessment score is read in the same way as in crisp EDAS. It is a position relative to the set's own average, not a percentage or a probability, and it cannot be compared with a different analysis. The difference is here: there is no longer any interval uncertainty behind the score. Although the support-rejection interval was gathered as four numbers, the calculation runs on exact numbers from the first step onward.
Thus instead of writing:
"Because IV-EDAS carries the interval uncertainty through to the end, the result is more reliable"
the report should read:
"The support-rejection intervals were reduced to a single score in the very first step of the calculation; the resulting score is computed from these scores, and the interval's width is not reflected in it"
When to Prefer This over the Base Method
This extension is suitable when a criterion assessment rests on a judgement, and the degree of support and rejection of that judgement is itself uncertain. An expert should be able to answer "how much do I support this" with an interval rather than a single number. If support and rejection are already single points, that is, if the interval width is zero, this extra width adds nothing and intuitionistic fuzzy EDAS is sufficient. Crisp EDAS's exit condition applies here too: if no compromise is acceptable on one criterion, this extension is also fully compensatory and does not eliminate anything below a threshold.
Mistakes Specific to This Extension
Allowing the lower bound to exceed the upper bound. In every interval the lower bound must be less than or equal to the upper bound. Unless this is checked, both the upper-bound constraint and the score calculation become meaningless.
Mistaking IV-EDAS for IV-ARAS. The two extensions share the same cell shape, but the order of defuzzification is exactly reversed. In IV-ARAS the interval is carried through to the final step; in IV-EDAS it descends to a score in the first step. Reporting one as if it were the other produces a false claim about uncertainty.
Reading the score as a probability. The score is a quantity that can range between minus one and one. It can also come out negative; this is as ordinary as falling below the average.
Trusting a criterion whose score average is very close to zero. In that case the ratio of positive to negative deviation grows large, and the result for that criterion should not be used without checking the underlying data.
The governing principle is this:
In IV-EDAS the support-rejection interval descends to a single score at the very first step, before the average is even built. The interval's width does not return at any later step; the report must not confuse this early defuzzification with IV-ARAS's.
Cases
This extension has no founding literature article. The first case is DecisionMind's validation example, built while staying faithful to the manifest's formula chain (score, average, deviation, normalisation). The second case is an illustrative construction.
1. Illustrative example: Three alternatives assessed on three criteria (DecisionMind validation example)
Three alternatives (A1, A2, A3) are assessed on three criteria (C1, C2 higher is better; C3 lower is better) with support-rejection interval pairs. The weights are C1=0.40, C2=0.35, C3=0.25.
| Alternative | C1 | C2 | C3 (cost) |
|---|---|---|---|
| A1 | support [0.65; 0.75] / rejection [0.15; 0.20] | support [0.45; 0.55] / rejection [0.30; 0.40] | support [0.55; 0.65] / rejection [0.20; 0.30] |
| A2 | support [0.75; 0.85] / rejection [0.05; 0.10] | support [0.55; 0.65] / rejection [0.20; 0.30] | support [0.35; 0.45] / rejection [0.40; 0.50] |
| A3 | support [0.55; 0.65] / rejection [0.20; 0.30] | support [0.65; 0.75] / rejection [0.15; 0.20] | support [0.45; 0.55] / rejection [0.30; 0.40] |
The method swaps support and rejection on C3, reduces every cell to a single score (on C1: A1=0.525; A2=0.725; A3=0.350), builds the column average from these scores, and applies the remaining steps of crisp EDAS.
| Alternative | Assessment score | Rank |
|---|---|---|
| A2 | 1.000 | 1 |
| A3 | 0.565 | 2 |
| A1 | 0.000 | 3 |
The result reads as follows. A2's score (0.725) on C1, the heaviest criterion, is markedly above the average (0.533). On the cost-oriented C3 too, once reversed, it sits below the average, that is, in its favour. Being advantaged on both heavy criteria at once, it comes first. A1 sits in exactly the opposite position and finishes last.
The decision's hesitation: if C2's weight is raised from 0.35 to 0.65, C1's lowered from 0.40 to 0.20, and C3's from 0.25 to 0.15, the ranking reverses. When DecisionMind's engine is independently rerun with these new weights, A3 comes first at 0.939 and A2 second at 0.912. This shows how sensitive the A2-A3 ordering is to the relative weight of C1 against C2.
In the report: "With the given weights (C1=0.40, C2=0.35, C3=0.25), A2 is in the most advantageous position relative to the set's average (1.000). If C2's weight is markedly increased (C2=0.65), the ranking reverses and A3 moves ahead; the weight distribution should therefore be separately justified."
Source: DecisionMind's validation example for the IV-EDAS engine. Since no shared IV-EDAS application table exists in the literature, the table was built synthetically, and the expected results were derived from the manifest's formula chain. The assessment scores and the weight scenario were verified by this card's author independently running DecisionMind's engine (scripts/method_runner.py IV-EDAS).
2. Archiving: A municipal archive's digitisation priority
A municipal archive department must decide, because of limited scanner capacity, the order in which three collections will be digitised. The criteria are: the collection's historical importance, its risk of physical deterioration, and the digitisation workload; the last is "lower is better," because a heavier workload means more time and staff. Archive specialists have reported, for each collection, how supportive and how hesitant they are on these three criteria, as an interval; the interval also carries the difference of opinion between specialists.
The method finds each collection's score on the three criteria, measures its favourable and unfavourable deviation from the column average, combines these with weights, and sums them into a single assessment score. Suppose the collection with the highest deterioration risk also carries the heaviest workload, and it still comes first, because the weight on deterioration risk has been set higher than that on workload.
The department's hesitation is this: because the workload weight was kept low, the collection that will actually take longest to complete may have been placed first in the queue. This risk is invisible within the assessment score. If the scanning capacity is a fixed upper limit, the department should not decide on the score alone without also setting a separate ceiling on workload.
In the report: "The priority order has been shaped by the collection that stays above the average on the deterioration-risk criterion, because of the high weight given to this criterion. Since the workload weight was kept low, this criterion's effect on the ranking is limited, and a separate workload threshold is recommended if the annual scanning capacity is fixed."
3. What Not to Do
In the illustrative example, a pair where C1's support upper bound is 0.75 and rejection upper bound is 0.20, whose sum does not exceed 1, becomes invalid if the lower bounds are written the wrong way round (support [0.75; 0.65], for instance); the lower bound must always be kept smaller than the upper bound. The second error, in the archiving example, is presenting the score reduced to a single number as "the uncertainty is still being carried as an interval"; from the moment the score is taken, the interval's width appears nowhere. The third error is ignoring that C3 is a cost criterion and failing to apply the support-rejection swap; this rewards the collection with the heaviest workload by mistake.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/iv-edas
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
Atanassov, K., & Gargov, G. (1989). Interval valued intuitionistic fuzzy sets. Fuzzy Sets and Systems, 31(3), 343–349. DOI: 10.1016/0165-0114(89)90205-4
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3
Moore, R. E. (1966). Interval Analysis. Prentice-Hall. (no DOI)