Methods · Ranking
FDOSM (Decision by Opinion Score Method)
FDOSM takes each alternative's performance on each criterion directly as an "opinion score," ratios this score against the best value, and combines it with weights to rank the alternatives.
Base method's data type: Classical
What Is the Method?
FDOSM stands for "Fuzzy Decision by Opinion Score Method." Salih, Zaidan and Zaidan (2020) proposed it, and since then it has built a wide family of applications, particularly in technology and system benchmarking studies, health-monitoring systems, network-security protocols and biometric-recognition systems (Muhsen et al., 2023). The method's core idea is that an alternative's performance on the criteria is expressed not through a direct physical measurement but through an "opinion score" (an assessment an expert or decision-maker gives relative to the ideal). The manifest DecisionMind implements runs the method's single-decision-maker, crisp (non-fuzzy) base version; its output is a score for every alternative and a rank produced by that score.
The Philosophy Behind It
In some decisions a direct physical measurement is not possible. Questions such as "how good is this software's usability" or "how high is this system's reliability" cannot be measured with a ruler; an expert or user expresses this with a score. FDOSM takes this score as an answer already given to the question "how does this compare with the ideal," and does not build a new ideal point on top of it; it merely brings these scores onto a common scale and combines them with weights. In the method's fuzzy version, when several experts give different opinions, these opinions are expressed as triangular fuzzy numbers (a lower, middle and upper value), averaged, and reduced to a single crisp number (defuzzification); in the crisp version DecisionMind runs in this manifest, the input is already a single expert's crisp score, so these steps act as a passthrough.
This idea has one consequence. FDOSM is compensatory and sits close to the weighted-sum family of methods, but its emphasis differs. Where TOPSIS assesses an alternative's raw measurement by its distance to ideal and anti-ideal points, FDOSM assumes the input is already an assessment (an opinion) and ratios this assessment against the best value.
How It Works
The method consists of six steps; in DecisionMind's crisp-data version, the first three steps act as a passthrough because the input is already a single crisp number.
First, converting linguistic expressions to triangular fuzzy numbers. If several experts have given linguistic assessments such as "good," "medium" or "poor," these are converted into triangular fuzzy numbers made of a lower, middle and upper value. This step is skipped in the crisp-data version.
Second, combining decision-makers' opinions. If more than one expert exists, their opinions are averaged. This step is skipped in the single-decision-maker crisp version.
Third, defuzzification. If a fuzzy value exists, it is reduced to a single crisp number. This step is skipped in the crisp version.
Fourth, linear-maximum normalisation. Every cell is ratioed against the best value in its own column: for benefit criteria the cell value is divided by the column's largest value, for cost criteria the column's smallest value is divided by the cell value.
Fifth, the weighted opinion score. The normalised values are multiplied by the criterion weights and summed.
Sixth, ranking. Alternatives are ranked by this score from highest to lowest.
The formulas behind each step, the intermediate tables and citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The opinion score is the weighted average of how close an alternative sits to the best value on every criterion. Unlike TOPSIS's closeness score, this score never looks at the worst value (the anti-ideal); it only ratios against the best. A score close to 1 means "reaches almost the best value on every criterion"; a low score shows the alternative falls short of the best value on one or more criteria. This score assumes the input is already an expert assessment (an opinion); if the input is a raw physical measurement, the method normalises it as given and does not itself question how reliable an "opinion" the measurement carries.
Thus instead of writing:
"System 2's score is the highest, so it is objectively the best system"
the report should read:
"Given the opinion scores and weights supplied, System 2 sits at the highest ratio to the best value; who gave these scores and how must be stated in the report"
Data Type and Inputs
Crisp data. In DecisionMind, this manifest runs the method's single-decision-maker base version, which requires no defuzzification, and currently has no extension. The original FDOSM in the literature carries the name "fuzzy" because it combines several experts' triangular fuzzy opinions; this extended multi-expert version is not covered by DecisionMind's manifest. You need an opinion score (or a direct measurement) for every alternative on every criterion, criterion directions, and weights summing to 1. FDOSM does not produce weights, it takes them from outside.
When to Use It, When Not To
If the alternatives being compared are already scored against an ideal reference, FDOSM is a natural choice, particularly in technology or system benchmarking studies; the literature has used it frequently in health-monitoring systems, network-security protocols and similar technical comparisons (Muhsen et al., 2023).
There are two situations where it should not be used. If your data is a raw physical measurement and jointly assessing distance to the ideal and the anti-ideal (as TOPSIS does) would be more informative, FDOSM's structure of ratioing only against the best falls short. If you need to combine several experts' disagreement in a fuzzy way, DecisionMind's version, being limited to a single decision-maker with crisp data, is not sufficient.
Input is already an expert opinion score, single decision-maker, crisp data → FDOSM
Several experts disagree significantly, fuzzy combination is needed → FDOSM's multi-expert fuzzy version (not covered by this manifest)
Input is a raw measurement, both the ideal and the anti-ideal must be considered together → TOPSIS
Weights, not a ranking, are needed → AHP, BWM, SWARA (subjective); Entropy, CRITIC (objective)
Strengths
FDOSM's greatest strength is its simplicity; its computational burden is small, and because it sits close to the weighted-sum family, the result is easy to interpret. The opinion-score philosophy offers a natural framework for comparisons that rest on expert assessment where pure physical measurement is not possible. Since Salih, Zaidan and Zaidan's (2020) proposal, the method has gained a wide family of applications, showing that it offers a skeleton adaptable to different fuzzy environments (Pythagorean fuzzy, neutrosophic, dual-hesitant fuzzy, and so on) (Alamoodi et al., 2022).
Weaknesses
Its limitations stem from its structure. First, the method ratios only against the best value and never uses the worst value (the anti-ideal); it does not offer the "both close to the good and far from the bad" balance that TOPSIS provides. Second, DecisionMind's version is limited to a single decision-maker with crisp data; the method's actual "fuzzy" contribution, the multi-expert opinion-combining and defuzzification steps, acts here as a passthrough and is not active. Third, Muhsen and colleagues' (2023) systematic review shows that consistency problems exist across the literature in how opinion scores are gathered within the FDOSM family of studies. Fourth, the quality of the opinion scores lies outside the method; a flawless calculation built on poor or inconsistent scores still gives a weak ranking.
Common Mistakes
The most common mistake is presenting the opinion score as a raw measurement without reporting who gave it and how. A second mistake is assuming that because the method's name contains "fuzzy," it automatically performs a multi-expert calculation; DecisionMind's manifest works with crisp, single-expert data. A third mistake is confusing the FDOSM score with TOPSIS's closeness score and assuming it also accounted for distance to the anti-ideal; FDOSM only ratios against the best. A fourth mistake is placing opinion scores given on different scales (one on a 1–5 scale, another on a 1–10 scale) into the same table without correction.
The governing principle is this:
An FDOSM result is the weighted ratio of the opinion scores supplied as input against the best value; if the report does not state how and by whom these scores were given, what the result is measuring remains unclear.
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. Health: A hospital unit's choice of remote patient-monitoring system (DecisionMind's validation example)
A hospital unit's technical team will bring one of three remote patient-monitoring systems into use. Three criteria have been set: data accuracy score, user-interface score and durability/battery-life score; all three are "higher is better" scores given out of ten by expert judgement. The weights are 0.40 for data accuracy, 0.30 for user interface and 0.30 for durability.
| System | Data accuracy | User interface | Durability |
|---|---|---|---|
| S1 | 8 | 7 | 6 |
| S2 | 7 | 9 | 8 |
| S3 | 6 | 8 | 9 |
| Direction | higher is better | higher is better | higher is better |
| Weight | 0.40 | 0.30 | 0.30 |
The method ratios every column against its own best value (best 8 in data accuracy, best 9 in interface, best 9 in durability), then multiplies these ratios by the weights and sums them.
| System | Opinion score | Rank |
|---|---|---|
| S2 | 0.917 | 1 |
| S3 | 0.867 | 2 |
| S1 | 0.833 | 3 |
The result reads as follows. S2 holds the highest score on no single criterion (it trails S1 on data accuracy) but rises to first place by staying close to the best value on all three criteria. S1, despite holding the best score on data accuracy, the most heavily weighted criterion, falls to last place because it trails noticeably behind the best value on the other two criteria. S3 holds the best score on durability but stays in second place because it trails on data accuracy.
The technical team hesitates here: the data accuracy, user-interface and durability scores rest on expert observation; if the standard behind these scores, how many patients, how many days of observation, is not stated, how reliable S1's edge in data accuracy really is remains debatable.
In the report: "Given the opinion scores and weights supplied, S2 sits closest to the best value (0.917); the observation period and number of cases behind these scores must be stated in the report."
Source: The decision table and weights are drawn from DecisionMind's kernel validation fixture; the manifest flags this example as "synthetic, closed-form, illustrative," and no 3x3 table matching it verbatim is reported in Salih and colleagues' (2019/2020) papers. The figures were produced by running DecisionMind's FDOSM engine.
2. Telecom: Assessing network security software
A telecom operator will choose one of three network security software packages. The criteria are attack-detection success score, false-alarm rate score (lower is better, so it is inverted and read as "higher is better") and the score system administrators give for ease of use. The weights were set by the security team.
The method ratios every criterion against its own best value and combines the ratios with weights. Suppose the software with the best attack-detection score falls to second place because it holds the lowest ease-of-use score.
The security team hesitates here: the ease-of-use score rests on system administrators' subjective assessment; how many administrators gave it and how much agreement exists between them is not known.
In the report: "The software with the best attack-detection score sits second because of its comparatively low ease-of-use score; how many administrators gave the ease-of-use score, and with what degree of agreement, must be stated."
3. Logistics: Assessing freight-tracking software
A freight company will choose one of three logistics-tracking software packages. The criteria are location-update frequency score, integration-ease score and customer-support quality score; all three are given by the joint assessment of the field team and IT department.
The method ratios every criterion against its best value and combines the ratios with weights. Suppose the software with the lowest customer-support score still rises to first place thanks to its edge on the other two criteria.
The company hesitates here: a software package with a low customer-support score coming out first prompts the company to question whether this criterion's weight has been set high enough; the company may review this weight.
In the report: "The software trailing on customer support sits first because of its edge in location-update frequency and integration ease; the weight of the customer-support criterion may be reviewed to better reflect the company's priorities."
4. What Not to Do
In the health case, reading S2's 0.917 score as "S2 is nearly perfect" is wrong; the score is only a ratio against the best value among these three systems, not an absolute measure of quality. A second error is feeding the data accuracy, user-interface and durability scores into the calculation without ever questioning the scale on which they were given or who gave them; these scores are opinions, not physical measurements. A third error is seeing FDOSM's "fuzzy" name and assuming the method automatically accounts for several experts' disagreement; this manifest works with crisp, single-expert data.
Sources
For the formulas behind each step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/fdosm
Salih, M. M., Zaidan, B. B., & Zaidan, A. A. (2020). Fuzzy decision by opinion score method. Applied Soft Computing, 96, 106595. DOI: 10.1016/j.asoc.2020.106595
Muhsen, Y. R., Husin, N. A., Zolkepli, M. B., & Manshor, N. (2023). A systematic literature review of fuzzy-weighted zero-inconsistency and fuzzy-decision-by-opinion-score-methods: assessment of the past to inform the future. Journal of Intelligent & Fuzzy Systems. DOI: 10.3233/jifs-230803
Alamoodi, A. H., Albahri, O. S., Zaidan, A. A., AlSattar, H. A., Ahmed, M. A., Pamucar, D., Zaidan, B. B., Albahri, A. S., & Mahmoud, M. S. (2022). New extension of fuzzy-weighted zero-inconsistency and fuzzy decision by opinion score method based on cubic Pythagorean fuzzy environment: a benchmarking case study of sign language recognition systems. International Journal of Fuzzy Systems. DOI: 10.1007/s40815-021-01246-z