Methods · Ranking
PHFS-HVaR (Hesitant Value-at-Risk under Probabilistic Hesitant Fuzzy Sets)
PHFS-HVaR is a risk measure that, when an alternative's future is expressed through several possible values and their probability of occurring, finds the worst boundary that stays below a chosen confidence level.
Base method's data type: Hesitant
What Is the Method?
PHFS-HVaR is a risk-focused ranking method used when you hold, for an alternative's performance, not a single definite figure but several possible values, each with its own probability of occurring. Its output is the boundary value that the alternative is "guaranteed to stay below with this probability" at a chosen confidence level (X); alternatives are ranked by this boundary. Zhou and Xu proposed it in 2017, from the observation that classical average-based comparisons can conceal poor scenarios.
The Philosophy Behind It
PHFS-HVaR's underlying idea is to carry the Value-at-Risk concept from finance into decision analysis. Even where an alternative's average performance looks good, this average can conceal a low-probability but very poor scenario. Rather than asking "what is the average," PHFS-HVaR asks "what is the worst case guaranteed under a given probability"; it finds the point at which probabilities, accumulated starting from the lowest values, reach that threshold, and takes the value at that point as the boundary.
This idea carries a philosophical consequence: the method reflects a risk-averse decision stance. PHFS-HVaR does not look at an optimistic average but at the boundary of the poor tail; two alternatives with the same average return can therefore produce different PHFS-HVaR results if their poor-scenario distributions differ.
How It Works
The method proceeds through four steps.
First, gathering the possible values. For every alternative, the possible values and their probabilities of occurring are sorted from smallest to largest. A confidence level (X) is set; this answers the question "what percentage of probability's worst case do we want to see."
Second, cumulative probability. Starting from the smallest value, probabilities are accumulated over the sorted values.
Third, finding the boundary. The value at which cumulative probability first crosses, or exactly matches, the X threshold is found. This value is that alternative's PHFS-HVaR.
Fourth, ranking. Alternatives are ranked by this boundary value; for a benefit-direction measure (such as return), a higher boundary is safer or better, while for a loss-direction measure a lower boundary is better. Where alternatives' boundary values come out equal, PHFS-HVaR is not discriminating, and EHVaR should then be used.
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
PHFS-HVaR is a point estimate; it states only the boundary at the chosen confidence level and gives no information about how poor the scenarios below that boundary could be. Two alternatives can have an equal PHFS-HVaR without their entire poor-scenario distributions being the same; one may have few scenarios just below the boundary while the other has far poorer ones.
The confidence level (X) must be stated in the report; as X changes the boundary changes too, and different X values can give different rankings.
Thus instead of writing:
"PHFS-HVaR proved with certainty that this alternative is safer"
the report should read:
"At the twenty per cent probability threshold X, this alternative's guaranteed boundary is this figure; this boundary does not show the severity of the scenarios below it"
Data Type and Inputs
PHFS-HVaR works with a probabilistic form of hesitant data: for every alternative, several possible values are given not merely as "possible" but each with its own probability of occurring, summing to 1. DecisionMind holds no extension of this base method.
You need: a set of possible values for every alternative and each value's probability of occurring (the probabilities must sum to 1); a confidence level (X); and whether the values represent a gain or a loss. PHFS-HVaR does not combine several criteria in the classical sense; it processes the possible scenarios of a single measurement dimension (such as rate of return). Where several criteria exist, a separate PHFS-HVaR is computed for each, or the criteria are combined beforehand.
When to Use It, When Not To
PHFS-HVaR is a sound choice if you hold several scenarios for an alternative's performance and the probability of each (expert estimates, historical data distributions, scenario analysis), and you particularly want a cautious decision against poor scenarios.
It should not be used where you hold only "possible" values whose probability of occurring is unknown; PHFS-HVaR requires probabilities and cannot be applied to hesitant data without them. Where the boundary values PHFS-HVaR produces come out equal, the method is also not discriminating.
Several probabilistic scenarios, particular interest in the poor tail → PHFS-HVaR
PHFS-HVaR values come out equal, a more discriminating risk measure is needed → PHFS-EHVaR
Only possible values exist, probability unknown → ordinary hesitant methods
Average performance is enough, no particular interest in the poor tail → expected value or classical weighted methods
Strengths
PHFS-HVaR's greatest strength is its direct interpretability. The statement "this is the worst case guaranteed under this probability" is easy to convey to a risk-averse decision-maker, and is familiar to anyone acquainted with the Value-at-Risk concept in finance. Its calculation is simple; it only requires finding the point at which cumulative probability crosses a threshold.
Weaknesses
Its limitations stem from its point-estimate structure. PHFS-HVaR disregards all information below the boundary entirely; two very different scenario distributions can give the same boundary value, and the method cannot distinguish between them (Zhou and Xu, 2020, Example 6.1). The choice of confidence level (X) strongly affects the result, and this choice is left largely to the decision-maker. Because the method was proposed in 2017, its literature is limited and it does not yet carry a broad body of comparison.
Common Mistakes
The most common mistake is sharing a PHFS-HVaR result without stating the confidence level (X); different X values can produce different rankings on the same data.
A second mistake is treating alternatives with equal PHFS-HVaR as "equally good" and never checking EHVaR; equality usually shows a situation the method cannot distinguish, not that the alternatives are genuinely equal. A third mistake is inventing probabilities for data where only possible values are known but probabilities are not, and applying PHFS-HVaR anyway; probability data must come from a genuine source, such as historical frequency or expert estimation.
The governing principle is this:
PHFS-HVaR shows only a boundary at the chosen confidence level; a PHFS-HVaR result presented without stating this level in the report, and without discussing the severity of the scenarios below the boundary, is incomplete.
Cases
Each case opens with possible values and probabilities, describes in words what the method does to them, and shows how to read the result. The first case is drawn from the method's founding source; its figures are the book's own.
1. Finance: A risk-focused choice between two stocks (Zhou and Xu, 2020)
An investor will choose between two stocks. Each stock's possible rates of return and the probability of each rate occurring have been set from past performance and expert opinion. The investor wants to see what happens in the worst twenty per cent probability band (X = 0.20).
| A1 stock: rate of return | Probability |
|---|---|
| 0.15 | 0.20 |
| 0.35 | 0.50 |
| 0.40 | 0.15 |
| 0.50 | 0.15 |
| A2 stock: rate of return | Probability |
|---|---|
| 0.10 | 0.05 |
| 0.15 | 0.15 |
| 0.30 | 0.40 |
| 0.45 | 0.20 |
| 0.55 | 0.20 |
The method sorts each stock's possible returns from smallest to largest and accumulates the probabilities. For A1, the first value's (0.15) probability already reaches 0.20, so the boundary is 0.15 directly. For A2, the first two values' (0.10 and 0.15) probabilities sum to exactly 0.20, so the boundary is the second value, 0.15.
| Stock | PHFS-HVaR (X=0.20) |
|---|---|
| A1 | 0.15 |
| A2 | 0.15 |
The result reads as follows. Both stocks guarantee the same return boundary, 0.15, in the worst twenty per cent probability band. PHFS-HVaR cannot distinguish between these two stocks.
The investor hesitates here: even though the boundary values are equal, the two stocks' poor-scenario distributions are not the same. A1's worst scenario is concentrated in a single value (0.15, with probability 0.20), while A2's worst scenario is spread across two different values (0.10 and 0.15), one of which (0.10) is lower than A1's worst value. PHFS-HVaR cannot see this difference; this is exactly the problem the EHVaR method aims to solve.
In the report: "At the confidence level X=0.20, both stocks give the same PHFS-HVaR boundary (0.15); this equality does not mean the stocks' poor-scenario distributions are the same, and they have been assessed further with PHFS-EHVaR."
Source: Zhou and Xu (2020), Chapter 6, §6.2.1–6.2.2, Example 6.2. The values are the book's own; this case serves as the validation example for DecisionMind's PHFS-HVaR engine, and the engine reproduces the same result.
2. Water Management: Choosing a dam operating scenario
A water authority will choose between two dam-operation policies. For each policy, the possible values of next year's minimum reservoir level and their probability of occurring have been derived from hydrological models. The authority wants to see what the reservoir level will be in the worst fifteen per cent probability band.
The method sorts each policy's possible reservoir levels, accumulates the probabilities and finds the boundary. Suppose both policies' guaranteed minimum-reservoir boundary at this threshold comes out the same.
The authority hesitates here: even though the boundaries are equal, one policy's worst scenario may correspond to a much lower reservoir level, albeit less probable. The authority should consider computing EHVaR or examining the full probability distribution to see this distinction.
In the report: "At the chosen confidence level, both policies give the same minimum-reservoir boundary; this equality alone is not sufficient, and the distribution of poor scenarios should be examined further."
3. Election Logistics: Choosing a vote-count centre capacity plan
An election board will choose between two vote-count centre capacity plans. For each plan, the possible values of count-completion time on a busy election day and their probability of occurring have been estimated from past elections. The board wants to know how long the count will take in the worst ten per cent probability band.
The method sorts each plan's possible completion times (duration being a loss criterion, a short time is good) and finds the boundary. Suppose one plan guarantees a shorter worst-case time at this threshold and comes out ahead.
The board hesitates here: this boundary is valid only at the chosen probability threshold; if the threshold is changed, lowered to five per cent, for example, which plan comes out ahead may change. The board should clarify which threshold is operationally meaningful.
In the report: "In the worst ten per cent probability band, the first plan guarantees a shorter completion time; this result depends on the chosen probability threshold."
4. What Not to Do
In the same stock example, interpreting A1 and A2's equal PHFS-HVaR (0.15) as "the two stocks are equally risky" is wrong; equality only shows that the method cannot distinguish these two stocks at this boundary. A second error is reporting only "PHFS-HVaR is 0.15" without ever stating the confidence level (X=0.20); the boundary changes if X changes. A third error is entering probabilities that do not sum to 1; PHFS-HVaR requires the probabilities to form a valid distribution.
Sources
For the formulas behind each step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/phfs-hvar
Zhou, W., & Xu, Z. (2017). Expected hesitant VaR for tail decision making under probabilistic hesitant fuzzy environment. Applied Soft Computing, 60, 297–311. DOI: 10.1016/j.asoc.2017.06.057
Zhou, W., & Xu, Z. (2020). Qualitative Investment Decision-Making Methods under Hesitant Fuzzy Environments. Studies in Fuzziness and Soft Computing, Vol. 376. Springer, Cham, Chapter 6. DOI: 10.1007/978-3-030-11349-0
Xu, Z., & Zhou, W. (2017). Consensus building with a group of decision makers under the hesitant probabilistic fuzzy environment. Fuzzy Optimization and Decision Making, 16(4), 481–503. DOI: 10.1007/s10700-016-9257-5
Zhou, W., Chen, J., Xu, Z. S., & Meng, S. (2018). Hesitant fuzzy preference envelopment analysis and alternative improvement. Information Sciences, 465, 105–117. DOI: 10.1016/j.ins.2018.07.002