Extension card · Spherical
Spherical fuzzy WASPAS (Boltürk and Kutlu Gündoğdu, 2021)
This is the form of WASPAS used when criterion scores are given as three separate numbers stating a degree of support, rejection and hesitancy for a judgement. The weighted-sum and weighted-product components are calculated separately with these three degrees, and only come down to a single score at the very last step.
Base method
WASPAS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Spherical →
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?
Cells. In crisp WASPAS every cell is a single number. In the spherical fuzzy form every cell consists of three degrees: support (μ), rejection (ν) and hesitancy (π). The expert supplies all three directly; hesitancy is not computed as a residual share. The only constraint is that the sum of the three degrees' squares cannot exceed 1. Criterion weights come from outside DecisionMind as crisp numbers.
Scale equalisation. Crisp WASPAS equalises every column by scaling it against its own best value. In the spherical fuzzy form there is no separate scale-equalisation step; every cell is already on the same 0–1 scale across three degrees. Instead, on a cost criterion the support and rejection swap places, while hesitancy stays as it is: (μ, ν, π) → (ν, μ, π).
Sum and product components. What crisp WASPAS's weighted sum (WSM) does here is done by the spherical fuzzy weighted arithmetic mean (SFWA): every alternative's three degrees across the criteria are reduced to a single triple (Q̃¹). What crisp WASPAS's weighted product (WPM) does here is done by the spherical fuzzy weighted geometric mean (SFWG), which likewise comes down to a single triple (Q̃²). SFWA magnifies support in an optimistic way, while SFWG brings rejection to the fore; this corresponds to the compensatory character of summation and the punishing character of multiplication respectively.
Result and crisping. The two triples (Q̃¹, Q̃²) are blended by spherical fuzzy addition into a single triple (Q̃) in the form λ·Q̃¹ ⊕ (1−λ)·Q̃²; DecisionMind does not present λ as a field in the interface, and it comes as an additional input with a default of 0.5. This combined triple is only crisped into a single number at the very last step, with Boltürk and Kutlu Gündoğdu's (2021) score function, (2μ − π/2)² − (ν − π/2)²; a larger Q_i is better.
DecisionMind holds this SFWA/SFWG combination and this score function fixed in spherical fuzzy WASPAS; weights come from outside as crisp numbers, and the method does not generate weights. DecisionMind does not support group decisions in this family (the step that merges several evaluators' matrices); the user enters a single, already merged decision matrix.
How to Read the Output
Q_i is read like the combined score in crisp WASPAS; it only ranks alternatives within this particular set, is not a percentage or a probability, and a larger value is better.
The difference is here. The score formula squares μ together with π in one term, (2μ − π/2)², and this term is not always increasing with respect to μ while π is held fixed. In cells where small μ and large π occur together, the score can first fall and then rise as μ increases a little. This is a feature noted from the literature that DecisionMind's own internal review has flagged in this family too, including SF-WASPAS; it is not an error in the engine but a mathematical consequence of the chosen score function, and it must not be ignored in the report.
Thus instead of writing:
"Q_i has risen, so support has increased"
the report should read:
"Q_i is a score that jointly squares support, rejection and hesitancy; when low support and high hesitancy occur together, a small rise in support can lower the score, so μ, ν and π should also be reported separately"
When to Prefer This over the Base Method
Use this extension when experts give the degrees of support, rejection and hesitancy for a judgement separately, and these three pieces of information run too high to fit the picture fuzzy structure's constraint (a sum of at most 1). A measured criterion is not expanded into three degrees by force. Crisp WASPAS's exit condition applies here too: the matrix must be of a single type, and if no compromise is acceptable on one criterion, this extension is also compensatory.
Mistakes Specific to This Extension
Confusing the value-space constraint. The constraint is the sum of the squares of the three degrees: μ²+ν²+π²≤1. Neither the picture fuzzy structure's constraint (the sum of the three degrees themselves) nor the intuitionistic fuzzy structure's constraint (hesitancy as a derived share) applies here.
Assuming the score always rises with μ. The score (2μ − π/2)² − (ν − π/2)² is not increasing everywhere with respect to μ while ν and π are held fixed. For instance, with ν=0.20 and π=0.40 held fixed, the score is 0.0256 at μ=0.02, 0.0000 at μ=0.10, and 0.0100 again at μ=0.15; as μ rises, the score first falls and then rises. This region occurs in cells where small μ and large π occur together, and can be misread if it is not noticed in the report.
Confusing this score with the closure ratio. In SF-TOPSIS's closure ratio a small value is good; here a large Q_i is good. The reading direction of the two families must be kept separate.
Looking for λ in the interface. λ is not an interface field like the weights here; it comes as an additional input with a default of 0.5.
The governing principle is this:
In spherical fuzzy WASPAS, a larger Q_i is better, but the score formula is not increasing everywhere with respect to μ; this feature should be checked separately, and stated in the report, in cells where low support and high hesitancy occur together.
Cases
The first case is DecisionMind's validation example: it follows Boltürk and Kutlu Gündoğdu's (2021) nine-step algorithm, but does not carry over the numbers from the book's own five-alternative industrial-robot example one for one; it is a small, single-evaluator table. The second case is an illustrative construction.
1. Manufacturing: Choosing an industrial robot for a contract manufacturer (Boltürk and Kutlu Gündoğdu, 2021 context)
A contract manufacturer will choose one of three industrial-robot offers to install on its automotive spare-parts line; this is the type of problem addressed by Boltürk and Kutlu Gündoğdu's (2021) spherical fuzzy WASPAS chapter. There are three criteria: speed and efficiency, precision and repeatability, and compliance with the safety standard. All three are "higher is better." The evaluation team has given separate degrees of support, rejection and hesitancy for every robot-criterion pair.
| Robot | Speed and efficiency | Precision | Safety compliance |
|---|---|---|---|
| R1 | (0.70; 0.20; 0.50) | (0.80; 0.10; 0.40) | (0.60; 0.30; 0.50) |
| R2 | (0.90; 0.10; 0.30) | (0.60; 0.30; 0.60) | (0.80; 0.20; 0.40) |
| R3 | (0.50; 0.40; 0.60) | (0.70; 0.20; 0.50) | (0.70; 0.10; 0.50) |
| Weight | 0.40 | 0.35 | 0.25 |
The method reduces every robot's triple on the three criteria to a sum component with SFWA and a product component with SFWG, blends the two with λ=0.5, and crisps the result with the score function.
| Robot | Q_i | Rank |
|---|---|---|
| R2 | 1.8334 | 1 |
| R1 | 1.4262 | 2 |
| R3 | 0.9532 | 3 |
The result reads as follows. R2 has the highest support and the lowest rejection-hesitancy triple, (0.90; 0.10; 0.30), on speed and efficiency, the most heavily weighted criterion; this advantage offsets its middling performance, (0.60; 0.30; 0.60), on the precision criterion. R3 is not the best on any criterion and finishes last.
The team's hesitation is this: what happens if the weight on speed and efficiency is lowered from 0.40 to 0.05 and precision is given 0.55 (safety compliance stays at 0.40)? When the kernel is run directly and independently in Python with these new weights, R1's score rises to 1.4850 and takes first place; R2 falls to second with 1.3329, and R3 to third with 1.2661, though the gap between the three narrows. This is because R1 carries stronger support than R2 on the precision criterion, (0.80; 0.10; 0.40).
In the report: "With the given weights (0.40; 0.35; 0.25), R2 has the highest Q_i value (1.8334). When the weight is shifted markedly to precision (0.05; 0.55; 0.40), first place passes to R1; which criterion should be prioritised must therefore be separately justified."
Source: This case follows the nine-step algorithm from Boltürk and Kutlu Gündoğdu's (2021) spherical fuzzy WASPAS chapter. It does not carry over the book's own five-alternative, four-criterion, three-evaluator industrial-robot table one for one; it is DecisionMind's smaller validation example, faithful to the formulas. The scores and the weight-trade scenario were independently calculated by this card's author by running the kernel directly. That this family's score function may not increase monotonically under low support and high hesitancy has also been separately noted in DecisionMind's own internal review, including for SF-WASPAS; the detail is in the approval note.
2. Public transport: A local government's choice of fuel technology for its bus fleet
A local government will choose one of three fuel technologies when renewing its bus fleet. There are three criteria: operational reliability, suitability for the maintenance infrastructure, and passenger comfort. The transport department has given separate degrees of support, rejection and hesitancy for every technology-criterion pair.
The method reduces the triples on the three criteria to sum and product components with SFWA and SFWG, blends them with λ=0.5, and scores the result. Suppose the technology with the highest support on operational reliability also shows a low rejection degree on suitability for maintenance infrastructure, and finishes first.
The department's hesitation is this: for a technology whose hesitancy share on the passenger-comfort criterion has remained high, this uncertainty has dissolved into a single score. The department should separately report this first-ranked technology's hesitancy share on passenger comfort and settle it before the tender.
In the report: "One technology stands out because of operational reliability and suitability for maintenance infrastructure; this technology's hesitancy share on the passenger-comfort criterion is higher than the others' and should be addressed before the tender."
3. What Not to Do
In the manufacturing case, changing R2's precision triple, 0.60/0.30/0.60, to a value such as 0.60/0.30/0.80 without checking the constraint is wrong; the sum of the squares becomes 0.36+0.09+0.64=1.09, exceeding the constraint. The second error is reporting R2's Q_i value of 1.8334 as "183 per cent suitability"; Q_i is not a percentage and only ranks these three robots relative to one another. The third error is assuming that Q_i must always rise when μ rises slightly in a low-support cell; the score function may not increase monotonically in this region and must be checked numerically.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/sf-waspas
Boltürk, E., & Kutlu Gündoğdu, F. (2021). Prioritizing manufacturing challenges of a contract manufacturing company for personal auto by using spherical WASPAS method. In C. Kahraman & F. Kutlu Gündoğdu (Eds.), Decision Making with Spherical Fuzzy Sets: Theory and Applications (Studies in Fuzziness and Soft Computing, Vol. 392, pp. 259–276). Springer. DOI: 10.1007/978-3-030-45461-6_11
Zavadskas, E. K., Turskis, Z., Antuchevičienė, J., & Zakarevičius, A. (2012). Optimization of weighted aggregated sum product assessment. Elektronika ir Elektrotechnika, 122(6), 3–6. DOI: 10.5755/j01.eee.122.6.1810
Kutlu Gündoğdu, F., & Kahraman, C. (2019). Spherical fuzzy sets and spherical fuzzy TOPSIS method. Journal of Intelligent & Fuzzy Systems, 36(1), 337–352. DOI: 10.3233/JIFS-181401
Ashraf, S., Abdullah, S., Mahmood, T., Ghani, F., & Mahmood, T. (2019). Spherical fuzzy sets and their applications in multi-attribute decision making problems. Journal of Intelligent & Fuzzy Systems, 36(3), 2829–2844. DOI: 10.3233/JIFS-172009