Extension card · Grey
Grey ARAS (Turskis and Zavadskas, 2010)
Grey ARAS is the form of ARAS that works with grey numbers when criterion values are known only by a lower and an upper bound. It computes the additive utility ratio over the bounds, reduces the result to a single midpoint, and converts it into a degree of utility.
Base method
ARAS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Grey →
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?
Four things change; the decision logic does not.
Cells. In crisp ARAS every cell is a single, strictly positive number. Here every cell is two numbers: a lower bound and an upper bound; no value within the bounds is considered more likely than another. Weights, too, may be given as a grey interval; when a crisp weight is supplied instead, DecisionMind embeds it as an interval with equal lower and upper bounds, adding no width. The method does not combine a group decision on its own.
Scale equalisation. Crisp ARAS first builds the optimal alternative, reverses cost criteria, then divides every column by its own sum. Here, for a cost criterion, every interval [lower; upper] becomes [1/upper; 1/lower] once reversed. This ensures the lower bound stays smaller than the upper bound even after reversal. The method then scales every column crosswise: a cell's lower bound is divided by the sum of all upper bounds in the column, and its upper bound is divided by the sum of all lower bounds in the column (including the optimal-alternative row). This crosswise division guarantees that the two bounds do not cross one another even once normalised. Ordinary division, that is, dividing both bounds by the same sum, gives no such guarantee.
Distance / score / aggregation. ARAS has no distance to a reference point; it takes a weighted sum directly, and that stays the case here, only the summation is carried out bound by bound over the intervals. The method multiplies each equalised interval by the criterion's (grey or crisp) weight, bound by bound (lower bound with lower bound, upper bound with upper bound). It then sums each row's intervals, including the optimal alternative, bound by bound across criteria. This produces a single interval "optimality score" for each row.
Result and defuzzification. The method reduces each row's interval sum to a single number by taking the average of its two bounds, whitening, grey system theory's own term for this. This is the defuzzification, and it happens only at this final step. The degree of utility K carries the same meaning as in crisp ARAS: the ratio of the real alternative's whitened score to the optimal alternative's whitened score.
DecisionMind fixes the midpoint whitening and the crosswise-ratio scale equalisation; intervals are never ranked directly at any stage, ranking is done only on the whitened K.
How to Read the Output
The degree of utility K carries the same meaning here. The best alternative is treated as 100, and the others receive a percentage relative to it; this percentage is valid only for this alternative set and these bounds. The difference is this: although K appears as a single number, a two-bounded uncertainty lies beneath it. This uncertainty disappears from view in the report because it is reduced to a single number at the whitening step. The K gap between two alternatives can be robust or fragile depending on the width of the input intervals; the same-sized K gap between two alternatives with wide, overlapping intervals is far less reliable than between two alternatives with narrow intervals.
Thus instead of writing:
"According to Grey ARAS, A2 is the best supplier"
the report should read:
"Relative to the optimal supplier derived from this supplier set, A2 has the highest degree of utility (K=0.885); its gap over A3 (0.879) is small relative to the width of the bounds, and the original paper's own table shows these two suppliers' ranking exactly reversed, so the advantage between A2 and A3 should be read as fragile, not decisive"
When to Prefer This over the Base Method
Use this method when only a lower and an upper bound are known about criterion values, and no most-likely value or distribution is available. Examples: new supplier bids assessed with little data, expert judgements that can state "at least this much, at most that much" but not "most likely," and indicators with a short track record.
If a known most-likely value exists within the bounds, dropping to a grey structure erases information that is already available; a fuzzy structure should be used instead in that case. Opening a measured criterion into a bound afterwards likewise manufactures uncertainty rather than modelling anything. DecisionMind requires a single data type: a measured criterion must be written as an interval with the lower bound equal to the upper bound. Crisp ARAS's exit condition applies here too: when no compromise is acceptable on one criterion, this extension is also fully compensatory and will not eliminate anything below a threshold.
Mistakes Specific to This Extension
Breaking the interval's order. In every cell the lower bound must be less than or equal to the upper bound, and all bounds must be positive (so that the cost criterion's reciprocal can be taken); if this condition is broken, the crosswise scaling produces a meaningless result.
Reading the whitened midpoint as a "most likely value." Whitening is only a computational step and carries no information about a most likely value within the bounds. The midpoint enters the calculation because of the defuzzification step, not because of the data.
Averaging the bounds first and then running crisp ARAS. In the supplier example below this path happens to give the same ranking (A2 still first), but this is not guaranteed; it erases from the outset the "how little is known" information the interval width carries, and the ranking can change in the next table.
Giving crisp weights and grey cells without saying so. The method embeds a crisp weight as a zero-width interval; this is legitimate, but it should be stated in the report.
The governing principle is this:
Grey ARAS is for taking a ratio against the optimal alternative while honestly preserving the fact that nothing is known beyond the bounds; any implementation that averages the bounds early, or ignores the difference between a narrow and a wide interval, conceals the method's one contribution.
Cases
The first case is the real supplier-selection example from Turskis and Zavadskas's (2010) founding paper. The second case is illustrative fiction.
1. Supply chain: Choosing among four suppliers (Turskis and Zavadskas, 2010)
Turskis and Zavadskas's (2010) paper in Informatica introduces Grey ARAS (ARAS-G) through an example in which a firm chooses among four suppliers. There are six criteria: delivery price (lower is better) and five higher-is-better criteria (indicators such as quality, delivery reliability, technical capacity, geographic proximity and relationship history); every criterion is given as a grey interval, since its bounds are uncertain, and the weights are also given as grey intervals.
| Supplier | x1 (price) | x2 | x3 | x4 | x5 | x6 |
|---|---|---|---|---|---|---|
| A1 | [0.591; 0.882] | [0.470; 0.600] | [0.663; 0.810] | [0.430; 0.750] | [0.650; 0.860] | [0.315; 0.615] |
| A2 | [0.544; 0.673] | [0.750; 0.960] | [0.512; 0.740] | [0.340; 0.550] | [0.660; 0.820] | [0.555; 0.975] |
| A3 | [0.541; 0.831] | [0.550; 0.780] | [0.659; 0.830] | [0.550; 0.860] | [0.830; 0.930] | [0.375; 0.690] |
| A4 | [0.706; 1.102] | [0.670; 0.900] | [0.709; 0.920] | [0.320; 0.670] | [0.720; 0.960] | [0.405; 0.735] |
| Direction | lower is better | higher is better | higher is better | higher is better | higher is better | higher is better |
| Weight | [0.195; 0.210] | [0.195; 0.195] | [0.054; 0.132] | [0.132; 0.195] | [0.171; 0.210] | [0.117; 0.195] |
The method first builds an optimal-supplier row carrying the best bounds on every criterion, reverses and cross-scales the price column, multiplies by the weights, sums the interval for each row (the four suppliers and the optimal supplier), and whitens the result into degrees of utility.
| Supplier | Degree of utility (K) | Rank |
|---|---|---|
| A2 | 0.885 | 1 |
| A3 | 0.879 | 2 |
| A4 | 0.827 | 3 |
| A1 | 0.772 | 4 |
The result reads as follows. A2 is the second cheapest on price and has the highest upper bounds on quality (x2) and on relationship history (x6); this combination carries it to first place. A3 is not the single best on any one criterion, but comes second with a balanced profile. A1 is the second most expensive supplier on price and, failing to stand out on the other criteria either, comes last.
The firm has a hesitation here. The paper's own Table 6 reports degrees of utility (A1=0.676; A2=0.796; A3=0.803; A4=0.720) that REVERSE the ranking of A2 and A3: the paper shows A3 first, whereas DecisionMind's calculation, independently re-run by this card's author, gives A2 first. In both readings the gap between A2 and A3 is small (0.007 in the paper, 0.006 here). This shows that the ranking between these two suppliers is fragile to rounding and to intermediate-step choices; being ranked first is not, on its own, sufficient grounds for a decision.
In the report: "With the given bounds, A2 has the highest degree of utility relative to the optimal supplier (K=0.885); its gap over A3 (0.879) is small, and the source paper's own table shows these two suppliers' ranking exactly reversed, so the final choice between A2 and A3 should not rest on the degree of utility alone, but should be tied to an additional criterion, such as the price offer being finalised."
Source: Turskis, Z., & Zavadskas, E. K. (2010), Informatica, 21(4), §4 Case Study, Tables 1-6. The degrees of utility have been independently recomputed by this card's author using DecisionMind's Grey ARAS engine; the paper's own Table 6 values are also given for comparison, and the A2-A3 rank difference between the two is reported as it stands, not concealed.
2. Agriculture: Trialling a new fertiliser programme in three regions
An agricultural cooperative must decide in which of three regions to first trial a new fertiliser programme as a pilot. Three criteria: expected yield increase, effect on soil acidity (lower is better; an increase in acidity is undesirable), and application cost (lower is better). Because this fertiliser programme has not previously been trialled in any of the regions, no criterion has a most-likely value; the cooperative's technical team can only say, for each region, "at worst this, at best that," with the bounds read from similar past trials and soil analysis.
The method compares the three regions: it builds an optimal (hypothetical best) region, reverses and cross-scales the cost and acidity columns, multiplies by the weights, whitens the result, and computes degrees of utility. Suppose the region with the widest yield-increase bound also has the widest cost uncertainty. It still comes out first, because the weight on yield increase exceeds that on cost. The region with the narrowest bounds, though its yield stays moderate, stands out as a highly reliable second option.
The cooperative also has a hesitation. The first region's wide bounds mean, in effect, that the data there is less reliable. The cooperative should assess the pilot choice not only by degree of utility, but also by which region's bounds are narrower, that is, more reliable. Once the actual yield is measured at the end of the season, the bounds will narrow and the calculation should be redone.
In the report: "With the weight given to yield increase, the first region has the highest degree of utility; however, because this region's bounds are the widest, its estimate is the least reliable, and the pilot decision should also take the width of the bounds into account."
3. What Not to Do
The first error is averaging the six intervals in the supplier example and running crisp ARAS. In this example it happens to give the same ranking (A2 still first), but this is not a general rule; the ranking can easily change in the next table. Moreover, averaging silently erases the "how little is known" information the interval width carries. The second error is reading A2's degree of utility of 0.885 as "definitively better than A3's 0.803 in the paper." The A2-A3 ranking is already reversed between the two sources, and the gap is small. The third error is cross-scaling the price column without first reversing it; this makes the most expensive supplier appear best.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/grey-aras
Turskis, Z., & Zavadskas, E. K. (2010). A novel method for multiple criteria analysis: Grey Additive Ratio Assessment (ARAS-G) method. Informatica, 21(4), 597–610. DOI: 10.15388/informatica.2010.307
Zavadskas, E. K., & Turskis, Z. (2010). A new additive ratio assessment (ARAS) method in multicriteria decision-making. Technological and Economic Development of Economy, 16(2), 159–172. DOI: 10.3846/tede.2010.10
Deng, J. L. (1982). Control problems of grey systems. Systems & Control Letters, 1(5), 288–294. DOI: 10.1016/S0167-6911(82)80025-X
Zavadskas, E. K., Kaklauskas, A., Turskis, Z., & Tamošaitienė, J. (2009). Multi-attribute decision-making model by applying grey numbers. Informatica, 20(2), 305–320. DOI: 10.15388/informatica.2009.252