Extension card · Fuzzy
Interval-valued intuitionistic fuzzy SAW (a DecisionMind derivation)
The form of SAW for situations where a judgement's own degree of support and degree of rejection are given not as single numbers but as intervals. The support-rejection interval, combined by weight across the criteria, descends to a single score only at the final step.
Base method
SAW →
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?
Three things change; the weighted-sum logic does not.
Cells. In crisp SAW 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. 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. The difference from intuitionistic fuzzy data is that support and rejection are themselves intervals. Criterion weights are taken from outside as crisp numbers.
Scale equalisation. Crisp SAW ratios every column to its own best value. There is no such step here, because support-rejection intervals already lie between 0 and 1. Instead, on a cost criterion, the support and rejection intervals swap places: ([μL,μU], [νL,νU]) → ([νL,νU], [μL,μU]). This is this family's counterpart to crisp SAW's ratio-to-best step; it reverses direction, not scale.
Weighted sum and defuzzification. In crisp SAW every column is multiplied by its weight and summed directly. Here, every alternative's support-rejection interval pair across the criteria is reduced directly to a single support-rejection interval pair by interval-valued intuitionistic fuzzy weighted averaging's own aggregation operation (IIFWA). This aggregation is an algebraic operator, different from crisp SAW's linear sum; its result is again a support-rejection interval pair, not yet a single number. Only at this last step does the combined interval pair descend to a single number through a score function. The score is found by subtracting the sum of the rejection bounds from the sum of the support bounds and dividing by two.
DecisionMind fixes, in this classical form, the IIFWA aggregation operator and this mean-like score function. Weights are taken from outside; the method does not generate weights.
How to Read the Output
The score ranks only this alternative set, exactly as crisp SAW's sum does; it is not a percentage or a probability, and it is not compared with another analysis.
The difference is this. Beneath the score now lies a four-number support-rejection interval that has first been combined by weight and only then reduced to a single number through a score function. Two alternatives with the same score may come from one narrow and one wide support-rejection interval; interval width shows how much experts agree on this judgement, and it does not appear in the score.
Thus instead of writing:
"According to interval-valued intuitionistic fuzzy SAW, this alternative is definitively the best"
the report should read:
"This score is a value that emerges from the weighted combination of support-rejection intervals; which alternative's interval is wider, that is, less agreed upon, must be reported separately"
When to Prefer This over the Base Method
This extension suits situations where a criterion assessment rests on a judgement, and that judgement's own degree of support and rejection is itself uncertain. An expert may answer "how much do you support this" with an interval rather than a single number, for instance when the lower and upper bound of several assessors' support-rejection scores are known but no single consensus point exists. If support and rejection already sit at a single point (interval width zero), this extra width contributes nothing, and intuitionistic fuzzy suffices. Crisp SAW's exit condition applies here too: if no compromise is acceptable on one criterion, this extension is likewise fully compensatory.
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; if this is not checked, both the support-rejection constraint (μU + νU ≤ 1) and the aggregation operation become meaningless.
Fabricating ν as 1 − μ. This zeroes the interval's width without justification and silently collapses the structure back into single-point intuitionistic fuzzy data.
Reading the score as "what percentage probability." The score is a combination of support and rejection bounds, not a probability.
Reporting without stating the defuzzification method. The score used here is a mid-point definition; other score definitions also exist in the literature, and which one was used must be stated in the report.
The governing principle is this:
In interval-valued intuitionistic fuzzy SAW, the support-rejection interval passes through a weighted combination and only descends to a single score at the very last step; interval width shows the degree of agreement among experts, and the report must state this separately.
Cases
The first case is DecisionMind's validation example: since no shared IV-SAW worked example exists in the literature, a synthetic three-alternative, three-criterion table was built that stays faithful to the formula chain. The second case is an illustrative construction.
1. Illustrative example (DecisionMind's validation example): Research-project funding allocation
A research-funding board will direct priority funding to one of three project applications. Three criteria apply: scientific originality (higher is better), feasibility (higher is better), requested budget (lower is better). Reviewers have reported their support and reservations for every project-criterion pair as an interval, because the reviewers have not reached full consensus.
| Project | Scientific originality | Feasibility | Requested budget (lower is better) |
|---|---|---|---|
| P1 | 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] |
| P2 | 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] |
| P3 | 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] |
| Weight | 0.40 | 0.35 | 0.25 |
The method swaps support and rejection on the budget criterion, reduces every project's support-rejection interval across the three criteria to a single interval pair with IIFWA, and scores it.
| Project | Score | Rank |
|---|---|---|
| P2 | 0.4995 | 1 |
| P3 | 0.3297 | 2 |
| P1 | 0.2459 | 3 |
The result reads as follows. P2 has the narrowest and highest support interval ([0.75; 0.85]) on scientific originality, the most heavily weighted criterion, and is also advantaged on the budget criterion once reversed. P3 has the strongest interval on feasibility ([0.65; 0.75]), but this is not enough to offset P2's lead on scientific originality.
The board's hesitation is this: what happens if scientific originality's weight is lowered from 0.40 to 0.05 and feasibility given 0.55? Once verified with an independent Python calculation, redistributing the weights to (0.05; 0.55; 0.40) drops P3's score to 0.3147 and P2's to 0.2777; first place passes to P3, because P3's advantage on feasibility now determines the most heavily weighted criterion.
In the report: "With the given weights (0.40; 0.35; 0.25), P2 has the highest score (0.4995). When the weight is markedly shifted towards feasibility (0.05; 0.55; 0.40), first place passes to P3; which criterion should take priority in the funding decision must therefore be separately justified."
Source: DecisionMind's IV-SAW validation example; since no shared IV-SAW worked table exists in the literature, it was built synthetically, and the expected results were derived from the manifest's formula chain (support-rejection complement, IIFWA aggregation, score). The value space follows Atanassov and Gargov's (1989) definition of interval-valued intuitionistic fuzzy sets. The scores and the weight-swap scenario were independently computed by this card's author by running the kernel directly.
2. Archiving: Choosing an institutional digital archiving system
An institution will choose one of three archiving-system proposals for the long-term storage of its paper and digital records. Three criteria apply: search-and-retrieval speed, data-integrity assurance, and installation and licensing cost (lower is better). The IT unit and the archive unit have reported their support and reservations for every proposal as an interval, because the two units do not fully agree.
The method swaps support and rejection on the cost criterion, combines the three criteria's intervals with IIFWA and scores them. Suppose the system offering the fastest access also has a low rejection on cost, and it finishes first.
The institution's hesitation is this: the width of the interval on data-integrity assurance, that is, how much the IT unit and the archive unit agree on this point, does not appear in the single score. For a system with a wide interval, integrity assurance should be additionally secured with a contract clause.
In the report: "One system comes out ahead owing to its access speed and low cost; the units' shared view on this system's data-integrity assurance spans a wide interval, and additional assurance should be sought in the contract."
3. What Not to Do
Had P1's budget criterion in the illustrative example been left unreversed (that is, with its support interval [0.55; 0.65] still read in the "support" direction), the most expensive project would have appeared advantaged on this criterion. The second error is reducing P2's scientific-originality interval from [0.75; 0.85] to a single point value (say 0.80) before calculating; this erases the real difference of opinion among the reviewers. The third error is reading P2's score of 0.4995 as "a fifty per cent probability of success"; the score only ranks these three projects relative to one another.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/iv-saw
Fishburn, P. C. (1967). Additive utilities with incomplete product sets: Application to priorities and assignments. Operations Research, 15(3), 537–542. DOI: 10.1287/opre.15.3.537
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)