Methods · Ranking
OCRA (Operational Competitiveness Rating Analysis)
A method that separately sums the alternatives' relative shortfall on input (cost) criteria and their relative superiority on output (benefit) criteria, then combines the two at a common reference point to produce a ranking.
Base method's data type: Classical
What Is the Method?
OCRA is a ranking method that arranges alternatives into a single order once you hold a decision table divisible into inputs and outputs; input criteria are "lower is better" criteria such as cost and time, output criteria are "higher is better" criteria such as quality and capacity. Its output is a preference score for every alternative and a descending order by that score. The least competitive alternative always scores 0; the others carry a number showing how far ahead of it they are. It does not sort alternatives into groups, nor does it produce criterion weights; it takes them from outside. Parkan proposed the method in 1994 to compare the operational competitiveness of production units, and the name (Operational Competitiveness Rating Analysis) comes from this. Later applications have carried it into fields such as supplier evaluation, manufacturing-process selection and staff assessment.
The Philosophy Behind It
The idea behind OCRA is to split the criteria into two separate sets: input criteria, that is, "lower is better" criteria such as cost, time and resource consumption, and output criteria, that is, "higher is better" criteria such as quality, capacity and gain. The method first sums each set on its own. On one side stands the question "how far behind the best is this alternative on the input side," on the other "how far ahead of the worst is it on the output side." It then places these two separate stories onto a common zero point and adds them together. A production unit's competitiveness is the combination of how well it manages its inputs and how well it produces its outputs.
Philosophically this sits in the same family as TOPSIS and SAW: OCRA is compensatory, a weakness on one criterion can be closed by strength on another. Its difference is that it measures distance not against two hypothetical points (ideal/anti-ideal) but against the best and worst references within the input and output sets themselves; this measurement comes out directly as a percentage shortfall or superiority.
How It Works
It proceeds through three steps.
First, measuring the shortfall on input (cost) criteria. For every "lower is better" criterion, it is computed what percentage worse an alternative's value is than that criterion's best (lowest) value. This ratio is multiplied by the criterion's weight and summed across all input criteria. The ratio is taken against the best value, not against the range's width; the result reads directly as "how far behind the best, in percentage terms."
Second, measuring the superiority on output (benefit) criteria. For every "higher is better" criterion, it is computed what percentage better an alternative's value is than that criterion's worst value; this is weighted and summed.
Third, combining the two sides at a common zero point. The input totals are zeroed against their own worst, and the output totals against their own worst; the worst-performing alternative scores 0 on both axes. These two zeroed values are summed, and finally the total is re-zeroed against its own worst. As a result the least competitive alternative scores exactly 0. The others carry a score showing how far ahead of this zero point they are, and the alternatives are ranked from highest to lowest by this score.
The formulas behind each step, the intermediate tables and citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The preference score says only how far ahead an alternative is of the least competitive alternative in this table; it says nothing else. A score of 0.28 does not mean "28 per cent better" or an absolute performance level; it is only a relative difference within this alternative set. The lowest score (0) does not mean "poor," it means "least competitive in this set." Scores have no upper bound and cannot be compared with the scores from a different analysis, because the reference points, that is, the best and worst of the input and output sets, are built in every analysis from that analysis's own alternatives.
Therefore, instead of writing:
"OCRA found the most competitive alternative"
the report should read:
"With these weights and this alternative set, the alternative with the highest preference score is this one; the score shows only its relative superiority within this set"
Data Type and Inputs
Classical OCRA works with crisp data: one number per cell. DecisionMind holds two extensions alongside the base method (FUZZY-OCRA, P-OCRA), giving three OCRA members in total. Which extension fits is explained on the relevant data-type cards if your data is approximate or uncertain, drawn from expert judgement.
You need alternatives in rows, criteria in columns, one number per cell, no empty cells; whether each criterion is an input (cost, lower is better) or an output (benefit, higher is better); and criterion weights that sum to 1. OCRA does not produce weights, it asks for them. A minimum of two alternatives and two criteria is required; three to twelve criteria work comfortably, and there is no upper limit on the number of alternatives. If all the criteria are inputs, or all outputs, the method's two-sided structure collapses to one side. For example, with no input (cost) criterion at all, the input total comes out zero for everyone and the final score reduces to the output ranking alone; the same happens in reverse if every criterion is an input.
When to Use It, When Not To
If your criteria can be clearly split into inputs (cost/resource consumption) and outputs (gain/performance), your table is fully populated, and you accept that a weakness on one criterion can be compensated on another, OCRA is a natural choice. Its typical territory is supplier and process evaluation, manufacturing/processing-method selection, and staff and performance assessment.
There are two cases where it should not be used. The first follows from its philosophy: if you accept no compromise on one criterion, for instance if falling below a safety threshold is never acceptable, you must screen first and rank afterwards. The second follows from its structure: if all your criteria are inputs, or all outputs, none of OCRA's two-sided structure contributes anything; in that case a one-sided total weighted score method, such as SAW, works more directly.
Criteria split into inputs/outputs, compensation accepted, a compact calculation → OCRA
Same idea, but distance to an ideal and anti-ideal point is wanted → TOPSIS
All criteria run in one direction (all benefit or all cost) → SAW
Not "the best" but "the compromise limiting the greatest regret" → VIKOR
No compromise on one criterion, sub-threshold alternatives must be screened out → screening first, then ranking
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective); Entropy, CRITIC (objective)
Strengths
OCRA's advantage is that it treats input and output criteria separately, combining them only at the end. This allows the question "how far behind are we on the cost side, how far ahead on the benefit side" to be answered separately. The calculation is simple and can be followed by hand on the table; it needs no two hypothetical reference points, as TOPSIS does, nor an additional balancing parameter, as VIKOR does. Fixing the worst alternative at zero makes the scores easier to interpret.
Weaknesses
Its limitations arise from its structure. Wang (2006) showed that OCRA's original form of normalisation, dividing by the best or worst value, can be sensitive to the scale of measurement and can lead to inconsistent rankings on some tables, and proposed an alternative normalisation. Second, where there are no input criteria at all, or conversely all criteria are inputs, the method collapses to a one-sided total score, and OCRA's central idea, a two-sided comparison, is disabled. Third, like TOPSIS, it carries a full-compensation assumption: a serious weakness on one criterion can be papered over by others. Fourth, the quality of the weights lies outside the method itself; a flawless calculation built on poor weights still gives a poor ranking. Fifth, its comparative and critical literature is not as broad as that of TOPSIS or SAW; its applied examples remain more limited (Madic, Petkovic and Radovanovic, 2015).
Common Mistakes
The most common mistake is marking which criterion is an input (cost) and which is an output (benefit) the wrong way round; this reverses the entire ranking. A second mistake is putting all the criteria into a single set, only inputs or only outputs, and still choosing OCRA. In that case none of the method's two-sided structure contributes anything, and a simpler method (SAW) gives the same result. A third mistake is reading the preference score as an absolute performance percentage and comparing scores from different analyses. A fourth mistake is assigning equal weights without justification. A fifth mistake is adding an alternative once the analysis is finished and being surprised that the reference points (the group's own best/worst) have shifted.
The governing principle is this:
An OCRA score is a consistent summary of the chosen input/output split, the weights and the alternative set; if the input/output split or the weights are contested, the score 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. The first case is DecisionMind's validation example; the figures are taken from the manifest and the engine produces the same result. The remaining cases are illustrative constructions.
1. Illustrative example: Three alternatives, three criteria (DecisionMind validation example)
This example is not a literature case; it is a small table built to make the method's steps traceable by hand and used to validate DecisionMind's OCRA engine. Three alternatives are evaluated on three criteria; the first two criteria are inputs ("lower is better"), the third is an output ("higher is better").
| Alternative | C1 (input) | C2 (input) | C3 (output) |
|---|---|---|---|
| A1 | 3 | 5 | 4 |
| A2 | 5 | 3 | 2 |
| A3 | 4 | 4 | 3 |
| Direction | lower is better | lower is better | higher is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method first computes, for the two input criteria, what percentage behind the best (lowest value) each alternative falls, weighting and summing this. It then computes, for the single output criterion, what percentage ahead of the worst each alternative stands, weighting this too. Finally it combines the two totals at a common zero point.
| Alternative | Preference score | Order |
|---|---|---|
| A1 | 0.2833 | 1 |
| A3 | 0.1417 | 2 |
| A2 | 0.0000 | 3 |
The result reads as follows. A2, being worst on C1 (the most expensive input) and weakest on C3 (the lowest output), forms the zero reference. A1, being best on C1 and best on C3, though worst only on C2, comes out ahead overall: its superiority on two criteria more than compensates for its weakness on the one. A3 sits at a middling level on all three criteria and remains second.
The decision-maker's hesitation: this order is fairly robust. A1 stays first even if C2's weight is raised from 0.35 to about 0.53, with the other two weights lowered proportionally (keeping the 0.40:0.25 ratio). Once the weight exceeds about 0.54, however, the order suddenly flips to A2-A3-A1 and A1 drops to third; this has been computed independently. In other words, the order in this table is resistant to small weight changes, but it flips suddenly and completely under an extreme weight shift; there is no gradual intermediate transition.
In the report: "With the weights given, A1 has the highest preference score (0.2833). This order does not change until C2's weight exceeds about 0.53, but beyond this threshold the order reverses completely."
Source: This example is DecisionMind's validation fixture for the OCRA engine. The method's founding source is Parkan (1994), but this table's figures do not come from the paper's own example, they come from the DecisionMind manifest; this is an illustrative example.
2. Energy: A distribution company's choice of renewable-plant investment
An electricity distribution company will choose among three renewable-energy plant investment proposals. Three criteria have been set: installation cost (input, lower is better), annual operating and maintenance expense (input, lower is better), and annual production capacity (output, higher is better). The investment committee has set the weights so that installation cost carries the most, production capacity less than that.
The method computes each proposal's shortfall against the cheapest on the two input criteria, and its superiority against the lowest capacity on the single output criterion, separately, and combines them. Suppose the result places the proposal with the cheapest installation first. Even though its production capacity is middling, its low cost more than compensates for the capacity advantage of the other two proposals.
The committee's hesitation: if the weight on production capacity is increased, the order may change; the proposal with the highest capacity but the most expensive installation could move ahead. This reflects a preference, not a fact. The committee is making a trade-off choice between "low cost" and "high production," and the report must state this choice explicitly.
In the report: "With the weights given, the proposal with the lowest installation cost is first; this order may change if the production-capacity weight is raised, and the decision is sensitive to this weight."
3. Logistics: An e-commerce company's choice of distribution-centre location
An e-commerce company will choose the location for a new distribution centre among three candidate regions. Three criteria: land rent (input, lower is better), average delivery time (input, lower is better), and daily parcel-processing capacity (output, higher is better). The weights give the most to delivery time, less to land rent.
The method computes each candidate's shortfall against the best on the two input criteria, and its superiority against the lowest capacity on the output criterion, and combines them. Suppose the result places the region with the shortest delivery time first; although this region's rent is highest, its superiority in delivery time compensates for it.
The company's hesitation: if a budget ceiling exists and the first-ranked region's rent exceeds it, OCRA will not screen it out on its own; rent is a criterion like any other, and it has already been traded off against the rest. In that case, the region exceeding the budget should be screened out before the analysis and only the remainder ranked.
In the report: "The budget ceiling was applied as a pre-screening criterion; the remaining regions were ranked using the delivery-time and capacity weights."
4. What Not to Do
Had C3 been marked "lower is better" in the same validation table, the output side's reference would have become the lowest production rather than the highest, and the alternative with the weakest output would have been unfairly favoured; the order would have become meaningless. The second error is adding a fourth alternative once the analysis is finished and being surprised that the input/output reference points (the group's own best/worst) have shifted; the alternative set should be fixed from the outset. The third error is reporting A1's score of 0.2833 as "A1 is 28 per cent more competitive than the others"; the score only ranks these three alternatives relative to one another, it is not a percentage performance level.
Extensions: for different data types
OCRA has 2 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, see the DecisionMind method page: decisionmind.app/library/ocra
Parkan, C. (1994). Operational competitiveness ratings of production units. Managerial and Decision Economics, 15(3), 201–221. DOI: 10.1002/mde.4090150303
Wang, S. (2006). Comments on operational competitiveness rating analysis (OCRA). European Journal of Operational Research, 169(1), 329–331. DOI: 10.1016/j.ejor.2004.07.056
Madic, M., Petkovic, D., & Radovanovic, M. (2015). Selection of non-conventional machining processes using the OCRA method. Serbian Journal of Management, 10(1), 61–73. DOI: 10.5937/sjm10-6802
Chakraborty, S., Chatterjee, P., & Das, P. P. (2023). Operational Competitiveness Rating Analysis (OCRA) Method. In Multi-Criteria Decision-Making Methods in Manufacturing Environments (pp. 165–170). Apple Academic Press / CRC Press. DOI: 10.1201/9781003377030-14