Methods · Ranking
Grey Projection
Grey Projection compares criterion values given as intervals (a lower and an upper bound rather than a single exact number) by projecting them onto the best and worst reference directions; the alternative with the larger projection onto the ideal and the smaller projection onto the worst comes out on top.
Base method's data type: Grey
What Is the Method?
Grey Projection is a method for ranking alternatives when the data you hold is not a single exact number but a lower bound and an upper bound (a grey number). It carries Grey Systems Theory's (Deng, 1982) principle that "a decision can still be made with little data and incomplete information" into multi-criteria ranking. The method is an extension of Grey Relational Analysis (GRA); in place of GRA's distance measurement, it uses projection onto ideal and anti-ideal points. The output is a closeness coefficient for every alternative and the rank that coefficient produces; the larger the coefficient, the closer the alternative sits to the ideal.
The Philosophy Behind It
The starting point of Grey Systems Theory is that a grey region lies between the fully known and the entirely unknown, and that many real decisions are made within this grey region. Consider a weather forecast. Saying "18 to 22 degrees tomorrow" rather than "20 degrees tomorrow" honestly admits incomplete information while still allowing a decision to be made. Grey Projection accepts criterion values as such intervals in the same way, and compares the direction each alternative forms from these intervals against the best and worst reference directions. Using projection in place of TOPSIS's distance measurement produces a comparison that takes direction into account as well as distance alone; of two alternatives equally distant from the ideal, the one more closely aligned with the ideal direction comes out ahead.
How It Works
The method proceeds through four steps.
First, defuzzification and scale equalisation. Each cell's grey number is first defuzzified: the lower and upper bounds are averaged down to a single number. Every column is then normalised against its own magnitude: benefit criteria are scaled against the largest upper bound in the column, cost criteria against the smallest lower bound. This step makes criteria in different units comparable.
Second and third steps, finding the ideal and anti-ideal directions and computing the projections. In the normalised table, the best value on each criterion builds the ideal direction, and the worst value builds the anti-ideal direction. The method projects each alternative's weighted, normalised vector onto both the ideal direction and the anti-ideal direction; this projection is a number measuring how closely the alternative aligns with that direction.
Fourth, computing the closeness coefficient and ranking. Grey Projection divides the projection onto the ideal by the sum of the projections onto the ideal and the anti-ideal. For an alternative strongly aligned with the ideal, this ratio approaches 1. Alternatives are ranked by this coefficient from the highest to the lowest.
The formulas behind each step, the intermediate tables and the citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The closeness coefficient shows how closely an alternative, given this interval data, aligns with the ideal direction; it says nothing more than that. A coefficient around 0.50 does not mean "an average decision," but a roughly equal projection onto the ideal and anti-ideal directions. It cannot be compared with a coefficient from a different analysis, because the ideal and anti-ideal directions are built afresh in every analysis from that analysis's own data.
In methods that use grey data, the gap between coefficients can come out smaller than in methods using crisp data, because the defuzzification step erases some of the information about the width of the interval. A small gap between coefficients points to a ranking sensitive to the width of the intervals; the report should show this sensitivity.
Thus instead of writing:
"Grey Projection found the best alternative"
the report should read:
"With this interval data and these weights, the alternative most closely aligned with the ideal direction is this one; if the gap between the coefficients is small, the width of the intervals should be separately reported"
Data Type and Inputs
Grey Projection works with grey numbers: every cell consists of a lower bound and an upper bound, not a single exact number. As of this writing, DecisionMind holds no extension alongside the base method; if your data is crisp, exact methods such as GRA or TOPSIS can be used directly without converting it into grey numbers.
You need: a lower bound and an upper bound for every criterion of every alternative (the lower bound must not exceed the upper bound), a direction for every criterion, and criterion weights that sum to 1. A minimum of two alternatives and two criteria is required; the recommended size is two to twenty-five alternatives and three to ten criteria.
When to Use It, When Not To
Grey Projection is a sound choice if your data is expressed as an interval because of incomplete measurement, a short observation period or expert estimation, and you do not want to ignore this uncertainty. Its typical territory is engineering and planning problems decided with a small sample or incomplete information.
It should not be used where your data is already fully known as single exact numbers; converting it into grey numbers adds needless uncertainty. If your intervals are very wide, the defuzzification step can oversimplify the information; in that case the interval itself should be shown separately in the report.
Data given as intervals, information is incomplete → Grey Projection
Data is a single exact number → exact ranking methods such as GRA, TOPSIS
Uncertainty comes from expert language (low, medium, high) → fuzzy or intuitionistic methods
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective), Entropy, CRITIC (objective)
Strengths
The method's greatest strength is that it accepts incomplete or uncertain data as an interval rather than forcing it into a single number. It can work with a small number of observations, drawing on Grey Systems Theory's search for solutions to small-sample problems. Its use of projection, which accounts for alignment with the ideal direction as well as distance alone, offers an alternative to TOPSIS's distance-based approach.
Weaknesses
Its limitations stem from this same flexibility. First, the defuzzification step partly loses information about the width of the interval; a very wide interval and a narrow one sharing the same average become indistinguishable. Second, there is no single, universally accepted founding article under the name "grey projection"; the method is one of several projection-based adaptations of Grey Relational Analysis and can vary slightly from application to application. Third, it carries the same limitations as GRA: criteria are treated as independent, and the quality of the weights lies outside the method itself.
Common Mistakes
The most common mistake is entering a lower bound greater than the upper bound; this breaks the definition of the interval and invalidates the calculation. A second mistake is reading the closeness coefficient as a percentage or a probability; the coefficient only shows relative alignment with the ideal direction. A third is setting the interval very wide and then interpreting the defuzzified average as if it were an exact number; the width of the interval should be separately stated in the report. A fourth is converting crisp data into grey numbers without justification, needlessly complicating the method.
The governing principle is this:
A Grey Projection result depends on the width of the intervals you supplied and on the weights; if the intervals are very wide, a single defuzzified coefficient conceals that width, and the report must show it separately.
Cases
Each case opens with a decision table, describes in words what the method does to it, and shows how to read the result.
1. Supply Chain: comparing suppliers with incomplete data (illustrative example)
A procurement team must compare three suppliers using limited observation data. Three criteria apply: delivery performance (higher is better), quality score (higher is better) and price index (lower is better); the data is held as intervals, the lowest and highest values observed across past orders. The team set the weights so that delivery performance carries the most (0.40), quality next (0.35), and price the least (0.25).
| Supplier | Delivery (C1) | Quality (C2) | Price (C3) |
|---|---|---|---|
| S1 | 3.0-4.0 | 5.0-6.0 | 7.0-8.0 |
| S2 | 7.0-8.0 | 8.0-9.0 | 3.0-4.0 |
| S3 | 5.0-6.0 | 6.0-7.0 | 4.0-5.0 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method defuzzifies and normalises every interval, builds the ideal and anti-ideal directions, and then computes each supplier's projection onto both directions.
| Supplier | Closeness Coefficient | Rank |
|---|---|---|
| S2 | 0.5034 | 1 |
| S3 | 0.5030 | 2 |
| S1 | 0.4966 | 3 |
The result reads as follows. S2 holds the best intervals on delivery and quality and the lowest (best) interval on price, so it is the supplier most closely aligned with the ideal direction. S1 finishes last, trailing S2 on all three criteria.
The team hesitates here. The three suppliers' coefficients sit very close to one another. This shows that defuzzifying the intervals erases small differences; had S2's price interval been slightly wider, its defuzzified average would rise and could move closer to S3's.
In the report: "With this interval data, the supplier with the highest closeness coefficient is S2 (0.5034); the gap to S3 (0.5030) is very small, and the width of the intervals should be separately assessed."
Source: this three-supplier example is an illustrative construction built by DecisionMind. A single, verified founding article for this exact step definition under the name "grey projection" could not be independently confirmed as of the time this card was prepared; the detail is recorded in the approval notes. The DecisionMind team is reviewing this method's source citation and certain boundary cases in the direction test. The figures have been verified exactly against both DecisionMind's engine and an independent Python calculation.
2. Maritime: incomplete data in choosing a port operator
A shipping agency must choose between two port operators for container transport. Two criteria apply: loading time (lower is better) and damage rate (lower is better); for both ports, the data is held as intervals drawn from a limited number of past voyage observations. Suppose the first port's loading-time interval is narrow and low, while the second port's damage-rate interval is narrow and low; each is better than the other on the criterion where it is strong.
The method computes the projection for both ports and shows that the gap between them comes out small.
The agency hesitates here. If the two ports' closeness coefficients sit close to one another, the decision should rest not on a single number but on which criterion matters more to the agency. This information does not show up in the coefficient; the justification for the weights must be explained separately in the report.
In the report: "The gap between the two ports' closeness coefficients is small; the choice depends on which criterion the weights prioritise, and this justification should be separately stated in the report."
3. Telecommunications: prioritising regions for infrastructure investment
A telecommunications operator must prioritise a new base-station investment across three regions. Three criteria apply: forecast user demand (higher is better, given as an interval because the demand forecast is uncertain), existing infrastructure density (lower is better) and installation cost (lower is better). Suppose one region's demand interval is wide but its average is the highest, while another region's demand interval is narrow but its average is lower.
The method projects each region's defuzzified and normalised values onto the ideal and anti-ideal directions; the region with the wide demand interval can come out ahead because its average is high.
The operator hesitates here. A wide demand interval carries the risk that actual demand turns out far below the forecast; defuzzification conceals this risk because it carries only the average forward. The region that comes out ahead should therefore also be checked, as a sensitivity test, against the lower bound of its demand interval.
In the report: "Based on the defuzzified values, the region below is favoured; because of the wide interval in this region's demand forecast, the lower-bound scenario should be separately tested."
4. What Not to Do
Three concrete errors, using the three suppliers of Case 1's table. The first is reading S2's coefficient of 0.5034 as "50 per cent suitable"; the coefficient only shows relative alignment. The second is presenting the small gap between S2 and S3 as a decisive advantage; this gap is a closeness produced by defuzzifying the intervals, and a decision should not be made without showing the width of the intervals in the report. The third is entering the lower and upper bounds reversed; this breaks the definition of the grey number and invalidates the calculation.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/grey-projection
Deng, J. (1982). Control problems of grey systems. Systems & Control Letters, 1, 288-294. DOI: 10.1016/S0167-6911(82)80025-X
Ke, H., & Liu, S. (2009). Similarity to ideal-based grey relational projection for multiple criteria decision-making. 2009 IEEE International Conference on Grey Systems and Intelligent Services (GSIS 2009). DOI: 10.1109/gsis.2009.5408022
Liu, S., & Lin, Y. (2006). Grey Information: Theory and Practical Applications. Springer. ISBN: 978-1-85233-995-1. (no DOI)
Tekin, E., & Büyüközkan, G. (2025). A Literature Survey on Grey MCDM: Recent Advances and Applications. In Intelligent and Fuzzy Systems (Lecture Notes in Networks and Systems). Springer. DOI: 10.1007/978-3-031-97985-9_89