Methods · Efficiency
HFEA (Hesitant Fuzzy Envelopment Analysis)
HFEA is a method that, when expert opinions are given as more than one possible score (hesitant), evaluates every option under the weighting most favourable to itself and produces an efficiency score showing whether it is efficient.
Base method's data type: Hesitant
What Is the Method?
HFEA is an efficiency-analysis method for when you have several options (companies, branches, projects) and want to compare their performance across multiple criteria. Unlike TOPSIS, it does not rank by a single distance measure; it asks each option "how efficient can you appear at best, if weighted entirely in your own favour?" and turns the answer into an efficiency score between 0 and 1. Options scoring 1 are considered to be "on the efficient frontier"; those below 1 show how far behind that frontier they fall. Zhou, Chen, Xu and Meng proposed it in 2018 as the form classical data envelopment analysis (DEA) takes when expert opinion is given not as a single number but as several possible values (hesitant).
The Philosophy Behind It
The core idea of classical data envelopment analysis (Charnes, Cooper and Rhodes, 1978) is to evaluate every unit with the weights most favourable to it: whichever criterion a unit is strong on, more weight is given to that criterion, and the condition under which the unit could look its best is sought. HFEA carries the same idea but uses two things in place of inputs and outputs: the mean expert score on each criterion (score, the higher the better) and the inconsistency among these scores (deviation, the lower the better, since agreement among experts increases confidence). For every option, the method searches for the weights that maximise the score relative to the deviation; if this ratio reaches 1 the option is "on the efficient frontier," and if it cannot, the option lies behind that frontier.
This idea carries a philosophical consequence: fair comparison. HFEA imposes no predetermined, externally set weight on any option; each option is evaluated on the dimension where it is strong. If an option turns out inefficient, this means that "even at its best" it falls behind the others; no weighting could rescue it.
How It Works
The method proceeds through six steps; the last is optional.
First, gathering the hesitant assessments. Where more than one expert has scored the same cell separately, these scores are combined into a single hesitant set (a set containing more than one possible value).
Second, computing score and deviation. For every option, the mean (score) and internal inconsistency (deviation) of the hesitant set on each criterion are computed separately.
Third, forming the efficiency ratio. For every option, the ratio of the weighted sum of the criteria's scores to the weighted sum of the criteria's deviations is defined. This ratio measures how efficient that option can appear at best, under weights chosen entirely in its own favour.
Fourth, finding the best weights. For every option separately, the weights that maximise this ratio are sought; the only constraint is that no option's ratio, computed with the same weights, may exceed 1. This is solved by converting it into a mathematically solvable linear programming problem.
Fifth, classification and ranking. Options whose efficiency ratio comes out at 1 are considered to be on the efficient frontier, those below 1 are deemed inefficient, and all are ranked from highest to lowest ratio.
Sixth (optional), an improvement target. For an option found inefficient, the amount by which the score on a given criterion must rise, or the deviation must fall, to reach the efficient frontier can be computed.
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 closer the efficiency score is to 1, the closer the option is to the efficient frontier; a score of 1 does not mean "perfect" but "within this option set, even under the best possible weighting in its own favour, no other option's ratio can exceed 1." A score of 0.875 shows that even under the best weighting, that option falls 12.5 per cent short of the efficient frontier. More than one option can score 1 at the same time; this does not mean all of them are equally good, but that this method cannot distinguish between them. The score cannot be compared with another option set or another analysis, because the efficient frontier is built afresh in every analysis from that analysis's own options.
Thus instead of writing:
"HFEA found the most efficient company"
the report should read:
"With this option set and these criteria, the following companies are on the efficient frontier; if a distinction between them is needed, cross-efficiency analysis (HFPE) is required"
Data Type and Inputs
HFEA works with hesitant data: each option's value on each criterion is not a single number but a set of several possible values (such as scores given separately by more than one expert). DecisionMind holds no extension of this method; the base method works on its own. The method neither requests nor produces weights from outside; each option's efficiency is determined by its own optimisation. All criteria must be benefit-oriented (higher value is better); a cost-oriented criterion must be converted to benefit-oriented by taking its complement (1 minus the value). The number of options must clearly exceed the number of criteria; if the number of options is close to or fewer than the number of criteria, nearly all options come out efficient and the analysis loses its power to discriminate.
When to Use It, When Not To
HFEA is appropriate if you want to compare several options fairly, on their own strengths, without setting weights from outside, and your data has a hesitant structure such as expert opinion. If your data consists of exact numbers and the classical input/output distinction is clear (production volume, cost, and so on), classical data envelopment analysis (CCR, BCC) is sufficient; using this method when there is no hesitation adds unnecessary complexity. If your goal is not merely a ranking but a full distinction among the options on the efficient frontier as well, HFEA alone is not enough.
Efficiency comparison weighted in each option's own favour, data hesitant → HFEA
Data an exact number, classical input/output efficiency → classical DEA (CCR, BCC)
A full distinction is needed among options on the efficient frontier → HFPE (cross-efficiency)
A priority order among criteria is also to be specified → HFPEA
Strengths
HFEA's greatest strength is that it evaluates each option on the criterion where it is strong, without imposing an external weight on any of them; this makes the comparison unbiased. It does not collapse the hesitation in expert opinion (the several possible values) into a single number at an early stage and lose it, but accounts for it as deviation. For options found inefficient, it can show not just a score but also how much improvement is needed, and on which criterion, to reach the efficient frontier; this makes the result actionable.
Weaknesses
HFEA's fundamental limitation is that it inherits a problem from classical data envelopment analysis: if the number of options is low relative to the number of criteria (roughly, if there are not about three options for every criterion), nearly all options come out efficient and the analysis loses its meaning (Banker, Charnes and Cooper, 1984). A second limitation is that more than one option can appear on the efficient frontier at the same time, and the method cannot distinguish between them; this requires a cross-evaluation step such as HFPE. Third, the score-and-deviation calculation collapses all the information in a hesitant set into two numbers; two sets of different structure can give the same score and deviation, in which case the method cannot tell them apart (Xia and Xu, 2011). Fourth, since all criteria must be treated as benefit-oriented, failing to take the correct complement of a cost-oriented criterion leads to a serious error.
Common Mistakes
The most common mistake is treating a cost-oriented criterion directly as benefit-oriented without taking its complement; this can reverse the efficiency ranking. A second mistake is interpreting the fact that nearly everyone comes out efficient, in a small data set where the number of options is close to the number of criteria, as "everyone is genuinely excellent"; this is generally a sign of a small sample. A third mistake is treating more than one option scoring 1 on efficiency as equal in quality; if a distinction is needed among these options, a cross-efficiency step such as HFPE should be applied. The governing principle is this:
An HFEA score is the highest efficiency an option can attain even under the best weights that could favour it; every score below 1 shows that no weighting could rescue that option.
Cases
Each case opens with a decision table, describes in words what the method does to it, and shows how to read the efficiency score. The first case is drawn from the method's founding source. The remaining cases are illustrative constructions.
1. Business: Pre-investment efficiency comparison of four technology companies (Zhou, Chen, Xu and Meng, 2018)
An investment appraisal board will compare four listed companies (y1, y2, y3, y4) on four criteria: market share, team quality, growth prospects and technology fit. More than one expert has scored each criterion separately, so every cell is not a single number but a set of several possible values. All four criteria are benefit-oriented (a higher score is better).
| Company | Market share | Team quality | Growth prospects | Technology fit |
|---|---|---|---|---|
| y1 | 0.2 · 0.5 · 0.8 | 0.1 · 0.6 | 0.5 · 0.9 | 0.2 · 0.8 · 0.9 |
| y2 | 0.4 · 0.8 | 0.32 · 0.45 · 0.7 | 0.4 · 0.8 | 0.1 · 0.4 · 0.6 |
| y3 | 0.6 · 0.8 | 0.25 · 0.4 · 0.55 | 0.25 · 0.4 · 0.55 | 0.4 · 0.5 · 0.7 |
| y4 | 0.1 · 0.5 · 0.7 | 0.3 · 0.8 | 0.5 · 0.9 | 0.2 · 0.8 |
| Direction | higher is better | higher is better | higher is better | higher is better |
The method first computes the mean (score) and internal inconsistency (deviation) of each cell; for example, y1's market-share set has a score of 0.5 and a deviation of 0.2. It then searches, for every company, for the weights that maximise its score relative to its deviation, and computes the efficiency ratio with those weights.
| Company | Efficiency score | Class | Rank |
|---|---|---|---|
| y2 | 1.000 | On the efficient frontier | 1 |
| y3 | 1.000 | On the efficient frontier | 1 |
| y1 | 0.875 | Inefficient | 3 |
| y4 | 0.875 | Inefficient | 3 |
The result reads as follows. y2 and y3, evaluated under the weights most favourable to each of them, reach the efficient frontier; both are considered "first," with no distinction between them since the method places them in the same class. y1 and y4 fall 12.5 per cent short of the frontier even under the best possible weighting; the improvement needed, and on which criterion, can be computed separately for these two companies.
The board hesitates here: both y2 and y3 coming out "first" does not give enough information to prefer one over the other. If a choice between the two is needed, a cross-evaluation (HFPE) should be carried out, showing which company also looks better from the others' perspective, not only its own.
In the report: "In the efficiency comparison of the four companies, y2 and y3 are on the efficient frontier, while y1 and y4 fall 12.5 per cent short of it; if a choice between y2 and y3 is required, cross-efficiency analysis should be applied."
Source: Zhou, Chen, Xu and Meng (2018), Chapter 4, Example 4.1; the figures are taken from Tables 4.1–4.4 of Zhou and Xu's (2020) book. The efficiency scores were recomputed with the DecisionMind engine (using a linear programming solver) while preparing this card and matched the record in the manifest (the kernel's golden test, tolerance 0.001). The book's printed page shows a value of 0.8748 for y1 and y4; this stems from the book using a rounded figure (0.633) for criterion x4, while the calculation with the exact fraction (19/30) gives 0.875 (7/8).
2. Education: Efficiency of the academic support programme at three secondary schools
An expert team from a district education authority wants to compare the efficiency of the academic support programme run at three secondary schools. The criteria include student participation rate, teacher satisfaction, parental feedback score, and progress on assessment tests; for each criterion, several observers who visited the schools gave separate scores.
The method computes the efficiency ratio for each school under the weights most favourable to it. Suppose the result finds one school on the efficient frontier and the other two clearly behind it.
The team hesitates here: which criterion the inefficient schools are falling behind on needs separate examination; a low score alone does not mean "a bad programme" — factors not reflected in the criteria, such as differences in student profile or resources, may also be at play. The efficiency score is only a comparison among these three schools; it is not a measure of district-wide achievement.
In the report: "When the efficiency of the academic support programme is compared across the three schools, one school is on the efficient frontier and the other two fall behind it; improvement targets by criterion should be derived separately for the remaining schools."
3. Logistics: Operational efficiency of four distribution depots
A courier company's operations department wants to compare the operational performance of four regional depots. The criteria include on-time delivery rate, warehouse capacity utilisation, customer satisfaction score, and throughput per employee; each criterion has been recorded as hesitant, with separate scores given by field auditors.
The method computes the efficiency ratio for each depot under the weights most favourable to it. Suppose the result finds two depots on the efficient frontier and two behind it.
Management hesitates here: two depots coming out on the efficient frontier at the same time does not mean the two are operationally identical; one may be strong on delivery speed, the other on capacity utilisation. Which one to adopt as a model must be answered together with which criterion is more of a strategic priority for the company, not by the efficiency score alone.
In the report: "In the operational efficiency comparison of the four depots, two are on the efficient frontier and two fall behind it; a further cross-evaluation should be carried out to select a best-practice example among the efficient depots."
4. What Not to Do
Three concrete errors, seen against the table in Case 1, are as follows. The first is seeing y2 and y3 both score 1.000 and saying "y2 is more efficient than y3 because it was listed first in the ranking"; the two are in the same class, and the method gives no distinction between them. The second is interpreting y1's 0.875 score as "87.5 per cent successful" as a general achievement percentage; this score only shows relative position among these four companies. The third is that, had one of the table's criteria been cost-oriented (for instance, "unit cost") and processed directly without taking its complement, the highest-cost company could have wrongly appeared the most efficient.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/hfea
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
Zhou, W., & Xu, Z. (2020). Qualitative Investment Decision-Making Methods under Hesitant Fuzzy Environments. Studies in Fuzziness and Soft Computing, Vol. 376. Springer, Cham. DOI: 10.1007/978-3-030-11349-0
Charnes, A., Cooper, W. W., & Rhodes, E. (1978). Measuring the efficiency of decision making units. European Journal of Operational Research, 2(6), 429–444. DOI: 10.1016/0377-2217(78)90138-8
Banker, R. D., Charnes, A., & Cooper, W. W. (1984). Some models for estimating technical and scale inefficiencies in data envelopment analysis. Management Science, 30(9), 1078–1092. DOI: 10.1287/mnsc.30.9.1078
Xia, M. M., & Xu, Z. S. (2011). Hesitant fuzzy information aggregation in decision making. International Journal of Approximate Reasoning, 52(3), 395–407. DOI: 10.1016/j.ijar.2010.09.002