Methods · Ranking
ERVD (Election Based on Relative Value Distances)
ERVD judges every alternative not against an "ideal point" but against a reference (expectation) level the decision-maker has set in advance; it weighs losses below that reference more heavily than gains above it.
Base method's data type: Classical
What Is the Method?
ERVD (Election based on Relative Value Distances) is a ranking method that, given a numerical decision table, places alternatives in a single order. Its output, like TOPSIS's, is a closeness score between 0 and 1 and a rank based on that score. Its key difference from TOPSIS is that, instead of building the ideal and anti-ideal points from the dataset's own best and worst values, it starts from a reference point the decision-maker has set in advance. Shyur, Yin, Shih and Cheng (2015) proposed it; the method carries prospect theory, from behavioural decision theory, into multi-criteria decision-making.
The Philosophy Behind It
In TOPSIS, the "best" and "worst" alternatives are built from the alternative set itself; when the alternative set changes, these two points shift with it. ERVD asks a different question: "how does this alternative perform relative to the expectation level I have set in advance?" Staying above the expectation level is a gain, falling below it is a loss. Kahneman and Tversky's (1979) prospect theory shows that people feel losses more heavily than equally sized gains; ERVD renders this idea numerically. Falling slightly below the reference on a criterion is penalised more heavily than rising by the same amount above it; this penalty ratio is set by a loss-aversion coefficient (λ). Sensitivity also decreases as both gains and losses grow: the first unit of difference is felt strongly, later units make less difference; this is captured by a curvature parameter (α).
This idea has one consequence. ERVD is compensatory, just like TOPSIS: a weakness on one criterion can be balanced by strength on another. But the balancing is not symmetric: a shortfall below the reference weighs more heavily than an equally sized surplus above it. Because the reference point comes from the decision-maker rather than from the dataset, ERVD's ideal point does not shift as readily as TOPSIS's when the alternative set changes; this is an advantage as long as the reference is held fixed.
How It Works
The method proceeds through four steps.
First step, sum normalisation. Every column is divided by the sum of the values in that column; each cell thereby becomes its column's share. The reference point is scaled by the same column sum. This normalisation does not take account of direction (whether benefit or cost); direction comes into play at the next step.
Second step, the prospect-theory value function. Every cell is compared against the normalised reference point. For benefit criteria, a value above the reference is a gain and is scaled down by the curvature parameter α; a value below the reference is a loss and is scaled by both α and the loss-aversion coefficient λ, which magnifies it disproportionately. For cost criteria this logic is reversed: below the reference is a gain, above it is a loss.
Third step, two reference points and decomposition. In the value table, the best value on each criterion builds the positive ideal, the worst value the negative ideal. Every alternative's weighted absolute distance to these two points is calculated.
Fourth step, relative closeness. An alternative's distance to the negative ideal is divided by the sum of its two distances. Alternatives are then ranked from the highest score 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 relative closeness score tells you how well an alternative stands, relative to the other alternatives in this analysis, given the stated reference point and the stated loss-gain assumptions. This score changes if the reference point is changed; TOPSIS's ideal point is at least consistent within the same alternative set, since it is derived from that dataset, whereas ERVD's reference is a choice made by the decision-maker, and once that choice changes, the whole order may be reshaped. The λ and α parameters default to values from Tversky and Kahneman's (1992) risk experiments; these values are not measured from this decision's own context.
Thus instead of writing:
"ERVD shows this alternative is the best"
the report should read:
"With this reference point and these loss-gain assumptions, the alternative closest to the ideal is this one; the order may change if the reference or λ/α is changed"
Data Type and Inputs
Crisp data. DecisionMind currently has no extension of this method. You need a complete table with alternatives in rows, criteria in columns, one number per cell; weights summing to 1 for every criterion (ERVD does not produce weights, it takes them from outside); a reference (expectation) value for every criterion; and, optionally, a loss-aversion coefficient (λ, default 2.25) and a curvature parameter (α, default 0.88). These two constants come from Kahneman and Tversky's (1992) experimental work; different values may be more suitable in a different context.
When to Use It, When Not To
If you have a clear expectation or minimum acceptable level, and you think falling below it should count as a heavier loss than rising above it, ERVD is a suitable choice. It is especially meaningful in decisions carrying a "must not fall below this line" logic, such as safety, compliance or regulatory standards.
There are situations in which it should not be used. If you have no natural reference or expectation level, and it seems more natural for the ideal point to be derived from the dataset itself, TOPSIS should be preferred. Working with the default values without questioning whether the loss-gain asymmetry is meaningful in this decision context, that is, whether λ and α are specific to this case or drawn from general risk experiments, grounds the result in an unexamined assumption.
A clear reference/expectation level exists, losses should count more heavily than gains → ERVD
No reference exists, the ideal should be derived from the dataset itself → TOPSIS
Not "the best" but "the compromise limiting the greatest regret" is wanted → VIKOR
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective) · Entropy, CRITIC (objective)
Strengths
ERVD's most important strength is that it carries a well-documented finding of behavioural decision theory (Kahneman and Tversky, 1979), loss-gain asymmetry, into a numerical framework. Because the reference point is set explicitly from outside, it does not shift on its own as the dataset changes the way TOPSIS's ideal point does; as long as the reference is held fixed, the risk that the whole ranking is reshaped when a new alternative is added is reduced. Because the method uses a computational structure similar to TOPSIS's, it is relatively easy to understand and apply.
Weaknesses
Its limitations stem from the reference point and the parameters coming from outside. First, the result is highly sensitive to the chosen reference point; a different reference can produce a different order, and this choice usually comes not from the data but from the decision-maker's own judgement. Second, the loss-aversion coefficient (λ=2.25) and curvature parameter (α=0.88) default from Tversky and Kahneman's (1992) individual risk experiments; that these values also hold in a specific supplier-selection or public-sector context is an assumption, not a measured fact. Third, the sum-normalisation step does not take account of direction, leaving direction to be handled in the value function; this is an easy point at which, in practice, where criterion direction is handled can be confused. Fourth, which of α and λ plays which role (α curvature, λ loss-magnification coefficient) can easily be mixed up.
Common Mistakes
The most common mistake is choosing the reference point at random, or from the alternatives' own average, and presenting it as an external standard; the reference should come from the decision context's own expectation, not from the data. A second mistake is leaving λ and α at their default values without noting in the report that this is an assumption. A third is confusing the default values of the curvature parameter (α) and the loss-magnification parameter (λ); DecisionMind's own technical notes specifically stress how easily this confusion arises. A fourth is reading the relative closeness score the way one reads TOPSIS's, and comparing it with a score from another analysis built with a different reference point. A fifth is looking for criterion direction (benefit or cost) only at the normalisation step and overlooking that it is also handled at the value-function step.
The governing principle is this:
An ERVD result is a reflection of the reference point you set and the loss-gain asymmetry you accept; if either is contested, the order is contested too, and the report must show this.
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. Education: An examination centre's choice of digital examination platform (DecisionMind's validation example)
An examination centre will choose one of three digital exam-delivery platforms. Three criteria have been set: a system-stability score, a user-satisfaction score and a security-audit score; all three are "higher is better" and scored out of a hundred. The weights are 0.33 for system stability, 0.33 for user satisfaction and 0.34 for security audit. The oversight board has set the minimum acceptable level (reference point) for each criterion at 80 for system stability, 75 for user satisfaction and 80 for security audit. The loss-aversion coefficient and curvature parameter are left at their default values (λ=2.25, α=0.88).
| Platform | System stability | User satisfaction | Security audit |
|---|---|---|---|
| P1 | 80 | 70 | 87 |
| P2 | 85 | 65 | 76 |
| P3 | 78 | 90 | 72 |
| Direction | higher is better | higher is better | higher is better |
| Weight | 0.33 | 0.33 | 0.34 |
| Reference | 80 | 75 | 80 |
The method normalises every cell against the column sum, then compares each cell against the reference: above the reference is a gain, below it a loss, and losses are magnified by the λ coefficient. Positive and negative ideal points are then built, and each platform's distance to these two points is measured.
| Platform | Relative closeness score | Rank |
|---|---|---|
| P1 | 0.565 | 1 |
| P3 | 0.507 | 2 |
| P2 | 0.256 | 3 |
The result reads as follows. P1 does not hold the highest score on any single criterion: it sits exactly at the reference level on system stability (80), above the reference on security audit (87), and slightly below the reference on user satisfaction (70). P2, despite having the highest score on system stability, finishes last, because its user satisfaction sits clearly below the reference (65, against a reference of 75), and this open loss is penalised heavily by the loss-gain asymmetry. P3 has the highest score on user satisfaction (90) but falls below the reference on the other two criteria.
The oversight board hesitates here: the reference level [80, 75, 80] is a standard the board set itself; it is not derived from the data. If the reference were changed slightly, say the user-satisfaction reference pulled down to 70, P2's loss would shrink and the order could change. The λ and α parameters, moreover, come not from this examination centre's own risk attitude but from general risk experiments.
In the report: "Given the set reference level and the default loss-gain coefficient, P1 is the platform closest to the ideal (0.565); this result stems from the heavy penalty on P2's below-reference user satisfaction. If the reference level or the loss-gain coefficient is changed, the order should be reassessed."
Source: the decision table and parameters are drawn from DecisionMind's manifest validation fixture; the values were computed with the pymcdm library's ERVD implementation. This example is not taken directly from Shyur and colleagues' (2015) article; it is DecisionMind's own validation example.
2. Mining: Selecting a contractor for mine-site rehabilitation
A mining company will select one of three contractors to rehabilitate a closed site. The criteria are a soil-remediation success score, completion time and cost; the first is a benefit criterion, the other two are cost criteria. The regulator has set the minimum acceptable soil-remediation success score as the reference.
The method evaluates the three bids against this reference; a success score above the reference is a gain, below it a loss. Suppose the cheapest bid falls clearly below the reference on soil-remediation success, and for this reason finishes last despite its low cost.
The company hesitates here: the reference level is the regulator's minimum standard and cannot be changed, but how large the loss-aversion coefficient should be in this context, that is, how many times heavier an environmental failure should count than cost, remains open to debate.
In the report: "The bid whose soil-remediation score falls below the minimum regulatory standard finishes behind despite its low cost; the choice of the loss-aversion coefficient directly affects this result and must be justified in the report."
3. Maritime: A port operator's choice of cargo-handling equipment supplier
A port operator will select one of three container-crane suppliers. The criteria are handling speed, failure frequency and unit cost; handling speed is a benefit criterion, the other two are cost criteria. The operator has taken the industry average as the reference for failure frequency.
The method compares the three bids against this reference. Suppose the fastest crane sits clearly above the industry average (that is, worse) on failure frequency, and this loss overshadows its speed advantage.
The operator hesitates here: taking the industry average as the reference may look neutral, but which year and region that average is drawn from affects the result; a different reference year could give a different order.
In the report: "The bid whose failure frequency sits above the industry average finishes behind despite its advantage in handling speed; the source and year of the industry average used as the reference should be stated in the report."
4. What Not to Do
In the examination-centre case, deriving the reference level from the three platforms' own average rather than using [80, 75, 80] is wrong; this makes the data its own reference instead of setting an external standard, defeating the method's purpose. A second error is presenting the values λ=2.25 and α=0.88 as "the method's own calculation" without mentioning them in the report; these are selectable assumptions and must be reported. A third error is comparing P1's score of 0.565 directly with a score computed in another analysis using a different reference point; the two scores are produced against different reference standards and cannot be compared.
Sources
For the formulas behind each step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/ervd
Shyur, H. J., Yin, L., Shih, H. S., & Cheng, C. B. (2015). A multiple criteria decision making method based on relative value distances. Foundations of Computing and Decision Sciences, 40(4), 299–315. DOI: 10.1515/fcds-2015-0017
Kahneman, D., & Tversky, A. (1979). Prospect theory: An analysis of decision under risk. Econometrica, 47(2), 263–291. DOI: 10.2307/1914185
Tversky, A., & Kahneman, D. (1992). Advances in prospect theory: Cumulative representation of uncertainty. Journal of Risk and Uncertainty, 5(4), 297–323. DOI: 10.1007/BF00122574
Kizielewicz, B., Shekhovtsov, A., & Sałabun, W. (2023). pymcdm — The universal library for solving multi-criteria decision-making problems. SoftwareX, 22, 101368. DOI: 10.1016/j.softx.2023.101368