Extension card · Z-Number
Z-fuzzy CRADIS (Puška et al., 2022)
This is the form of CRADIS for situations where a criterion value is carried as a triangular fuzzy number together with a separate Z-number component stating how far that value can be trusted, the two together reduced to a single fuzzy number. The output remains a compromise score.
Base method
CRADIS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Z-Number →
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 CRADIS logic of keeping closeness to the ideal and distance from the anti-ideal as two separate ratios and then averaging them does not.
Cells and the prior conversion. In crisp CRADIS every cell is a single number. In this extension a cell is, conceptually, a Z-pair: the value an expert gives (A, converted from a verbal scale into a triangular fuzzy number) and the confidence placed in that value (B, converted from a separate verbal scale into a triangular fuzzy number). Puška and colleagues' method first reduces every expert's every Z-pair to a single triangular fuzzy number through Kang and colleagues' (2012) conversion; in this reduction, A's three corners are scaled by the square root of a coefficient drawn from B's centroid. Where more than one expert is involved, the triangles reduced in this way are combined by arithmetic mean into a single collective fuzzy decision matrix.
The step DecisionMind runs in this extension. A lasting and important limitation must be reported here: the engine that computes this extension for DecisionMind does not itself carry out the reduction from a Z-pair to a triangular fuzzy number described above; it expects a decision matrix that is already reduced, that is, made up of ready-made triangular fuzzy numbers. This card's author verified it by running the engine: when a cell is given six figures (a three-figure value triangle plus a three-figure reliability triangle), the engine reads only the first three figures and disregards the remaining three (reliability) entirely; changing the reliability between (0.1; 0.1; 0.1) and (0.9; 0.9; 0.9) leaves the result identical to the decimal place. This belongs to the same family as the "reliability component is not read" situation reported on the Z-number data-type card and on DecisionMind's Z-TOPSIS, Z-VIKOR, Z-EDAS, Z-COPRAS and Z-WASPAS cards. The reason here, however, differs. On those cards reliability is read and then cancels out mathematically. Here reliability is never read by the engine at all; the step converting a Z-pair into a fuzzy number has not been implemented in the engine's code.
Normalisation, weighting, the ideal/anti-ideal, distance, defuzzification and the compromise score. Once a ready triangular fuzzy decision matrix is in hand, all of these steps are the fuzzy form of crisp CRADIS and run according to Puška and colleagues' (2022) definition: direction-sensitive normalisation (ratioing to the largest value in a benefit column, to the smallest in a cost column), weighted triangles, a SINGLE ideal and a SINGLE anti-ideal triangle built over the whole matrix, the d+ and d- deviations found by triangular subtraction, their sums, defuzzification with the GMIR centroid (1,4,1)/6, K+ and K- against the best ratio, and the compromise score Q as their average.
DecisionMind fixes, in this extension, the GMIR defuzzification and the single-global-ideal/anti-ideal logic. Weights are taken from outside, as crisp numbers; the method does not generate weights.
How to Read the Output
The compromise score Q is read as in crisp CRADIS (see the CRADIS card): it is not a percentage, and it is not compared with another analysis.
The difference lies here. The purpose of the Z-number data structure is to carry confidence in the source into the decision. But the engine that computes this extension for DecisionMind never reads reliability; the calculation runs directly on the triangular fuzzy values entered. For that reason the report must not state that "reliability has been taken into account."
Thus instead of writing:
"Because Z-fuzzy CRADIS has been used, the supplier's reliability history is reflected in the result"
the report should read:
"Criterion values have been entered as triangular fuzzy numbers; the current engine does not read or take into account any reliability component accompanying these values. If a difference in reliability matters, it must be reflected, at the data-collection stage, in the value itself (A), not in a separate reliability field"
When to Prefer This over the Base Method
In formal terms, if criterion values come from a judgement or an estimate, and reducing them to a single number would manufacture an artificial precision, this extension, in effect functioning as a fuzzy CRADIS, is the right choice. But if the decision-maker expects that "a difference in the source's reliability will affect the ranking," this expectation is not met by the current engine; this limitation must be stated before data collection. Fuzzifying an already measured value manufactures uncertainty rather than modelling it; crisp CRADIS should be kept instead.
Crisp CRADIS's exit condition also applies here: if no compromise is acceptable on a criterion, sub-threshold alternatives must first be screened out, and only the remainder ranked with this extension.
Mistakes Specific to This Extension
Assuming that reliability (B) will change the ranking. The current engine does not read B; two identical A values with different reliability are, to the engine, exactly the same. This is not a software bug but a limit of the engine's present scope, and it must be stated explicitly in the report.
Confusing GMIR defuzzification with a simple centroid. Puška's formula uses GMIR weights of the form (l+4m+u)/6; replacing this with the simple centroid (l+m+u)/3 produces a different number.
Reversing s0+ and s0-. s0+ is the smallest s+ value (the alternative departing least from the ideal); s0- is the largest s- value (the alternative departing most from the anti-ideal). Reversing these two definitions inverts the ranking.
Adding a "reliability" field to a measured value out of caution. Adding a reliability field to an actual measurement is both unnecessary and, in any case, not read by the engine; a measured value should stay as a triangle whose three components are identical.
The governing principle is this:
Z-fuzzy CRADIS is designed to record the criterion value and the confidence placed in it separately. But DecisionMind's present engine never reads this confidence component; the calculation runs only on the triangular fuzzy value, and this limit must be stated to the decision-maker before data collection.
Cases
The first case is anchored to Puška and colleagues' (2022) agricultural green-supplier-selection case study. The second case is an illustrative construction.
1. Illustrative example (anchored to the source): Green supplier selection among six suppliers (Puška et al., 2022)
An agricultural cooperative has assessed six suppliers (A1-A6) on ten sustainability criteria; all the criteria run in the "higher is better" direction. The experts' Z-pair assessments are given as already reduced to triangular fuzzy numbers, and averaged across three experts, in the article's own table; the weights come from a separate weighting method (Z-fuzzy LMAW). Below are shown eight of the table's columns (two columns not reported in the article) together with the weights.
| Supplier | C1 | C2 | C4 | C6 | C7 |
|---|---|---|---|---|---|
| A1 | 2.20; 2.61; 3.02 | 1.57; 1.94; 2.32 | 2.45; 2.87; 3.29 | 3.18; 3.61; 3.90 | 2.23; 2.60; 2.98 |
| A2 | 2.96; 3.37; 3.78 | 3.18; 3.61; 4.04 | 2.75; 3.14; 3.37 | 3.46; 3.90; 4.19 | 3.50; 3.93; 4.23 |
| A3 | 2.90; 3.31; 3.57 | 2.52; 2.84; 3.07 | 2.68; 3.02; 3.17 | 3.18; 3.60; 3.88 | 3.18; 3.54; 3.62 |
| A4 | 1.65; 2.06; 2.47 | 1.63; 2.00; 2.38 | 2.22; 2.66; 3.11 | 1.48; 1.89; 2.29 | 1.64; 2.01; 2.37 |
| A5 | 2.00; 2.36; 2.71 | 2.44; 2.85; 3.25 | 2.99; 3.41; 3.84 | 2.70; 3.11; 3.51 | 2.29; 2.68; 3.07 |
| A6 | 2.45; 2.89; 3.32 | 1.57; 1.92; 2.26 | 1.78; 2.16; 2.54 | 2.23; 2.68; 3.13 | 1.52; 1.89; 2.25 |
| Weight | 0.099 | 0.099 | 0.119 | 0.152 | 0.156 |
(The table also has criteria C3, C5, C8, C9 and C10; the remaining two columns, C8 and C9, are not reported in the article's own table either, and are left blank in this example too. This shows that the example is not complete, reflecting the source's own incomplete reporting.)
The method normalises every column in the benefit direction, weights it, finds a single global ideal and anti-ideal triangle, sums the deviations, defuzzifies with GMIR, and calculates the compromise score.
| Supplier | Compromise Score (Q) | Rank |
|---|---|---|
| A2 | 1.000 | 1 |
| A3 | 0.689 | 2 |
| A5 | 0.443 | 3 |
| A1 | 0.394 | 4 |
| A6 | 0.143 | 5 |
| A4 | 0.082 | 6 |
The result reads as follows: A2 is ranked first both because it holds the highest values on most of the eight criteria and because it departs least from the single global ideal; A4 is last because it holds the lowest values on most criteria. The ranking coincides exactly with the order Puška and colleagues (2022) published (A2 > A3 > A5 > A1 > A6 > A4).
An important disclosure is needed here: the Q values above were obtained by DecisionMind's engine independently recomputing this table today. The engine's own internal audit gate reports that these values do not coincide exactly with the figures the article publishes (A2=0.920; A3=0.889; A5=0.727; A1=0.685; A6=0.480; A4=0.462); the ranking matches the article, the magnitude of the compromise scores does not (detail in the approval notes).
The cooperative's hesitation: because no cell in this table has its reliability component read by the engine, the answer to "did the three experts' relative experience get reflected in the ranking" is no. The three experts' assessments have already been combined by an equally weighted arithmetic mean; one expert being more experienced than the others carries no additional weight in this average.
In the report: "The ranking (A2 > A3 > A5 > A1 > A6 > A4) coincides with the order Puška and colleagues (2022) published. The magnitude of the compromise scores differs between DecisionMind's current engine output and the figures the article publishes; furthermore, the three experts' assessments have been averaged with equal weight, and the difference in their experience has not been separately taken into account as a reliability component."
Source: Puška, Božanić, Nedeljković and Janošević (2022), Axioms 11:427, Table 6 (weights) and Tables 8-9 (matrix and ranking). The ranking coincides with the article; the magnitude of the compromise scores does not, and since columns C8-C9 are not reported in the article, they are also missing from this example.
2. Retail: A chain's choice of warehouse supplier
A retail chain will choose a regional distribution partner among three logistics warehouse operators. The criteria are delivery-time reliability (past performance rate), storage capacity, contract cost and the maturity of the digital tracking system; all but cost are "higher is better", cost is "lower is better". The procurement team enters each criterion as a triangular fuzzy number derived from the verbal scores of three regional managers. The team knows that, on the delivery-time-reliability criterion, one operator's score rests on only the last three months of data while the other's rests on a five-year history, and expects this difference to be reflected in the calculation.
The method normalises the three operators' fuzzy values, weights them, sums the distances to the single global ideal and anti-ideal, and calculates the compromise score. Suppose the result places first the operator scoring highest on delivery-time reliability, even though that score rests on only three months of data.
The team's hesitation is this: this advantage has been calculated in the current engine with no distinction made for reliability at all; even though the operator resting on five years of history scores lower, the engine has treated the two sources as equally reliable. If the team wants the reliability difference genuinely to affect the decision, it must reflect this, not in a separate reliability field, but directly, as a margin of caution built into the three-month operator's own score.
In the report: "The operator scoring highest on delivery-time reliability is ranked first; however, this score rests on only three months of data, and the current calculation makes no reliability distinction based on the length of the data history. This difference should be assessed separately before the decision."
3. What Not to Do
In the illustrative example, writing a supplier's reliability field as (0.9; 0.9; 0.9) instead of (0.1; 0.1; 0.1) and expecting "this supplier's score will now rise": the score does not change at all, because the engine never reads this field. The second error is reporting the compromise scores the article publishes (such as A2=0.920) as though they were the engine's current output; the ranking coincides, but the magnitude of the scores does not. The third error is confusing GMIR defuzzification with the simple centroid, which produces a different number.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/zf-cradis
Puška, A., Božanić, D., Nedeljković, M., & Janošević, M. (2022). Green supplier selection in an uncertain environment in agriculture using a hybrid MCDM model: Z-Numbers–Fuzzy LMAW–Fuzzy CRADIS model. Axioms, 11(9), 427. DOI: 10.3390/axioms11090427
Puška, A., Stević, Ž., & Pamučar, D. (2021). Evaluation and selection of healthcare waste incinerators using extended sustainability criteria and multi-criteria analysis methods. Environment, Development and Sustainability, 24(9), 11195–11225. DOI: 10.1007/s10668-021-01902-2
Kang, B., Wei, D., Li, Y., & Deng, Y. (2012). A method of converting Z-number to classical fuzzy number. Journal of Information and Computational Science, 9(3), 703–709. (no DOI)
Zadeh, L. A. (2011). A note on Z-numbers. Information Sciences, 181(14), 2923–2932. DOI: 10.1016/j.ins.2011.02.022