Methods · Ranking
DNMA (Double Normalization-based Multiple Aggregation)
DNMA does not rely on a single aggregation logic (sum alone, or product alone). It scores the same data by three different methods (weighted sum, weighted product, closeness to the ideal), then produces a single combined score by rewarding the consistency of both the scores and the ranks.
Base method's data type: Classical
What Is the Method?
DNMA is a ranking method that arranges alternatives into a single order once you hold a decision table filled with numbers. Its output is a single score for each alternative: this score is built from the combination of three different aggregation logics, and alternatives are ranked by this score. Liao and Wu proposed the method in 2020. It arose from a concern: in multi-expert, multi-criteria decision problems, a decision-maker's choice of a single aggregation method (weighted sum alone, or weighted product alone) can change the result. DNMA produces no weights; it takes them from outside.
The Philosophy Behind It
Multi-criteria ranking methods share another known weakness. Whichever aggregation logic is chosen, weighted sum, weighted product, or closeness to the ideal, different alternatives can come out ahead. The reason is this: a weighted sum readily compensates for a weakness on one criterion, whereas a weighted product is less tolerant of an extremely low value. DNMA's philosophical move is this: rather than giving a single answer to "which aggregation is correct", the method calculates all three at once and trusts none of them fully. DNMA calculates three separate measures for every alternative: a weighted sum (WSM, fully compensatory), a weighted product (WPM, less tolerant of low values), and a third measure based on closeness-to-the-ideal logic.
The second philosophical move is seen in how DNMA combines these three measures. DNMA does not simply average the three scores; it extracts both a score and a rank from each aggregation. It builds the combined score to reward alternatives that are "scored highly AND consistently ranked well across all three methods". If an alternative ranks well under only one aggregation method but poorly under the other two, this inconsistency lowers the combined score. The philosophical consequence is this: DNMA is a ranking approach that hands over trust in any single aggregation model to the mutual confirmation of several models, a kind of "cross-method consensus".
How It Works
The method proceeds through four steps.
First, two separate normalisations. DNMA equalises every column of the decision table in two different ways. The first is a vector normalisation that takes direction into account; for cost criteria this operation is reversed. The second is a linear-maximum normalisation, also accounting for direction (relative to the column's largest value for a benefit criterion, or relative to the ratio of the column's smallest value for a cost criterion). These two differently normalised tables form the basis for the three aggregations in the next step.
Second, three sub-utility calculations. From the normalised tables, DNMA calculates three separate aggregations: a fully compensatory weighted sum (WSM-like, the "complete" model), a weighted product less tolerant of compensation (WPM-like, the "incomplete" model), and a third measure based on closeness-to-the-ideal logic (TOPSIS-like). Every alternative receives a separate score under each of these three models.
Third, ranks and deviation measures. DNMA extracts each alternative's rank within each of the three models from that model's own scores, and also calculates how much the scores within each model deviate from one another. DNMA thus holds both three scores and three ranks together for every alternative.
Fourth, the combined score. DNMA builds a single combined score by subtracting the weighted sum of the normalised squared ranks across the three models from the weighted sum of the normalised squared scores across the three models. This score jointly rewards a high score AND low (good) rank consistency. DNMA ranks alternatives by this combined score, from highest to lowest.
You can find the formulas for each step, the intermediate tables and the citation formats on the DecisionMind method page; this card carries no formulas.
How to Read the Output
DNMA's combined score is a figure that jointly summarises the magnitude of an alternative's scores under three different aggregation logics and the consistency of its ranks; a higher score is better. Unlike TOPSIS's closeness score, this figure does not arise from a single distance measure, but from how much three separate models confirm one another. If an alternative's score is high, this does not just mean "it came out well under one model"; it means "it was consistently ranked well under more than one aggregation logic". This is DNMA's central claim to reliability.
The score itself is neither a percentage nor a probability, and it can come out negative. If an alternative's rank inconsistency is penalised more heavily than the magnitude of its scores, the score comes out negative. A negative score does not mean "failure"; it only shows the relatively weakest position among these particular alternatives. The score cannot be compared directly with a score calculated with a different set of alternatives or different weights.
Thus instead of writing:
"By the DNMA score, A2's performance is 1.0, meaning perfect"
it is correct to write:
"A2 is the alternative that all three aggregation models consistently place at the top; this combined score only shows an order among these three alternatives, not an absolute percentage of success"
Data Type and Inputs
DNMA works with crisp data: a single number per cell. You need: alternatives in rows, criteria in columns, one number per cell; direction information for each criterion; weights that sum to 1. Optionally, additional coefficients can be defined specifying how much weight is given to the score and rank components of the three aggregation models; if unspecified, DecisionMind gives all three equal weight. DNMA produces no weights, taking them from outside; you can obtain these weights from methods such as AHP, BWM, Entropy or CRITIC. DecisionMind holds four DNMA members alongside the base method (including fuzzy, negative and positive extensions). A minimum of two alternatives and two criteria is required; three to twelve criteria is recommended. If every value in a criterion column is equal, that is, the largest and smallest values coincide, linear normalisation becomes undefined. Such constant columns should be avoided.
When to Use It, When Not To
If your criteria can be measured numerically, DNMA is a suitable choice. It is especially useful if, instead of relying on a single aggregation logic (sum alone, or product alone, or closeness to the ideal alone), you want a result confirmed by all three together. It typically finds use in multi-expert, multi-criteria evaluations and in supplier or alternative selection.
There are some situations where you should not use DNMA. Do not use it where simplicity and the traceability of a single calculation logic matter; combining three separate models is a longer method to explain than a single one. Do not use DNMA if a criterion column is constant, that is, shows no variation, and linear normalisation would be undefined. Nor is DNMA suitable if no compromise is accepted on one criterion, that is, if veto logic is required.
If you do not want to rely on a single aggregation logic and want the consistency of more than one model → DNMA
If a simple, single-aggregation (sum only) ranking suffices → SAW, TOPSIS
If explanatory simplicity matters (a logic explainable in one step is wanted) → SAW
If a criterion column is constant (the same value across all alternatives) → remove this criterion first or choose a different form of normalisation
If no compromise is accepted on one criterion → the ELECTRE family
Strengths
DNMA's greatest strength is this: it does not depend on a single aggregation logic (sum alone or product alone). It uses three different logics together and looks for them to confirm one another. This approach provides a safeguard against the arbitrariness of choosing a single method (Liao and Wu, 2020). Second, DNMA looks not only at the magnitude of the score but also at rank consistency. This means an alternative cannot dominate the result on the strength of a single model where it happened to do well by chance. Third, researchers have extended the method to uncertain data types such as fuzzy, intuitionistic fuzzy and probabilistic linguistic since its publication (Liao et al., 2019; Liao et al., 2024). This shows the design is flexible. Fourth, Liao and Wu designed DNMA specifically for multi-expert evaluation settings. The method directly answers the need to combine multiple viewpoints in that scenario.
Weaknesses
Its limitations come from the same design. First, explaining three separate aggregation models and the rank-consistency penalty together requires a longer explanation than single-model methods such as SAW or TOPSIS. Answering the decision-maker's question of "why did this order come out" takes more steps. Second, the relative weights of the combined score's squared-score and squared-rank terms lie in the analyst's hands. These weights can be distributed equally or unequally across the three models, and this choice can affect the result. Third, if a criterion column is constant, linear normalisation remains undefined; this is a constraint that must be checked separately during data preparation. Fourth, because it includes a fully compensatory (WSM) component, DNMA is ultimately a partly compensatory method as well. It has no veto logic; a very poor value on one criterion does not entirely prevent an alternative from looking good on the other measures.
Common Mistakes
The most common mistake is this: the user ignores the fact that DNMA calculates three separate aggregation models and interprets the result as a single "closeness-to-ideal score" (as in TOPSIS). Yet DNMA's score arises from the combination of three models; the analyst must state this explicitly in the report. A second mistake is this: the user, not knowing the combined score can come out negative, mistakes a negative value for a calculation error. Yet a negative score only shows a relatively weak position. A third mistake is this: the user marks a criterion's direction (benefit/cost) incorrectly. This error affects both the vector and the linear normalisation, and hence all three models. A fourth mistake is this: the user includes a criterion column in the analysis without noticing it is constant. In that case, linear normalisation remains undefined. A fifth mistake is this: the user presents the result without reporting the weights given to the three models' score and rank components (equal or unequal). Yet these weights are genuine inputs that affect the result.
The governing principle is this:
DNMA's combined score is a summary of the score and rank consistency of three different aggregation models; if an alternative looks good under only one model, this is exactly the kind of fragility DNMA is designed to catch, and the report must show it.
Cases
Each case opens with a decision table, describes in words what the method does to it, and shows how to read the result. The first case is an illustrative example drawn from DecisionMind's own validation record; the others are illustrative constructions.
1. Human Resources: A company's choice of performance-review system supplier (illustrative example)
A company's HR department will choose among three performance-review software proposals. There are three criteria: a user-satisfaction score and a reporting-flexibility score ("higher is better"), and an annual licence-cost index ("lower is better"). The department has given satisfaction a weight of 0.40, flexibility 0.35, cost 0.25, and has assigned equal weight (one third each) to the score and rank components of the three aggregation models.
| Proposal | User satisfaction | Reporting flexibility | Cost index |
|---|---|---|---|
| Y1 | 3 | 5 | 4 |
| Y2 | 5 | 3 | 2 |
| Y3 | 4 | 4 | 3 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method normalises every column in two different ways (vector and linear-maximum). From these two tables it calculates three separate aggregation scores (weighted sum, weighted product, a closeness-to-ideal-like measure). It then extracts the rank under each model and builds a single score combining the magnitude of the scores with rank consistency.
| Proposal | DNMA score | Rank |
|---|---|---|
| Y2 | 1.000 | 1 |
| Y3 | 0.569 | 2 |
| Y1 | -0.322 | 3 |
The result reads as follows. Y2 is the proposal that all three aggregation models (weighted sum, weighted product, closeness to the ideal) consistently place at or near the top. Its lowest cost and highest satisfaction support this consistency. Y1, by contrast, received a negative score. Despite being the best on reporting flexibility, it remained weak on satisfaction and cost; this weakness produced a relatively poor rank under all three models and outweighed the magnitude of its score.
The department has one hesitation: this ranking is sensitive to the weight given to the reporting-flexibility criterion. If the weights are shifted so that flexibility rises from 0.35 to about 0.53, with the other two weights lowered proportionally (satisfaction ~0.29, cost ~0.18), Y1 moves ahead (Y1: 0.656, Y2: 0.484). As long as the weight stays below 0.525 (for example, at 0.50 Y2 is still ahead at 1.00), Y2 remains first. This shows how sensitive the combined score can be to criterion weights.
In the report: "With the given weights and equal model weights, Y2 is consistently the best proposal under all three aggregation models (score 1.00); when the reporting-flexibility weight is raised to 0.53, Y1 moves ahead, so the ranking is sensitive to this weight."
Source: illustrative example; a DecisionMind validation case. The calculation logic rests on Liao and Wu's (2020) DNMA method, but this table and these figures are not taken from the paper.
2. Construction: A municipality's infrastructure contractor ranking
A municipality will produce a full ranking among three construction-contractor proposals. There are three criteria: a technical-competence score and a workplace-safety-record score ("higher is better"), and the bid price ("lower is better"). The tender committee has given technical competence the highest weight. It has also assigned a somewhat greater weight to the rank component of the three aggregation models than to the score component, because it found the criterion of "being consistently good" important.
The method scores and ranks the three proposals separately under three models and builds the combined score. Suppose the result places first a proposal that is not the best on any single criterion but remains steadily second under all three models. A proposal that is very good on one criterion but very poor on another falls behind because of its inconsistency across models.
The committee has one hesitation: the extra weight given to the rank component has favoured a "steady average" proposal over a "brilliant but unbalanced" one. If the committee made this choice deliberately, this justification should be stated explicitly in the report; perhaps there have been problems with unbalanced contractors in the past. Otherwise, the question "why isn't the most technically competent proposal first" arrives as a legitimate objection.
In the report: "Because of the extra weight given to rank consistency, the proposal that stayed steadily second under all three models has come out ahead; this choice is a deliberate weighting against past fluctuations in contractor performance."
3. Forestry: A forest management directorate's ranking of management-plan options
A forest management directorate will rank three forest management plan options. There are three criteria: a sustainable-harvest-volume score and a biodiversity-conservation score ("higher is better"), and annual implementation cost ("lower is better"). The planning team considered the three criteria to represent different stakeholder groups (economic, ecological, financial). It has therefore assigned a somewhat greater weight to the weighted-sum and closeness-to-ideal components of the three aggregation models than to the weighted-product component.
The method ranks the three plans. Suppose the result places first a plan with a high biodiversity-conservation score but also a high cost. It places last a plan with a high harvest volume but a low conservation score.
The team has one hesitation: the weighted-product component is less tolerant of low values. Had this component been given more weight, the plan with the low conservation score could have fallen even further behind. Or, conversely, a balanced plan that stands out on no single criterion could have moved ahead. The team should explain in the report which stakeholder priority (economic or ecological) the weights given to the three models reflect.
In the report: "With the extra weight given to the weighted-sum and closeness-to-ideal components, the plan with a high biodiversity-conservation score has come out ahead; how the ranking would change if the weighted-product component were emphasised instead should be shown in a separate sensitivity analysis."
4. What Not to Do
In the performance-review software example, had the cost index been marked "higher is better", a total would have been built in favour of the most expensive proposal and the ranking would have become meaningless. The second error is this: someone mistakes Y1's negative score of -0.322 for a calculation error and says "the method did not work". Yet a negative score is a normal output in DNMA and only shows a relatively weak position. The third error is this: someone summarises the result in a single sentence as "by DNMA, Y2 is best" without ever mentioning the existence of the three aggregation models and the rank-consistency penalty. This summary does not explain why the score came out this way and prevents the reader from questioning the result.
Extensions: for different data types
DNMA has 3 extensions in the library. Same decision logic, different data type: if your data is not a classical number, read the relevant data type card, then open that member.
Sources
For the formulas behind each step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/dnma
Liao, H., & Wu, X. (2020). DNMA: A double normalization-based multiple aggregation method for multi-expert multi-criteria decision making. Omega, 94, 102058. DOI: 10.1016/j.omega.2019.04.001
Liao, H., Long, Y., Tang, M., Streimikiene, D., & Lev, B. (2019). Early lung cancer screening using double normalization-based multi-aggregation (DNMA) and Delphi methods with hesitant fuzzy information. Computers & Industrial Engineering, 136, 453–463. DOI: 10.1016/j.cie.2019.07.047
Liao, H., Xiao, Y., Wu, X., & Bausys, R. (2024). Z-DNMASort: A double normalization-based multiple aggregation sorting method with Z-numbers for multi-criterion sorting problems. Information Sciences, 653, 119782. DOI: 10.1016/j.ins.2023.119782