Extension card · Intuitionistic
Intuitionistic fuzzy CoCoSo
IF-CoCoSo is the intuitionistic fuzzy form of CoCoSo. Here criterion assessments are expressed through a degree of support for, and a degree of rejection of, a judgement (μ, ν). Every cell is first reduced to a single Chen-Tan score. The rest of the calculation, that is scale equalisation, the additive and multiplicative measures, and the three compromise strategies, runs exactly as in crisp CoCoSo.
Base method
CoCoSo →
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?
Two things change; the five-step skeleton and the decision logic do not.
Cells. In crisp CoCoSo every cell is a single number. Here every cell is a pair, a degree of support (μ) for and a degree of rejection (ν) of a judgement; μ + ν cannot exceed 1. Criterion weights are taken from outside as crisp numbers, not as a μ/ν pair. DecisionMind does not support group decisions in this extension; every cell is either a single assessor's judgement or a single already-combined judgement.
Point of defuzzification. Here defuzzification happens at the very start. Every (μ, ν) pair is reduced, in the first step of the calculation, to a single number by the Chen-Tan (1994) score function (s = μ − ν). This score takes on the same role as the "criterion value" number that crisp CoCoSo expects. It is then scaled to the 0-1 range by direction-sensitive min-max normalisation, taken column by column: for a benefit criterion this scaling is anchored on the lowest score, and for a cost criterion it is reversed. The weighted-sum (P-like) and weighted-power-sum (R-like) measures are then computed, and finally the three compromise strategies are applied to produce the final K score; every one of these steps runs on exactly the formulas of crisp CoCoSo. The intuitionistic fuzzy structure constrains only the INPUT, that is, how μ and ν are combined and turned into a score. The OUTPUT mechanics are the same as in the crisp method.
DecisionMind fixes two things in this extension: it uses the Chen-Tan (1994) score function (μ − ν) as the defuzzification rule, and it fixes the balance coefficient in the third compromise strategy at λ=0.5. Weights are taken from outside; the method does not generate weights.
How to Read the Output
As in crisp CoCoSo, the K score is only a ranking within this particular set of alternatives, and whether the three compromise strategies agree with one another shows its robustness.
The real difference appears here. μ and ν each carry separate information: how strongly something is supported, how strongly it is rejected, how much remains undecided. This information is reduced, at the very first step, to a single difference, μ − ν, and is lost from that point on. The gap between two alternatives can look identical in the K score even when it was reached through very different support/rejection pairs. One alternative might reach the same difference through strong support and strong rejection, another through weak support and weak rejection; the two are indistinguishable in the K score. For this reason, the report should state not only the K score but also which criterion's judgement, support or rejection, is carrying the ranking.
Thus instead of writing:
"The IF-CoCoSo score is more reliable because it also takes the expert's indecision into account"
the report should read:
"The share of indecision stays in the cell only until it enters the μ − ν score; from the moment the score is computed, it is processed exactly as in crisp CoCoSo, so the robustness of the result must still be tested separately (do the three strategies agree, does the ranking break down if one judgement shifts by a single step)"
When to Prefer This over the Base Method
Use the intuitionistic fuzzy structure when criteria come from a JUDGEMENT rather than a MEASUREMENT, and when evidence for and against this judgement can be gathered separately. This is appropriate, for example, when the support and rejection given to a proposition such as "this supplier is reliable" come from separate sources, say different auditor reports or different pieces of evidence. Computing rejection as 1 − support carries none of this extension's contribution, because the result comes out no different from crisp CoCoSo.
The exit conditions of the crisp method apply here in exactly the same way. The matrix must be of a single type, and the direction of each criterion (more is better or less is better) must be marked correctly. Direction is especially critical here, because it determines which end of the score (μ − ν) is preferred. If direction is marked incorrectly, the ranking is COMPLETELY reversed; see the "What Not to Do" section below for details.
Mistakes Specific to This Extension
Forgetting the direction marker, or entering it incorrectly. In the illustrative example below, if the third criterion's direction, which is actually "less is better," is marked as "more is better," the ranking flips from A3-A2-A1 to A1-A2-A3; this is a complete reversal, not a small shift.
Feeding a pair with μ + ν > 1 into the calculation without noticing. This is an invalid intuitionistic fuzzy number; the share of indecision comes out negative and the score becomes meaningless.
All alternatives sharing the same μ − ν score in one column. In this case the denominator of the min-max normalisation goes to zero and the calculation becomes undefined; DecisionMind rejects this with a typed error (DEGENERATE_DATA_FOR_METHOD).
Silently changing the score function. Chen-Tan (μ − ν) is the fixed rule here. A different score function, for example using μ alone or adding an accuracy function such as μ + ν, can produce a different ranking. This change should never be made without stating it in the report.
The governing principle is this:
IF-CoCoSo carries the degrees of support and rejection only as far as the Chen-Tan score, at the very start of the calculation. Once the score is computed, it is crisp CoCoSo itself that carries the ranking from then on. What matters most is that the direction marker is entered correctly.
Cases
The first case is DecisionMind's engine validation fixture. The manifest's source note, "Yazdani et al., 2019, Intuitionistic Fuzzy Combined Compromise Solution," carries no journal, volume or page information, and no publication matching this title could be found on Crossref. This source is therefore not presented as a literature case; instead, a synthetic validation table built directly on the method's own formulas is used (see the approval notes). The second case is an illustrative fiction.
1. Illustrative example (DecisionMind's validation example): Choosing a software vendor for a public tender
A public agency is evaluating three software vendors (A1, A2, A3) for a new records system. Three criteria: technical competence, project delivery reliability and the judgement "this vendor carries a high data-security risk." The third criterion is a "less is better" criterion: the lower the support given to this judgement, the better the vendor. The evaluation committee has given each vendor a degree of support and a degree of rejection (μ, ν) for each judgement.
| Vendor | Technical competence | Delivery reliability | "Carries high data-security risk" |
|---|---|---|---|
| A1 | (0.70; 0.20) | (0.60; 0.30) | (0.40; 0.50) |
| A2 | (0.80; 0.10) | (0.50; 0.40) | (0.30; 0.60) |
| A3 | (0.50; 0.40) | (0.70; 0.20) | (0.20; 0.70) |
| Direction | more is better | more is better | less is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method reduces every pair to a Chen-Tan score (μ − ν), then scales the third column, reversed, by direction-sensitive min-max. It then computes the weighted-sum and weighted-power-sum measures, and combines them through the three compromise strategies (proportion, worst-case, balanced; λ=0.5).
| Vendor | Combined score (K) | Rank |
|---|---|---|
| A3 | 2.301 | 1 |
| A2 | 2.078 | 2 |
| A1 | 1.809 | 3 |
The result reads as follows. A3 scores lowest on technical competence, the most heavily weighted criterion (0.50; 0.40). But it holds the highest support and lowest rejection pair on delivery reliability, and the lowest, that is best, score on data-security risk. Together, these two more than compensate for A3's weakness on technical competence. All three compromise strategies (proportion, worst-case, balanced) give the SAME ranking (A3, A2, A1). This result has been verified by recomputing it independently in Python.
The committee had one hesitation. If the support A1 gave to the judgement "carries a high data-security risk" had dropped one notch and its rejection had risen instead, that is (0.30; 0.60) instead of (0.40; 0.50), A1's score on this criterion would improve. Giving less support and more rejection to the judgement means the evidence for low risk is stronger. This change affects not only A1 but also A2: A2 drops from second to third place, while A1 rises to second (K: A1=2.201, A2=1.551, A3=2.787). This result has been verified by recomputing it in Python. The reason is that normalisation is relative, column by column. When one alternative's score changes, the column's min-max range changes with it, so the normalised scores of the other alternatives shift as well.
In the report: "A3 leads on the combined score (2.301), and all three compromise strategies agree on this ranking. A2's second place, however, is sensitive to a single assessor's rating of A1's data-security-risk judgement: if this rating shifts by one notch, A1 and A2 swap places."
Source: DecisionMind's validation example for the IF-CoCoSo engine; the "Yazdani et al., 2019" note in the manifest record has not been used as a literature case because it carries no journal/page information and could not be verified on Crossref (see the approval notes). The combined scores and sensitivity scenario have been independently recomputed on the Chen-Tan (1994) score rule and the Yazdani et al. (2019) CoCoSo skeleton.
2. Agriculture: Choosing a producer group for a cooperative's irrigation investment
An agricultural development cooperative will allocate a limited support budget to one of three producer groups (A1, A2, A3) as a new irrigation-system investment. Three criteria: the urgency of irrigation need (a judgement based on field experts' observation reports), soil productivity potential (likewise an expert judgement), and the judgement "this group carries a high risk of failing to complete the investment on time" (less is better). Field experts have given each group degrees of support and rejection for these three judgements.
The method reduces every judgement to a Chen-Tan score, scales the third criterion, reversed, computes the additive and multiplicative measures, and combines them through the three compromise strategies. Suppose the group with the most urgent irrigation need also carries the highest completion risk, and so comes second; the group with the highest soil productivity and a moderate risk level comes first.
The cooperative also had a hesitation at one point. If the weight of the irrigation-urgency criterion is raised, that is, if the budget priority shifts towards "most urgent need," the first- and second-placed groups could swap. The cooperative should therefore base its decision not only on the current weights, but also on how readily the ranking flips when weighting priorities change.
In the report: "With the current weights, the group with the highest soil productivity leads; if the weight given to the urgency of irrigation need is raised, the group with the most urgent need could move ahead, so the choice of weighting should be separately confirmed with the cooperative's management board."
3. What Not to Do
The first mistake, in the illustrative example, is marking the direction of the third criterion incorrectly. The judgement "carries a high data-security risk" is "less is better," and entering it as "more is better" runs the scaling in the wrong direction. In that case the ranking reverses completely, from A3-A2-A1 to A1-A2-A3. This is not a small shift; it is a complete reversal of the ranking. The second mistake is failing to notice that the support/rejection pair given to A1's data-security-risk judgement also affects the normalised scores of the other alternatives. Reporting this as "a change affecting only A1" is wrong, because a column's min-max range depends on EVERYONE's score in the alternative set. The third mistake is reading the combined K score, a value above 1 such as 2.301, as a confidence percentage, and comparing it directly with μ or ν. The K score is by then a crisp ranking value derived from μ and ν; it is not a probability.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/if-cocoso
Yazdani, M., Zarate, P., Zavadskas, E. K., & Turskis, Z. (2019). A combined compromise solution (CoCoSo) method for multi-criteria decision-making problems. Management Decision, 57(9), 2501–2519. DOI: 10.1108/MD-05-2017-0458
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3
Chen, S.-M., & Tan, J.-M. (1994). Handling multicriteria fuzzy decision-making problems based on vague set theory. Fuzzy Sets and Systems, 67(2), 163–172. DOI: 10.1016/0165-0114(94)90084-1
Xu, Z. (2007). Intuitionistic fuzzy aggregation operators. IEEE Transactions on Fuzzy Systems, 15(6), 1179–1187. DOI: 10.1109/TFUZZ.2006.890678