Extension card · Fuzzy
Interval-valued intuitionistic fuzzy MARCOS (aggregated, a DecisionMind derivation)
Interval-valued intuitionistic fuzzy MARCOS is the form of MARCOS for situations where a judgement's own degree of support and degree of rejection are given not as single numbers but as intervals. The utility-ratio logic against the ideal and the anti-ideal runs on these intervals throughout.
Base method
MARCOS →
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 extended-matrix and ideal/anti-ideal ratio logic does not.
Cells. In crisp MARCOS every cell is a single number. Here every cell consists of four numbers: the lower and upper bound of the degree of support ([μL, μU]) and the lower and upper bound of the degree of rejection ([νL, νU]); the sum of the two upper bounds (μU + νU) cannot exceed 1. Criterion weights are supplied from outside as crisp (single) numbers.
Ideal and anti-ideal. In crisp MARCOS the ideal and the anti-ideal are built from the best and worst observed numbers. Here, on a benefit column, the ideal is taken as the component-wise highest of the support interval and the lowest of the rejection interval; on a cost column, the reverse is taken as ideal, and the anti-ideal is reversed accordingly.
Aggregation and defuzzification. Crisp MARCOS multiplies each row by the weights and sums it. Here each row is first combined into a single support-rejection interval pair with the interval-valued intuitionistic fuzzy weighted averaging operator (IIFWA), and this pair then descends to a single number through a score function ((μL + μU − νL − νU)/2). What remains is crisp MARCOS itself: the ratio to the ideal and the anti-ideal (K+, K−), the two utility functions and the final utility degree that combines them are built through the same steps.
DecisionMind fixes, for this classical form, the IIFWA aggregation operator and the mid-point score function; no path is followed that additionally treats interval width as a penalty or a reward.
How to Read the Output
The final utility degree is read exactly as in crisp MARCOS: a position relative to this set's own ideal and anti-ideal references (see the MARCOS card). The difference is here: this degree rests only on the mid-point of the support-rejection interval, and does not show how wide that interval is. A degree arising from a narrow interval and the same degree arising from a wide interval are indistinguishable in the final utility degree.
Thus instead of writing:
"According to interval-valued intuitionistic fuzzy MARCOS, A1 is the best alternative"
the report should read:
"The final utility degree rests only on the mid-point of the support-rejection interval; A1 comes out ahead, but this lead should not be taken as certain without separately examining how narrow or wide A1's intervals are"
When to Prefer This over the Base Method
This extension is appropriate when only an interval is known for a judgement's degree of support and degree of rejection, that is, when an expert says "support is not exactly 0.6, but somewhere between 0.5 and 0.7." Examples include supplier audits where several assessors' support-rejection scores are summarised as an interval, and committee evaluations that are deliberately left unreduced to a single crisp ratio. If support and rejection are each given as a single number (interval width zero), this extra width contributes nothing, and intuitionistic fuzzy MARCOS (IF-MARCOS) suffices. Crisp MARCOS'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, and the sum of the upper support and the upper rejection must not exceed 1.
Forgetting that the score function conceals the interval. DecisionMind uses the mid-point score. This is a canonical choice, but it does not report interval width; a narrow interval and a wide one can give the same score, and this loss of information must be stated in the report.
Domain violation. Every μU + νU ≤ 1 must hold; entering the calculation without checking this invalidates the method.
Confusing this card with IVIF-MARCOS. Both use the same four-number cell format (the support-rejection interval), but this card first aggregates with IIFWA into a single interval pair and only then descends to a score; a different aggregation-and-score order can produce a different number. Which engine was used must be stated in the report.
The governing principle is this:
In interval-valued intuitionistic fuzzy MARCOS, the support-rejection interval descends to a single mid-point score only at the very last step. The interval's width never returns at any step after that, and must be stated separately in the report.
Cases
The first case is DecisionMind's validation example: since no shared IV-MARCOS 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: Comparing three energy-storage system proposals (DecisionMind validation example)
Three energy-storage system proposals (A1, A2, A3) are assessed on three criteria (C1 and C2 are "higher is better," C3 is "lower is better") using interval support-rejection pairs. The weights are C1 = 0.40, C2 = 0.35, C3 = 0.25.
| Proposal | 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, builds the extended matrix together with the ideal and anti-ideal rows, aggregates each row with IIFWA and reduces it to a score, then computes the final utility degree as a ratio to the ideal and the anti-ideal.
| Proposal | Final utility degree | Rank |
|---|---|---|
| A2 | 0.8595 | 1 |
| A3 | 0.5673 | 2 |
| A1 | 0.4231 | 3 |
The result reads as follows. A2 holds the strongest support-rejection advantage on C1, and sits closest to the ideal on C3 (cost, once reversed); because this advantage on both criteria falls on the two most heavily weighted, A2 comes first by a clear margin.
The decision's hesitation: if C2's weight is raised from 0.35 to 0.70, with C1's weight lowered from 0.40 to 0.18 and C3's from 0.25 to 0.12, the ranking changes. The same calculation moves A3 to first place at 0.7812 and A2 to second at 0.7444. This shows that the lead between A2 and A3 is quite sensitive to C2's weight.
In the report: "With the given weights (0.40; 0.35; 0.25), A2 has the highest final utility degree (0.8595). When C2's weight is raised to 0.70, A3 moves ahead (0.7812); the ranking should therefore be treated as sensitive to C2's weight."
Source: DecisionMind's validation example for the interval-valued intuitionistic fuzzy MARCOS engine; since no shared IV-MARCOS worked table exists in the literature, it was built synthetically, and the expected results were derived from the manifest's formula chain (IIFWA aggregation, mid-point score, ideal/anti-ideal ratio, MARCOS utility function). The figures for the weight-change scenario were independently recomputed with the same engine by this card's author.
2. Care home: A foundation's choice of care-service provider
A care-home foundation will choose one of three service firms to outsource its daily care services (personal care, medication tracking, social activity). Three criteria apply: staff-experience score (higher is better), service-continuity assurance score (higher is better) and the hourly rate (lower is better). The foundation's board and an external auditor have each reported their support and reservations for every firm as an interval with a lower and an upper bound, reflecting the gap between their two views.
The method compares the three firms: it swaps support and rejection on the hourly rate, reduces every cell to a mid-point score and, in the extended matrix, ratios each firm to the ideal and the anti-ideal. Staff experience carries the highest weight (0.5). Suppose the firm with the most experienced staff also charges the highest hourly rate; it still comes first, because the weight on staff experience exceeds that on the rate.
The foundation's hesitation is this: this firm's hourly-rate interval is wide, for instance between 180 and 260 lira. If the budget is fixed, this width carries a worst-case cost risk above what was expected. The foundation should look not only at the final utility degree but also at the upper end of the rate interval.
In the report: "With the high weight given to staff experience, the most experienced firm comes out ahead. This firm's hourly-rate interval is wide; since the budget is fixed, the worst-case scenario should be separately assessed."
3. What Not to Do
Averaging the four bounds in the illustrative example down to a single support-rejection pair and then running intuitionistic fuzzy MARCOS (IF-MARCOS): this erases from the outset the "how little is known" information carried by the interval's width, and makes a separate calculation pointless. The second error is presenting the gap of 0.8595 against 0.5673 between A2 and A3 as a fixed lead without ever stating the weight sensitivity; A3 already moves ahead once C2's weight rises. The third error is comparing IV-MARCOS's result directly with IVIF-MARCOS's; although the two engines use the same cell format, they follow a different aggregation-and-score order, and their numbers are not interchangeable.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/iv-marcos
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
Stević, Ž., Pamučar, D., Puška, A., & Chatterjee, P. (2020). Sustainable supplier selection in healthcare industries using a new MCDM method: Measurement of Alternatives and Ranking according to Compromise Solution (MARCOS). Computers & Industrial Engineering, 140, 106231. DOI: 10.1016/j.cie.2019.106231
Moore, R. E. (1966). Interval Analysis. Prentice-Hall. (no DOI)