Extension card · Fuzzy
Fuzzy SMART
Fuzzy SMART is the form of SMART used when the importance ratings a decision-maker gives to criteria are verbal or approximate. It takes these ratings as triangular fuzzy numbers and produces only the criterion weights.
Base method
SMART →
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?
There is an important difference in scope here, not merely a calculation difference. The base SMART card explains the method from beginning to end. First, the worst and best end of every criterion is fixed. Then alternatives are placed between 0 and 1 relative to this end. Next, importance ratings are converted into weights, and finally the alternatives' utility scores are calculated and ranked.
This DecisionMind extension makes only the third step fuzzy. This is the step that converts importance ratings into weights.
Input. No alternative table is entered into this extension. The input is only the list of criteria and the importance rating given to each. Every importance rating consists of three numbers: minimum, most likely, maximum.
Weight derivation. In crisp SMART, the decision-maker gives each criterion an importance rating, and these ratings are normalised so that they sum to 1. Fuzzy SMART carries out this same normalisation separately on all three components. One weight vector emerges from the minimum ratings, one from the most-likely ratings, one from the maximum ratings. These three vectors are then averaged criterion by criterion and renormalised so that the total is again 1.
Result. The output is a weight vector, not a ranking. Scoring and ranking alternatives falls outside this extension's scope; it corresponds to the fourth step on the base SMART card and is not run here.
DecisionMind, in this extension, also calculates the difference between the averaged weight and the weight derived from the most-likely component alone. This difference shows how much the uncertainty margin the expert gave changes the weight. If all three components produce identical weights, this is flagged as a warning.
How to Read the Output
The output is a weight vector showing the relative importance of the criteria. The criterion with the highest weight is the one the decision-maker found most important in the ratio scoring. This weight does not say which alternative comes out ahead, because this extension never sees any alternatives.
The difference is here: the weight is now derived from three separate rating bands, minimum, most likely and maximum. If all three bands give the same weight, the expert's uncertainty has not affected the weight. If the three bands give different weights, the report must show which band is driving the weight.
Thus instead of writing:
"The Fuzzy SMART analysis showed K1 to be the most important criterion"
the report should read:
"K1 obtained the highest weight in all three of the minimum, most-likely and maximum rating bands. Because these three bands come out close together, the weight is not sensitive to the width of the range the decision-maker gave"
When to Prefer This over the Base Method
The decision-maker may think of an importance rating as a range rather than a single number when scoring criteria. If they say, for instance, "I would give this criterion a minimum of 50, most likely 60, maximum 70," Fuzzy SMART is preferred. If the importance rating is already a single crisp number, fuzzification adds nothing, and base SMART suffices.
This extension produces weights only. If alternatives are to be scored and ranked, these weights should be used as the input to base SMART or another ranking method. If no compromise is acceptable on one criterion, screening should be applied before weighting.
Mistakes Specific to This Extension
Trying to give this extension an alternative table. The input is only a triple of importance ratings per criterion. An alternative table does not belong here; it belongs in base SMART itself.
Failing to notice proportional fuzzification. If the same proportional width has been added to every criterion, for instance if all ratings have been scaled up and down by the same factor, the three bands give exactly the same weight. This is not an error, but if it goes unnoticed it can create the misleading impression that "the three bands were each calculated separately."
Presenting the weight as an objective result. The weight comes from the decision-maker's own subjective ratio scoring. DecisionMind does not generate these ratings; it only converts them into weights in fuzzy form.
Widening the rating band without justification. Opening up a single crisp rating into three numbers afterwards adds no information; it only manufactures an apparent uncertainty.
The governing principle is this:
Fuzzy SMART exists to carry the approximation in the decision-maker's importance ratings into the weight vector. Any application that presents this weight as though it were a ranking outcome, or that conceals its subjective source, misrepresents the method's scope.
Cases
The first case is an illustrative example, reproduced from DecisionMind's own engine code. The second case is fictional.
1. Illustrative example: Ratio importance ratings for three criteria (DecisionMind's validation example)
A decision-maker gives importance ratings to three criteria by ratio scoring. The ratings are given not as single numbers but as minimum, most likely, maximum.
| Criterion | Importance rating |
|---|---|
| C1 | (72; 80; 88) |
| C2 | (54; 60; 66) |
| C3 | (27; 30; 33) |
The method derives a separate weight vector in each of the three bands by dividing the ratings by their total, then averages the three vectors.
| Criterion | Weight |
|---|---|
| C1 | 0.4706 |
| C2 | 0.3529 |
| C3 | 0.1765 |
C1 comes out the most important criterion, C3 the least important. Here the rating bands are proportional, meaning the minimum, most-likely and maximum ratings keep the same ratio. Because of this, all three bands give exactly the same weight, and DecisionMind flags this with a degeneracy warning.
The decision-maker's hesitation lies here: this warning shows that the uncertainty margin the expert gave has not affected the weight at all. Had the rating bands not been proportional, that is, had the maximum ratings not kept the same ratio, the three bands could have given different weights. In that case, which band is driving the weight would need separate examination.
In the report: "C1 obtained the same weight, 0.4706, in all three of the minimum, most-likely and maximum rating bands. Because these three bands come out identical, the weight is not sensitive to the width of the given range."
Source: This example has been reproduced independently from DecisionMind's Fuzzy SMART engine. This profile has no separate published literature source of its own; it rests on DecisionMind's own engine code.
2. Construction: A tender committee weighting its evaluation criteria
A construction firm's tender-evaluation committee is giving importance ratings to three criteria by ratio scoring. The criteria are technical competence, price and completion time. Because committee members could not fully agree on the ratings, a minimum, most likely and maximum rating is given for each criterion.
| Criterion | Importance rating |
|---|---|
| Technical competence | (60; 70; 85) |
| Price | (50; 55; 65) |
| Completion time | (20; 25; 35) |
The method derives a separate weight vector in each of the three bands and averages them.
| Criterion | Weight |
|---|---|
| Technical competence | 0.4626 |
| Price | 0.3675 |
| Completion time | 0.1699 |
Technical competence comes out the most important criterion, completion time the least important. This time the rating bands are not proportional; the three bands give different weights. The difference between the average and the weight derived from the most-likely band alone is roughly 0.008, small but not zero.
The committee's hesitation lies here: if the rating for completion time were (35; 40; 50) instead of (20; 25; 35), this criterion's weight would rise from 0.17 to 0.245. Technical competence would still remain the most important criterion. If the rating for completion time were raised to roughly equal that of price, for instance to the (50; 55; 65) band, the two criteria's weights would come nearly level. If the rating goes slightly beyond this, completion time overtakes price in weight. This has been calculated independently.
In the report: "Technical competence obtained the highest weight, 0.4626, in the average of the three rating bands. Completion time's weight could approach or overtake price's if the rating given to this criterion is raised."
3. What Not to Do
Had the rating bands in the first case been used directly as weights without normalising their total to 1, the three criteria's weights would have summed to more than 1 and the subsequent ranking step would have broken down. The second error is ignoring, as in the second case's committee, the fact that the three bands come out different from one another, and reporting only the weight from the most-likely band. This conceals the disagreement among committee members. The third error is presenting the weight vector this extension produces as though it were an alternative ranking. This extension scores no alternatives at all; it produces only criterion weights.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/fuzzy-smart
Edwards, W. (1977). How to use multiattribute utility measurement for social decisionmaking. IEEE Transactions on Systems, Man, and Cybernetics, 7(5), 326–340. DOI: 10.1109/TSMC.1977.4309720
Edwards, W., & Barron, F. H. (1994). SMARTS and SMARTER: Improved simple methods for multiattribute utility measurement. Organizational Behavior and Human Decision Processes, 60(3), 306–325. DOI: 10.1006/obhd.1994.1087
Zadeh, L. A. (1965). Fuzzy sets. Information and Control, 8(3), 338–353. DOI: 10.1016/S0019-9958(65)90241-X