Extension card · Classical
Interval Number Grey Relational Analysis (Olson and Wu, 2008)
This is the form of GRA for situations where criterion values are given not as a single number but as a known, exact lower and upper bound. It carries the bounds through without reducing them to a single number at any step; it computes the reference and the distance from the two bounds together.
Base method
GRA →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Classical →
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 grey relational coefficient and the ranking logic do not.
Cells. In crisp GRA every cell is a single number. Here every cell is a lower and an upper bound: [a⁻, a⁺]. This is not uncertainty or a lack of information; it is known with certainty that the value lies between these two bounds. Weights can be crisp or interval numbers; DecisionMind supports a scalar (single-number) weight in this extension.
An interval must not be confused with a grey number. The two share the same shape, two bounds. The difference lies in context: the bound in Grey GRA is a "partial information" object that may narrow in future as more becomes known, and it is reduced to its midpoint (whitenisation) before entering the calculation. The bound here states that the value is exactly within that interval and is never reduced to a midpoint at any step; both bounds are carried separately right to the end.
Scale equalisation. Crisp GRA places every column into the 0–1 range according to its own smallest and largest value (min–max normalisation). This extension does not use min–max. First, direction is corrected on a cost criterion by reversing the sign of both bounds ([a⁻,a⁺] → [−a⁺,−a⁻]). Each column is then divided by the largest absolute value among that column's two bounds across all cells (the column's vector norm). This does not squeeze the column into 0–1; it merely scales its magnitude against the column's own extreme point.
The reference is built from both bounds. In crisp GRA the reference sequence is a fixed single normalised value, (1; 1; …; 1). Here the reference is an envelope built separately from the largest of each column's lower bounds and the largest of its upper bounds: U₀ = ([max a⁻], [max a⁺]). This is a reference that may not match any real alternative exactly, criterion by criterion assembling the best of each; the logic resembles the optimal-alternative envelope on the IV-ARAS card.
Distance. In crisp GRA, distance is the absolute difference of a single number. Here distance is whichever is larger of the absolute difference of the lower bounds and the absolute difference of the upper bounds (the worse of the two bounds is taken as the basis). This is not a midpoint difference; both bounds are compared separately and the larger deviation is chosen.
DecisionMind fixes, in this extension, vector-norm scaling, the two-bound envelope reference and the two-bound distance rule; the grey relational coefficient and degree are then computed with the same formula as crisp GRA, using the discrimination coefficient ρ.
How to Read the Output
The grey relational degree shows, as in crisp GRA, an alternative's relative closeness to the reference within this particular analysis; it cannot be compared with a different analysis.
The difference is here. The degree is computed not from the midpoint of the bounds but from the bounds themselves; however wide an alternative's interval is, it is neither penalised nor rewarded separately for that width. Width only affects the degree indirectly, through how far the lower and upper bounds deviate from the reference in the distance calculation. This differs from Grey GRA, which works from the midpoint and never sees the width at all; here width enters the calculation implicitly, because the two bounds are carried separately.
Thus instead of writing:
"According to interval-number GRA, A1 is more reliable because its interval is narrow"
the report should read:
"A1's grey relational degree of 0.714 is higher than A2's 0.667; this difference comes from A1's lower and upper bounds sitting closer to the reference on both criteria, not from the width of the interval itself"
When to Prefer This over the Base Method
Use this extension when a criterion value is known only through a lower and an upper bound, and these bounds are known to be exact, that is, not expected to narrow with future information. Examples: a minimum-maximum delivery time guaranteed in a contract, a device's operating range as stated by the manufacturer, an approved lower and upper limit for a budget item. Where the bound sits in a "partial information" context, that is, where it is expected to narrow to a more precise point in future, Grey GRA is the more suitable framework.
If the value is measured as a single number, remain with base GRA. If the table is mixed, DecisionMind requires a single data type; a crisp value is written as a zero-width interval in the form [a, a]. Base GRA's exit condition applies here too: if a criterion carries a threshold on which no compromise is ever acceptable, GRA's additive structure does not preserve it.
Mistakes Specific to This Extension
Allowing the lower bound to exceed the upper bound. Every interval must satisfy a⁻ ≤ a⁺; feeding this into the calculation without checking renders the scaling and reference steps meaningless.
Forgetting the cost conversion. If the sign reversal ([a⁻,a⁺] → [−a⁺,−a⁻]) is not applied on a "lower is better" criterion, the ranking silently reverses; this is the most common error point the manifest itself names.
Mistaking this for triangular fuzzy GRA. The input here is not a triangular fuzzy number (lower, most likely, upper) but a two-ended interval; there is no most-likely point. The arithmetic, too, runs not on the triangular fuzzy extension principle but on Olson and Wu's interval-product rules. Confusing the two produces a different normalised matrix.
Reducing to a midpoint and treating it as Grey GRA. This treats the interval as "partial information" and adds a whitenisation step that DecisionMind never performs in this extension; the result approaches Grey GRA's result but departs from this extension's own definition.
Pushing the discrimination coefficient (ρ) outside its bounds. ρ must lie in (0,1]; ρ far above 1 weakens discrimination, while ρ very close to zero makes every alternative other than the closest one resemble each other.
The governing principle is this:
In interval-number GRA both bounds are carried separately right to the end and are never reduced to a midpoint at any step. Skipping the cost conversion, confusing this with triangular fuzzy GRA, or reducing to a midpoint early and treating it as Grey GRA all break the method's principle of preserving the bounds as exact information.
Cases
The first case is DecisionMind's validation example. Olson and Wu's (2008) source chapter gives no numerical example for the deterministic core of interval-number GRA; the chapter instead moves on to Monte Carlo simulation. Case 1 is therefore a small example, faithful to the manifest's formula chain (Eq. 1-9), verified by hand calculation with fractional numbers. The second case is an illustrative construction.
1. Illustrative example: Interval assessment of two suppliers on two criteria
A firm is comparing two suppliers (A1, A2) on two criteria; both are "higher is better" and equally weighted (0.5). The criterion values are the guaranteed minimum-maximum performance intervals from past contracts.
| Supplier | C1 (higher is better) | C2 (higher is better) |
|---|---|---|
| A1 | [1; 2] | [3; 4] |
| A2 | [2; 3] | [1; 2] |
| Weight | 0.5 | 0.5 |
Since both criteria are "higher is better," no sign reversal is applied. The method divides every column by its own vector norm (the column's largest absolute bound value), multiplies by the weight, builds the reference envelope (U₀) from the largest of the two bounds column by column, measures distance based on the worse of the two bounds, and converts to a grey relational degree with ρ = 0.5.
| Supplier | Grey relational degree | Rank |
|---|---|---|
| A1 | 5/7 ≈ 0.714 | 1 |
| A2 | 2/3 ≈ 0.667 | 2 |
The result reads as follows. A1 is the reference itself on C2 ([3;4], the column's largest bounds); trailing A2 ([2;3]) on C1 does not outweigh this lead, because the two criteria are equally weighted and A1's advantage on C2 offsets its shortfall on C1.
The firm's hesitation lies in the weights. If C1's weight is raised from 0.50 to 0.60, A1 and A2 become exactly equal (both 2/3); raised to 0.65, A2 (0.691) overtakes A1 (0.667). In other words, A1's lead depends on the two criteria being weighted equally or close to favouring C2; once C1 is weighted markedly more, first place passes to A2.
In the report: "With equal weights, A1 is the supplier closest to the reference envelope (grey relational degree 5/7). The two suppliers become equal once C1's weight is raised to 0.60, and A2 moves ahead once it is raised to 0.65; the relative importance of the two criteria must therefore be separately justified in the report."
Source: DecisionMind's validation example for the interval-number GRA engine; since Olson and Wu's (2008) source chapter gives no numerical application for the deterministic core, this 2×2 positive-interval example was built in Python with fractional numbers, staying faithful to the manifest's formula chain (Eq. 1-9), and matches exactly the expected result in DecisionMind's manifest (r₁=5/7, r₂=2/3). The weight sensitivity was independently computed by this card's author using the same method.
2. Logistics: A warehouse operator's choice of forklift rental quotation
A warehouse operator is comparing three forklift rental quotations on two criteria for a seasonal capacity increase: daily lifting capacity (higher is better) and daily rental fee (lower is better). Each quotation is given with the supplier's contractually guaranteed minimum-maximum values, that is, an exact interval; these bounds are not estimates but contract terms.
The method reverses the sign on the fee criterion, divides the columns by their vector norm, builds the reference envelope, measures distance based on the worse of the two bounds, and computes the grey relational degrees. Suppose the quotation with the highest capacity interval also has the widest fee interval, that is, the most uncertain pricing, and yet still comes first, thanks to the higher weight on capacity.
The operator's hesitation is this: if this quotation's fee interval is wide, and its upper bound (the fee payable in the worst case) is close to the other quotations' upper bounds, the operator should look not only at the grey relational degree but also at this upper bound; interval width enters the degree calculation only indirectly and should be stated separately in the report.
In the report: "The quotation with the highest lifting-capacity interval comes first in the grey relational degree; this quotation's fee interval is wider than the others', and the worst-case (upper-bound) scenario should be separately assessed."
3. What Not to Do
Had C1 been marked "lower is better" in the illustrative example, continuing the calculation without applying the sign reversal is the first error; in that case the reference envelope is built around the worst-performing supplier and the ranking reverses. The second error is reading an interval such as [1;2] as a triangular fuzzy number (1; 1.5; 2) and processing it with TFN-based fuzzy GRA formulas; there is no "most likely" point here, and the arithmetic runs on interval-product rules. The third error is ignoring the point where a weight change (C1=0.60) makes A1 and A2 exactly equal and reporting that "A1 is clearly first"; the ranking is sensitive to the choice of weight and this must not be concealed from the report.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/interval-gra
Olson, D. L., & Wu, D. (2008). Simulation support to grey-related analysis: data mining simulation. In C. Kahraman (Ed.), Fuzzy Multi-Criteria Decision Making, Springer Optimization and Its Applications, vol. 16 (Ch. 11, pp. 281–299). Springer. DOI: 10.1007/978-0-387-76813-7_11
Deng, J. L. (1989). Introduction to grey system theory. The Journal of Grey System, 1(1), 1–24. (no DOI)
Moore, R. E. (1966). Interval Analysis. Prentice-Hall. (no DOI)
Olson, D. L., & Wu, D. (2006). Simulation of fuzzy multiattribute models for grey relationships. European Journal of Operational Research, 175(1), 111–120. DOI: 10.1016/j.ejor.2005.05.002
Kuo, Y., Yang, T., & Huang, G. W. (2008). The use of grey relational analysis in solving multiple attribute decision-making problems. Computers & Industrial Engineering, 55(1), 80–93. DOI: 10.1016/j.cie.2007.12.002