Extension card · Fuzzy
Fermatean Fuzzy COPRAS
The form of COPRAS for situations where criterion assessment is given as a degree of support for a judgement and a degree of rejection of it, and these two degrees can be simultaneously high over a wider region than intuitionistic fuzzy data allow. It builds the benefit and cost totals from these support-rejection pairs.
Base method
COPRAS →
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 benefit-cost ratio logic does not.
Cells. In crisp COPRAS every cell is a single number. Here every cell is a pair: a degree of support for a judgement (μ) and a degree of rejection of it (ν). In intuitionistic fuzzy data the sum of these two cannot exceed 1; in Fermatean fuzzy data the limit is wider, the sum of their cubes cannot exceed 1 (μ³+ν³≤1). This allows pairs such as μ=0.8 and ν=0.5, whose sum exceeds 1 but whose cube sum stays below 1, to remain valid; a judgement can be both strongly supported and strongly rejected. Criterion weights are supplied from outside as crisp (single) numbers.
Scale equalisation. DecisionMind first reduces every pair to a single score: this score is μ³−ν³ and ranges from −1 to 1. Because it can be negative, 1 is added to shift it into the [0,2] range. The column-sum-based normalisation of crisp COPRAS is then applied to the scores obtained after this shift. This follows the same logic as the Chen-Tan score-difference shift in IF-COPRAS, except that the score function is extended to μ³−ν³.
Distance / score / combination. The normalised, weighted scores are split into a benefit total and a cost total exactly as in crisp COPRAS; the relative significance value (Q) is built with the same ratio and the same correction term that rewards low cost.
Result and defuzzification. Defuzzification happens right at the start: the support-rejection pair collapses to a single score (μ³−ν³) in the very first step, and the remainder of the calculation follows crisp COPRAS's own steps exactly. The output is a single utility degree, in the same form as crisp COPRAS's own output.
DecisionMind holds the μ³−ν³ score function and the +1 shift fixed for this family; no other score definition, nor a route that normalises support and rejection separately, is followed.
How to Read the Output
The output is a utility degree and ranking in the same form as crisp COPRAS, and it is read the same way. The difference is this: the score rests on the cube difference of support and rejection, and it also covers the "both high support and high rejection" situations that intuitionistic fuzzy data cannot express. An apparently identical μ³−ν³ difference can arise whether support and rejection are both high or both low; the utility degree does not distinguish between these two cases.
Thus instead of writing:
"Fermatean fuzzy COPRAS found this alternative more reliable"
the report should read:
"The utility degree rests only on the cube difference of support and rejection; A2 leads with 100.00, and this does not by itself mean 'more reliable' unless how strongly A2's support-rejection pair carries both endorsement and reservation is separately examined"
When to Prefer This over the Base Method
This extension is suitable when criterion assessment rests on a judgement, and the support and rejection degree of that judgement need to be expressed together, more strongly than intuitionistic fuzzy data allow. Example: an expert both strongly endorses a software vendor and holds a serious reservation, and these two sentiments do not fit within intuitionistic fuzzy data's μ+ν≤1 limit. If a criterion states only "how suitable" and carries no separate evidence of rejection, this wider limit adds nothing, and intuitionistic fuzzy or ordinary fuzzy data suffice. The exit condition of crisp COPRAS applies here too: where a criterion admits no compromise, this extension is also fully compensatory.
Mistakes Specific to This Extension
Entering a cell without checking the cube-sum limit (μ³+ν³≤1). A pair outside this limit is invalid; applying intuitionistic fuzzy data's μ+ν≤1 limit here is wrong, since Fermatean fuzzy data's own limit is wider.
Treating the score function (μ³−ν³) as the only correct choice and failing to state it in the report. Different score definitions can give a different ranking; the function used must be stated in the report.
Ignoring the shift constant (+1) and dividing scores directly by the column sum. If negative scores are divided without shifting, the column sum can turn out negative and the utility degrees become meaningless.
Marking criterion direction wrongly. If a cost criterion is marked "higher is better", high support on that criterion is included in the benefit total, and the result can reverse.
The governing principle is this:
Fermatean fuzzy COPRAS exists to carry the strong support-rejection combinations that intuitionistic fuzzy data cannot hold through to an optimal utility degree; any application that skips checking the cube-sum limit or omits the shift step corrupts this information.
Cases
The first case is DecisionMind's validation example: there is no single, page-traceable literature example commonly accepted for the Fermatean fuzzy COPRAS family, so the manifest uses a synthetic, hand-traceable table with three alternatives and three criteria. The second case is an illustrative construction.
1. Illustrative example: Three alternatives, three criteria (DecisionMind validation example)
Three alternatives are assessed on three criteria; the first two criteria are "higher is better", the third is "lower is better". Scores are given as support-rejection pairs.
| Alternative | C1 | C2 | C3 (cost) |
|---|---|---|---|
| A1 | support 0.70 / rejection 0.40 | support 0.50 / rejection 0.50 | support 0.60 / rejection 0.50 |
| A2 | support 0.80 / rejection 0.30 | support 0.60 / rejection 0.40 | support 0.40 / rejection 0.60 |
| A3 | support 0.60 / rejection 0.50 | support 0.70 / rejection 0.40 | support 0.50 / rejection 0.50 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method reduces every pair to a μ³−ν³ score, shifts it by adding 1, normalises against the column sum, and multiplies by the weight. It accumulates the C1 and C2 values in the benefit total and the C3 value in the cost total, computes the relative significance value (Q), divides by the highest value, and converts to a percentage.
| Alternative | Utility degree | Rank |
|---|---|---|
| A2 | 100.00 | 1 |
| A3 | 88.44 | 2 |
| A1 | 84.16 | 3 |
The result reads as follows. A2 holds the highest support (0.80) and lowest rejection (0.30) on the most heavily weighted criterion, C1, and it also sits in the most favourable position on C3 (cost) once support and rejection have been reversed. These two advantages carry A2 to first place despite its mid-range performance on C2. A1 finishes last because it is weaker than A2 on C1 and is the most expensive alternative on C3.
The decision's hesitation is this: if the weight is concentrated on C2 and redistributed as C1=0.10, C2=0.68, C3=0.22, the utility values (via Q) come out to 0.2965 for A1, 0.3506 for A2 and 0.3529 for A3 (computed by independently rerunning DecisionMind's engine in Python). A3 overtakes A2 to move into first place; the gap between them is only 0.0022, meaning the ranking between these two alternatives is close to a tie under this weight distribution.
In the report: "With the given weights (0.40; 0.35; 0.25), A2 has the highest utility degree (100.00). When the weight is shifted noticeably towards C2 (0.10; 0.68; 0.22), A3 and A2 nearly equalise and the ranking can change; the weight distribution should therefore be separately justified in the report."
Source: The validation example for DecisionMind's Fermatean Fuzzy COPRAS engine; built synthetically because no shared FF-COPRAS application table exists in the literature, with expected results derived from the manifest's own formula chain (μ³−ν³ score, +1 shift, column-sum normalisation, benefit/cost split, Q formula). The figures for the weight-change scenario have been independently recomputed by this card's author using the same engine.
2. Software procurement: An organisation's choice of cloud infrastructure provider
An organisation will choose a cloud infrastructure provider for a critical workload from among three candidates. There are three criteria: history of service outages (lower is better), technical support response speed (higher is better), and data migration cost (lower is better). The IT team has reported, separately for each provider, how much it trusts and how much reservation it holds, as a support-rejection pair; for one provider the team holds both high trust and a serious reservation stemming from a past incident, and the sum of these two sentiments exceeds 1.
The method compares the three providers: it reverses support and rejection on the outage-history and cost criteria, shifts and normalises the scores, and multiplies and sums with the weights. The highest weight has been given to technical support response speed. Suppose the fastest-responding provider is also the one carrying the highest reservation; it still comes first, because the weight on response speed exceeds that of the criteria carrying the reservation.
The team's hesitation is this: the source of the reservation about this provider is a single outage incident from two years ago. If the contract is extended without confirming this reservation through current references, the risk is being disregarded; the team must either confirm the reservation from a second source or lower the weight on response speed and review the result again.
In the report: "With the high weight given to technical support response speed, the fastest provider comes out ahead. As the reservation about this provider rests on a single past incident, confirming it through current references before the contract is recommended."
3. What Not to Do
In the illustrative table, applying crisp COPRAS logic to C3 by taking 1 divided by support instead of swapping support and rejection: this breaks the cube-sum limit (μ³+ν³≤1) and produces an invalid pair. The second error is reporting A2's utility degree of 100.00 as "one hundred per cent reliable"; this value only means A2 is the best among these three alternatives. The third error is skipping the shift step (+1) and dividing negative scores directly by the column sum; in that case the signs of the shares can become confused and the utility degrees become meaningless.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/ff-copras
Senapati, T., & Yager, R. R. (2020). Fermatean fuzzy sets. Journal of Ambient Intelligence and Humanized Computing, 11, 663–674. DOI: 10.1007/s12652-019-01377-0
Senapati, T., & Yager, R. R. (2019). Fermatean fuzzy weighted averaging/geometric operators and its application in multi-criteria decision-making methods. Engineering Applications of Artificial Intelligence, 85, 112–121. DOI: 10.1016/j.engappai.2019.05.012
Zavadskas, E. K., & Kaklauskas, A. (1996). Determination of an efficient contractor by using the new method of multicriteria assessment. In International Symposium for the Organization and Management of Construction: Shaping Theory and Practice, Vol. 2, 94–104. (no DOI)
Atanassov, K. T. (1986). Intuitionistic fuzzy sets. Fuzzy Sets and Systems, 20(1), 87–96. DOI: 10.1016/S0165-0114(86)80034-3