Methods · Objective weighting
Fuzzy LOPCOW
Fuzzy LOPCOW carries classical LOPCOW's idea, the logarithmic ratio between a criterion's average magnitude and its spread, into fuzzy data by running it separately on the lower, middle and upper end of the triangular fuzzy number and averaging the three results.
Base method's data type: Fuzzy
What Is the Method?
Fuzzy LOPCOW is not a ranking method; it does not order alternatives, it produces criterion weights. Classical LOPCOW is an objective weighting method like Entropy and CRITIC, but it measures spread differently: it takes the logarithm of the ratio between a criterion's normalised values' average magnitude (root mean square) and their spread (standard deviation). Fuzzy LOPCOW, when your data is given as a triangular fuzzy number (lower, middle, upper end), carries out this calculation three times, separately at each end, and then averages.
Ecer and Pamučar proposed classical LOPCOW in 2022. DecisionMind's Fuzzy LOPCOW is not that paper's own proposed fuzzy formulation; separate studies exist in the literature that carry LOPCOW into other kinds of uncertainty, such as neutrosophic and Fermatean fuzzy data (for example Simic et al., 2023), but none of these is identical to the "calculate each end separately, then average" profile DecisionMind implements here. DecisionMind built this profile as its own engineering decision; the card states this explicitly below.
The Philosophy Behind It
The idea behind classical LOPCOW is that how much information a criterion carries can be measured by looking at the ratio between that criterion's average magnitude and its spread. Where alternatives closely resemble one another on a criterion (spread small relative to the average), this ratio grows large and its logarithm stays small; the criterion is not very distinguishing. Where alternatives differ widely from one another, the ratio shrinks and its logarithm grows large; the criterion is the one that decides the outcome. Fuzzy LOPCOW keeps the same idea, but when the data is uncertain it computes this ratio separately at the pessimistic, most-likely and optimistic ends.
One consequence of this design is that fuzziness's effect can differ from criterion to criterion. If a criterion's lower, middle and upper component weights sit close together, that criterion's distinguishing power is a robust finding, independent of data uncertainty. If the components are far apart, the criterion's distinguishing power is sensitive to data uncertainty, and the average conceals that sensitivity.
How It Works
The method proceeds through three steps.
First, validation. Every cell is checked to be an ordered triangular fuzzy number (lower ≤ middle ≤ upper), and direction information is confirmed for every criterion.
Second, three separate classical LOPCOW calculations. The lower, middle and upper component of the triangular fuzzy number are each treated as though they were a separate crisp decision table. Direction-sensitive scale equalisation is carried out separately for each, the logarithm of the ratio between each criterion's average magnitude and its spread is taken, and the result is normalised. The result is three separate weight vectors, one for each component.
Third, averaging and reporting. The three weight vectors are averaged criterion by criterion and rescaled so that they sum to 1. At this step DecisionMind also records how much the fuzzy envelope changes the result.
The formulas behind each step and the intermediate tables are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The fuzzy LOPCOW weight tries to measure the same thing as classical LOPCOW: how widely a criterion's normalised values are spread relative to their magnitude. The difference is that this measurement is the average of three separate (pessimistic, most likely, optimistic) calculations. A weight of 0.35 does not mean "this criterion is 35 per cent of the decision"; it means "in this fuzzy dataset, this criterion's average magnitude-to-spread ratio is roughly 35 per cent of the total ratio."
How close a criterion's lower, middle and upper component weights are to one another should also be checked separately. If expert estimates for a given criterion have been widened by the same proportion for every alternative, for instance by adding and subtracting the same constant from every value, the three components can come out almost identical; this does not mean the criterion's distinguishing power is robust, only that the fuzzification method happens to coincide for this criterion.
Thus instead of writing:
"The fuzzy LOPCOW analysis showed that C3 is the most important criterion"
the report should read:
"In this fuzzy dataset, C3 came out with the highest average weight; the lower and middle component weights coming out identical may indicate that these two components were widened by the same proportion in the data estimate"
Data Type and Inputs
Fuzzy LOPCOW works with triangular fuzzy numbers (TFNs): every cell consists of three values (lower, middle, upper), and lower ≤ middle ≤ upper must hold. In DecisionMind's LOPCOW family there are two members alongside the base method: classical LOPCOW and this fuzzy extension; the family has no other extension. If your data can be expressed as a single crisp number, classical LOPCOW is sufficient.
You need the following: alternatives in rows, criteria in columns, an ordered triangular fuzzy number in every cell, and no empty cells. Direction information is required for every criterion. Weights are not entered; the method produces them. A minimum of two alternatives and two criteria is required; if a criterion carries the same value at all three components across every alternative, that criterion's weight comes out close to zero.
When to Use It, When Not To
Fuzzy LOPCOW is appropriate when your data comes from expert judgement, when you want the weight derived from a spread measure based on the magnitude-to-spread ratio, and when this data can be expressed as a three-point interval. If crisp data is available, classical LOPCOW is sufficient.
The cases where it should not be used follow from its own philosophy. If a criterion carries the same value across every alternative (zero spread), its weight goes to zero. If what is wanted is exactly a particular fuzzy, neutrosophic or Fermatean fuzzy LOPCOW formulation proposed in the literature, DecisionMind's profile is not suitable, because it implements none of these formulations; this point is stated separately below. If the decision-maker's own priority needs to show through in the result, a subjective method is required instead.
Data is fuzzy, weight should be derived from the magnitude-to-spread ratio → Fuzzy LOPCOW
Data is crisp → LOPCOW
Weight should also look at correlation between criteria, data is fuzzy → FUZZY-CRITIC
Both spread and opportunity cost should enter together, data is fuzzy → Fuzzy IDOCRIW
Strengths
Fuzzy LOPCOW's chief strength is that it carries classical LOPCOW's relatively simple and transparent spread measure into fuzzy data; every step can be followed with the same logic at all three components. It carries uncertainty through three separate components and averages only at the last step, which lets DecisionMind record how much fuzziness changes the weight on each criterion. LOPCOW's log-ratio is less sensitive to large values than the raw standard deviation; this property is preserved in the fuzzy version as well.
Weaknesses
Its limitations are both inherited and specific to itself. First, if a criterion carries a constant value across every alternative, its weight is zeroed out; DecisionMind may process this case as a silent zero weight rather than as a separate error, so the result should be read carefully. Second, published studies exist in the literature that carry LOPCOW into other kinds of uncertainty such as neutrosophic and Fermatean fuzzy data (for example Simic et al., 2023), but the profile DecisionMind implements here is not a direct implementation of any of them; "fuzzy LOPCOW in the literature" and "fuzzy LOPCOW in DecisionMind" are not the same thing. Third, if the data estimate for a criterion has been widened by the same proportion for every alternative, for instance by adding and subtracting a fixed margin from every value, the lower and middle component weights can come out almost identical; this is not an error, but it should be remembered that it may be an artefact of the fuzzification method.
Common Mistakes
The most common mistake is assuming this method is a direct implementation of a specific "fuzzy LOPCOW" paper published in the literature; DecisionMind here uses its own TFN-component profile.
A second mistake is reporting only the average weight without checking how close the lower, middle and upper components are to one another. A third is interpreting identical components as meaning "the data is very reliable"; this can in fact be a sign that the expert estimate was widened by the same proportion for that criterion. A fourth is artificially fuzzifying crisp data to run this method; it gives no information different from classical LOPCOW.
The governing principle is this:
The weight fuzzy LOPCOW reports is the magnitude-to-spread ratio calculated separately at three ends and averaged; if the components are far apart, the weight is sensitive to data uncertainty, and the report must state this.
Cases
Each case opens with a fuzzy decision table, describes in words what the method does to that table, and shows how to read the resulting weights. The first case is DecisionMind's own source-code verification example; it is not drawn from a publication. The remaining cases are illustrative constructions.
1. Illustrative example: A three-criterion fuzzy table (DecisionMind source-code verification example)
This example is not a case from the literature. It is a small table built to check whether DecisionMind's engine code produces exactly the expected result; it is not drawn from any publication. Four alternatives are evaluated on three criteria with triangular fuzzy numbers; C1 and C3 are "more is better," C2 is "less is better."
| Alternative | C1 (lower·middle·upper) | C2 | C3 |
|---|---|---|---|
| A1 | 1·2·3 | 4·5·6 | 7·8·9 |
| A2 | 2·3·5 | 7·8·10 | 3·4·6 |
| A3 | 5·6·7 | 2·3·4 | 8·9·10 |
| A4 | 4·5·6 | 6·7·8 | 1·2·3 |
The method calculates a separate magnitude-to-spread ratio for each component.
| Criterion | Lower component | Middle component | Upper component | Average (reported) |
|---|---|---|---|---|
| C1 | 0.341 | 0.341 | 0.363 | 0.349 |
| C2 | 0.295 | 0.295 | 0.296 | 0.295 |
| C3 | 0.364 | 0.364 | 0.341 | 0.356 |
The result reads as follows. C3 receives the highest average weight, because the alternatives show the widest spread on this criterion. What stands out is that the lower and middle component weights come out identical across all three criteria. This is because every cell's lower and middle values in this table are given with a constant unit difference (lower = middle − 1); min-max scaling absorbs such a constant shift completely, and the lower and middle components produce the same normalised table. This does not mean the criteria's distinguishing power is especially robust; it is a consequence of how the data has been fuzzified in this table.
Caveat: the ranking shifts slightly at the upper component, where C1 and C3 almost swap places (0.363 against 0.341), because the increases at the upper end are not distributed proportionally across the criteria. This shows that the average conceals a small but real sensitivity.
In the report: "Criterion weights were computed with fuzzy LOPCOW; C3's highest average weight (0.356) reflects the wide spread on this criterion. The lower and middle component weights coming out identical stems from the lower and middle estimates in this table being given with a constant difference."
Source: DecisionMind fuzzy LOPCOW engine, source-code verification example (not from a published paper, but from the engine's own engineering record).
2. Aviation: Fuzzy weighting for ground-handling equipment selection
An airline ground-handling unit wants to derive criterion weights from data before choosing among four baggage-handling vehicles. The field team assessed three criteria with triangular fuzzy numbers: fuel consumption, load capacity and mean time between failures. Fuel consumption is "less is better."
The method calculates a separate magnitude-to-spread ratio for each component and averages the three components. Suppose time between failures turns out to be the criterion on which the vehicles differ most from one another, and it receives the highest weight; on fuel consumption the vehicles come out close to one another, so this criterion receives a low weight.
The unit's hesitation: fuel consumption's low weight does not mean it is unimportant in terms of cost; it is not distinguishing because fuel consumption is already similar across these four vehicles. The unit decides to note this distinction in the report and to monitor fuel consumption separately as a cost constraint.
In the report: "Criterion weights were computed with fuzzy LOPCOW; fuel consumption's low weight reflects the similarity among these four vehicles, not the unimportance of cost."
3. E-commerce: Fuzzy weighting for warehouse automation system selection
An e-commerce company wants to weight four criteria before choosing among three warehouse automation system proposals: installation cost, hourly order-picking capacity, error rate and integration time. Installation cost, error rate and integration time are "less is better." The engineering team assessed these four criteria with triangular fuzzy numbers.
The method calculates a separate magnitude-to-spread ratio for each component. Suppose error rate shows the widest spread among the proposals and receives the highest weight; integration time comes out similar across the proposals and receives the lowest weight.
The company's hesitation: integration time's low weight does not mean it is operationally unimportant; it is not distinguishing because all three proposals integrate in a similar time. The company decides to add integration time to the contract separately as a delivery-schedule clause.
In the report: "Criterion weights were computed with fuzzy LOPCOW; integration time's low weight reflects the similarity among the three proposals, not its operational unimportance; this clause will also be added to the contract."
4. What Not to Do
In the illustrative example, if the identical lower and middle component weights were reported, without investigating the cause, as "proof that the criterion is very robust," the real cause, that the data was fuzzified with a constant shift, would be concealed. A second error is assuming this method is a direct implementation of Simic and colleagues' (2023) work or another published fuzzy or neutrosophic LOPCOW study; DecisionMind here uses a different, its own TFN-component profile. A third error is permanently dismissing a criterion as "unimportant" upon noticing that it carries a constant value across every alternative and that its weight comes out close to zero; a zero weight only reflects the situation in this particular table.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/fuzzy-lopcow
Ecer, F., & Pamučar, D. (2022). A novel LOPCOW-DOBI multi-criteria sustainability performance assessment methodology: An application in developing country banking sector. Omega, 112, 102690. DOI: 10.1016/j.omega.2022.102690
Simic, V., Dabic-Miletic, S., Tirkolaee, E. B., Stević, Ž., Ala, A., & Amirteimoori, A. (2023). Neutrosophic LOPCOW-ARAS model for prioritizing industry 4.0-based material handling technologies in smart and sustainable warehouse management systems. Applied Soft Computing, 143, 110400. DOI: 10.1016/j.asoc.2023.110400 (The profile described by DecisionMind in this card does not implement this paper's neutrosophic formulation; the paper is one example in the literature of LOPCOW being carried into fuzzy or uncertain data.)
Odu, G. O. (2019). Weighting methods for multi-criteria decision making technique. Journal of Applied Sciences and Environmental Management, 23(8), 1449–1457. DOI: 10.4314/jasem.v23i8.7