Understand AHP in engineering projects: hierarchy, pairwise comparison, Saaty scale, weight calculation, consistency ratio, sensitivity, and technical applications.

Check it out!

The AHP — Analytic Hierarchy Process — is a multi-criteria decision-support technique that structures a problem into hierarchical levels and uses pairwise comparisons to derive relative priorities among criteria and alternatives. In engineering projects, it is particularly useful when a choice involves technical, economic, operational, and risk requirements that cannot be reduced to a single unit of measure and when assigning weights directly would be arbitrary or excessively dependent on informal negotiation.

The central difference from a simple weighted decision matrix is that AHP does not merely ask the team to state final weights. It asks participants to compare two elements at a time: how much more important is availability than CAPEX? How much more important is maintainability than schedule? Which alternative is preferred to another under a given criterion? These comparisons form reciprocal matrices from which priority vectors are derived. The method also makes it possible to check the internal consistency of judgments.

AHP does not eliminate subjectivity. It organizes subjectivity and makes it auditable. The quality of the result still depends on the definition of the problem, criteria, alternatives, evidence, and the people making the judgments. In critical engineering decisions, the method should be accompanied by mandatory requirements, technical data, economic analysis, and sensitivity analysis — and should not be used as a mathematical mechanism to legitimize a predetermined choice.

What Is the AHP Method

The Analytic Hierarchy Process was developed by Thomas L. Saaty as a method for decomposing complex problems into a hierarchy and deriving ratio scales from pairwise comparisons. The classic 1977 paper presents the use of the principal eigenvector of a positive reciprocal matrix, a 1-to-9 judgment scale, and a consistency measure based on the maximum eigenvalue.

A typical structure has three levels:

  1. decision objective;
  2. criteria and, when necessary, subcriteria;
  3. alternatives.

More complex decisions may contain several intermediate levels.

How AHP Works

The process can be summarized in six steps:

  1. define the decision question;
  2. structure the hierarchy;
  3. perform pairwise comparisons;
  4. calculate local priorities;
  5. check consistency;
  6. synthesize global priorities and test sensitivity.
AHP method flow applied to an engineering decision

No

Yes

Define objective

Structure criteria and subcriteria

Compare criteria pairwise

Calculate local weights

Check consistency

Acceptable consistency?

Compare alternatives by criterion

Calculate local priorities of alternatives

Synthesize global priority

Test sensitivity and record decision

AHP method flow applied to an engineering decision

The sequence prevents the team from seeing only a final score without understanding how it was produced.

AHP Versus a Weighted Decision Matrix

Both approaches can produce weights and a ranking, but they are constructed differently.

AspectSimple weighted matrixAHP
Weight definitiondirectpairwise comparison
Structuregenerally flathierarchical
Judgment scalefreestructured ratio scale
Consistencyusually not measuredhas a consistency index and ratio
Effortlowerhigher
Auditability of weightsmoderatehigh when properly documented

The Decision Matrix in Engineering Projects is suitable when criteria and weights are simple and consensual. AHP adds rigor when the relative importance of the criteria is itself an important part of the problem.

Structure the Hierarchy Correctly

The hierarchy should represent the logic of the decision, not merely organize a list.

Example for selecting a critical-infrastructure solution:

Objective: select the most appropriate alternative.

Level 1 criteria:

  • technical performance;
  • reliability and operations;
  • economics;
  • implementation;
  • risk and life cycle.

Subcriteria:

  • capacity;
  • availability;
  • maintainability;
  • CAPEX;
  • TCO;
  • schedule;
  • constructability;
  • obsolescence;
  • supply chain.

Alternatives: A, B, and C.

Overly broad criteria make judgments difficult. Excessively fragmented criteria increase the number of comparisons and may introduce redundancy.

Mandatory Requirements Must Be Filtered Before AHP

AHP should not be used to compensate for a mandatory requirement. Noncompliant alternatives must be filtered out first; the method compares preferences among feasible options.

Structure requirements before making the decision

AHP compares preference. It should not turn a mandatory requirement into a compensable criterion.

If an alternative does not meet:

  • a mandatory standard;
  • minimum capacity;
  • a safety requirement;
  • mandatory interoperability;
  • a required certification;
  • a legal constraint;
  • an eliminatory contractual condition;

it should be addressed before the multi-criteria comparison, except when the objective itself is to study the cost or feasibility of eliminating that gap.

Requirements Management in Engineering Projects should provide that foundation.

Pairwise Comparison

The core of AHP is comparing two elements at a time relative to an element at the level above.

If the objective is to select an architecture, the team might answer:

With respect to project success, which is more important: availability or CAPEX? And by how much?

Then:

Availability or schedule?

And so on.

This decomposition reduces the difficulty of assigning global weights directly to many criteria.

Saaty’s Fundamental Scale

The traditional scale uses values from 1 to 9 to represent the intensity of preference.

ValueGeneral interpretation
1equal importance or preference
3moderate preference
5strong preference
7very strong preference
9extreme preference
2, 4, 6, 8intermediate values

Reciprocal values are used when the preference is reversed.

If A is strongly preferred to B and receives a value of 5, then B relative to A receives 1/5.

The scale is not a grading system. It represents a judgment ratio between pairs.

Reciprocal Comparison Matrix

For three criteria A, B, and C, a matrix may be:

ABC
A135
B1/312
C1/51/21

The diagonal is always 1 because each element is equally important to itself.

The reciprocal property requires:

aᵢⱼ = 1 / aⱼᵢ

The method derives a priority vector from this matrix.

How to Calculate Weights in AHP

The original formulation uses the principal eigenvector associated with the largest eigenvalue of the comparison matrix.

In a perfectly consistent matrix, if A is three times more important than B and B is twice as important as C, then A should be six times more important than C.

Human judgments are rarely perfectly consistent. AHP accepts some inconsistency and provides a mechanism for measuring it.

Eigenvector Method

Relative priority is obtained from the normalized principal eigenvector of the matrix.

Computational tools perform this calculation easily.

Normalization Approximation

For instructional applications, columns are often normalized and row averages calculated to obtain an approximation of the weights.

For professional decisions, the calculation methodology should be stated and reproducible.

Consistency in AHP

Consistency checks whether judgments maintain reasonably coherent relationships with one another.

Suppose:

  • A is preferred to B;
  • B is preferred to C;
  • but C is declared extremely preferable to A.

This structure may indicate a significant contradiction.

Saaty proposed the Consistency Index:

CI = (λmax − n) / (n − 1)

where:

  • λmax = largest eigenvalue of the matrix;
  • n = order of the matrix.

The index is then compared with a Random Index — RI — associated with random matrices of the same order.

Consistency Ratio — CR

A low consistency ratio indicates coherent judgments, not the quality of the criteria or evidence. A consistent matrix can be perfectly organized around poor assumptions.

Support the decision with Engineering Technical Consulting

The Consistency Ratio is:

CR = CI / RI

A widely used AHP reference is to seek a CR below 0.10 for matrices large enough for the measure to be meaningful. This threshold should be treated as a methodological reference rule, not as an automatic certificate of quality.

A matrix with a low CR may still have poor criteria, weak data, or biased participants. Internal consistency does not mean external correctness.

What to Do When Consistency Is Poor

The objective is not to manipulate numbers until a threshold is reached.

The team should review comparisons that appear contradictory and ask:

  • were the criteria understood in the same way?
  • was there a change of unit or perspective?
  • is any criterion redundant?
  • was the scale used correctly?
  • was the preference based on evidence or impression?
  • is there a real stakeholder conflict that should remain explicit?

The review should improve understanding of the decision, not merely the indicator.

Consistency Is Not Consensus

Two experts may be internally consistent and still disagree profoundly.

Example:

  • Operations prioritizes availability and maintainability;
  • Finance prioritizes CAPEX and cost of capital;
  • Engineering prioritizes performance and technical margin.

AHP should not hide this difference through automatic averaging.

One approach is to calculate weight scenarios by stakeholder and then discuss the differences.

How Many Comparisons Are Required

For n elements in a set, the number of unique comparisons is:

n(n − 1) / 2

This grows rapidly.

ElementsComparisons
33
510
721
1045
15105

Very broad hierarchies create fatigue and reduce the quality of judgments.

For this reason, AHP works best when the structure is well decomposed and the criteria at each level remain manageable.

Redundant Criteria Increase Work and Distortion

If CAPEX, initial price, and acquisition cost appear as three separate criteria, the same economic dimension may receive weight three times.

The problem exists in any MCDA method, but becomes especially burdensome in AHP because each additional criterion increases the number of comparisons.

Before the workshop, perform a semantic review of the criteria.

Compare Elements at the Same Conceptual Level

It is not coherent to compare “CAPEX” directly with “manufacturer quality” if one is an elementary criterion and the other represents an undefined group of attributes.

The hierarchy should place elements of comparable granularity under the same parent node.

This improves judgment quality.

AHP for Weights Versus Full AHP

There are two common ways to use AHP in engineering.

AHP Only to Define Weights

The team uses pairwise comparisons to derive criterion weights and then evaluates alternatives with normalized data in a decision matrix.

This hybrid approach is practical when the alternatives already have objective performance metrics.

AHP for Criteria and Alternatives

In addition to comparing criteria, the team compares alternatives pairwise under each criterion.

This is useful for criteria that are difficult to measure directly, but it greatly increases the number of judgments.

Prefer Objective Data When Available

If the alternatives’ CAPEX values are known, there is no need to ask subjectively whether A is “strongly better” than B in cost.

The actual values can be used and converted through a value function compatible with the method.

The same applies to:

  • calculated availability;
  • consumption;
  • schedule;
  • power;
  • capacity;
  • footprint;
  • MTBF;
  • efficiency.

Judgment should be reserved for dimensions for which sufficient direct measurement is not available.

AHP and Qualitative Criteria

The method is especially useful when criteria include:

  • ease of maintenance;
  • technology maturity;
  • architectural flexibility;
  • manufacturer support;
  • integration complexity;
  • operability;
  • future adaptability.

Even in these cases, descriptors and evidence should be defined before comparison.

AHP and Analysis of Technical Alternatives

During conceptual engineering, AHP can support trade studies when several solutions remain feasible.

The Set-Based Design approach keeps alternatives open until evidence allows responsible convergence.

AHP can be used at a convergence gate, provided the options have sufficient maturity for an equivalent comparison.

AHP and the Business Case

The Business Case in Engineering Projects can use AHP to justify the selection of the alternative that will proceed to final economic analysis.

The technical hierarchy does not replace:

  • NPV;
  • TCO;
  • risks;
  • schedule;
  • financing capacity;
  • strategic benefits.

It organizes dimensions that cannot be reduced directly to money.

AHP and Feasibility Studies

In a Technical and Economic Feasibility Study, AHP can structure the comparison among alternatives before the recommendation.

A good practice is to separate:

  1. mandatory technical filters;
  2. multi-criteria analysis;
  3. economic evaluation;
  4. risk and sensitivity analysis;
  5. recommendation and conditions.

This prevents a single score from hiding different dimensions.

AHP and TCO

When life-cycle costs are relevant, the economic criterion can use TCO and Life-Cycle Cost instead of initial price.

Pairwise comparison should not turn CAPEX, OPEX, and TCO into three redundant criteria without checking for double counting.

AHP and Procurement

In Procurement, AHP can support comparison of technologies or suppliers in strategic decisions.

TBE — Technical Bid Evaluation remains the process for technically evaluating bids against the requisition.

If AHP is used within TBE:

  • criteria should be defined before bid opening, where applicable;
  • eliminatory requirements remain eliminatory;
  • judgments should have documentary evidence;
  • commercial and technical evaluation should follow the established governance;
  • weights should not be changed to accommodate the result.

AHP and Technical Authority

The Technical Authority in Engineering can approve the methodology, criteria, and recommendation in critical decisions.

The AHP facilitator is not automatically the decision-maker.

Roles can be separated among:

  • sponsor;
  • facilitator;
  • subject-matter experts;
  • data owners;
  • independent reviewer;
  • approval authority.

Aggregating Judgments from Multiple Experts

There are two different questions:

  • aggregate individual judgments;
  • aggregate final priorities.

The aggregation method should be defined before the workshop.

Geometric means are frequently used to aggregate reciprocal judgments in AHP, but the choice should respect the governance model and the nature of the group.

One alternative is to maintain separate scenarios by function when disagreement is informative.

AHP Workshop

An effective workshop requires preparation.

Before the meeting:

  • approved problem statement;
  • alternatives described;
  • mandatory requirements resolved;
  • criteria defined;
  • data compiled;
  • participants selected;
  • methodology explained;
  • conflicts of interest identified.

During the meeting:

  • compare one pair at a time;
  • record the rationale;
  • present relevant evidence;
  • track consistency;
  • avoid undue hierarchical pressure;
  • record dissent.

Afterward:

  • calculate priorities;
  • test sensitivity;
  • validate assumptions;
  • issue a decision record.

Avoid Voting Disguised as AHP

If participants merely choose numbers to express personal preference without reference to criteria and evidence, the method loses value.

AHP is not an opinion poll. It is a structure for making judgments about a defined decision.

Sensitivity of Weights

The final priority should be tested against reasonable changes in weights.

Important questions include:

  • if the CAPEX weight increases by 10%, does the winning alternative change?
  • if availability is considered more critical, which alternative leads?
  • what minimum schedule weight would cause another option to take first place?

The Sensitivity and Scenario Analysis article examines switching values in greater depth.

Sensitivity of Judgments

If small changes in weights or comparisons change the winning alternative, the ranking is sensitive and deserves additional evidence before a CAPEX commitment.

Test robustness with sensitivity and scenarios

A 5:1 comparison can be tested as 3:1 or 7:1 when uncertainty exists.

If small changes in comparisons alter the ranking dramatically, the result is not robust.

This may justify:

  • additional testing;
  • consultation with another expert;
  • a pilot;
  • criterion review;
  • collection of market data.

AHP and Scenario Analysis

Different scenarios may use different hierarchies.

Example:

  • aggressive expansion scenario;
  • base case;
  • reduced-demand scenario.

Scalability may carry much greater weight in the first scenario.

Instead of forcing an average weight, the organization can compare how each alternative performs across scenarios.

AHP and Uncertainty

Classical AHP works with point judgments. Fuzzy, probabilistic, and other extensions have been developed to address uncertainty, but they add complexity.

Before using sophisticated extensions, verify whether the main problem is simply a lack of technical data.

Rank Reversal

AHP literature discusses situations in which adding or removing alternatives can change the relative ranking of existing options.

This phenomenon should be understood when the method is used for critical decisions.

The team should record the set of alternatives, the model version, and the synthesis rule used.

The result should not be presented as invariant to any change in context.

The Consistency Criterion Does Not Resolve Rank Reversal

CR measures the coherence of judgments in the matrix. It does not guarantee ranking stability when the set of alternatives changes.

These are different methodological issues.

AHP Versus MCDA

AHP is an MCDA method, not a synonym for multi-criteria analysis.

Multi-Criteria Decision Analysis — MCDA in Engineering Projects includes a broader family of methods, such as value models, outranking, and techniques based on distance from an ideal solution.

The choice depends on the nature of the decision.

When AHP Is a Good Choice

AHP tends to work well when:

  • there is a natural hierarchy of criteria;
  • the number of elements per level is manageable;
  • relative judgments are easier than absolute weights;
  • qualitative criteria are relevant;
  • the organization wants to measure consistency;
  • the decision requires strong traceability.

When AHP May Be Excessive

A simple weighted matrix may be better when:

  • there are three objective criteria;
  • weights are consensual;
  • data are directly measurable;
  • the decision is reversible and low impact;
  • the cost of the decision process exceeds the additional benefit of rigor.

The method should be proportional to the decision.

Example: Data Center Architecture Selection

Objective: select a critical-power architecture.

Criteria:

  • availability;
  • maintainability;
  • efficiency;
  • CAPEX;
  • TCO;
  • schedule;
  • expansion;
  • operational complexity.

Alternatives:

  • N+1;
  • 2N;
  • hybrid modular architecture.

AHP can define weights through pairwise comparison. Actual data can evaluate CAPEX, efficiency, and footprint; experts can compare operability and flexibility when those dimensions lack a single sufficient metric.

Example: Telecommunications Solution Selection

Alternatives may involve radio, fiber, or a hybrid solution.

Criteria:

  • availability;
  • throughput;
  • latency;
  • CAPEX;
  • schedule;
  • licensing;
  • physical vulnerability;
  • expansion;
  • maintenance.

A minimum-capacity requirement should be a filter before AHP. Compliant options can then be compared.

Example: Make-or-Buy

Criteria may include:

  • TCO;
  • implementation speed;
  • technology control;
  • supplier dependency;
  • internal capability;
  • scalability;
  • obsolescence risk;
  • security.

The economic decision should be modeled separately to prevent a subjective score from replacing available financial values.

Example: Technically Equivalent Supplier

After a TBE, two bids may meet all requirements and remain technically very close.

AHP can be used if governance allows preferential criteria such as:

  • maintainability;
  • warranty;
  • support;
  • performance history;
  • flexibility;
  • integration.

The criteria need to be defined in advance to avoid ex post favoritism.

AHP in FEL

In FEL — Front-End Loading, AHP can support selection of the alternative that will advance to a higher level of definition.

In early FEL, some scores will be based on benchmarks. In advanced FEL, engineering data, quotations, and risks become more precise.

The matrix should be version-controlled across the gates.

AHP in Design Review

Design Reviews can assess whether:

  • criteria represent the requirements;
  • weights reflect the decision;
  • alternatives were compared at equivalent maturity;
  • judgments have evidence;
  • CR was reviewed;
  • sensitivity analysis was performed;
  • risks of the winning alternative are recorded.

The review should not be limited to looking at the final ranking.

AHP in Owner’s Engineering

Owner’s Engineering can independently facilitate AHP among alternatives presented by EPC contractors, suppliers, or designers.

This independence is valuable in choices with significant life-cycle impact.

Minimum AHP Record

The report should contain:

  • objective;
  • decision scope;
  • alternatives;
  • mandatory filters;
  • criteria hierarchy;
  • definitions;
  • participants;
  • comparison matrix;
  • weight calculation method;
  • CI and CR;
  • local priorities;
  • global priorities;
  • objective data used;
  • rationales;
  • sensitivity analysis;
  • model version;
  • approved decision;
  • conditions.

Without this record, the final score is difficult to audit.

An AHP Spreadsheet Is Not a Methodology

A spreadsheet can automate calculations, but it does not define:

  • the problem;
  • the criteria;
  • the evidence;
  • the participants;
  • the consensus process;
  • the decision authority.

The risk is turning AHP into a mathematical form without governance.

Common AHP Mistakes

Creating Criteria After Knowing the Preferred Alternative

This introduces structural bias.

Allowing a Mandatory Requirement to Be Compensated

Compliance should be addressed before preference.

Using Too Many Criteria at the Same Level

This increases comparisons and fatigue.

Accepting a Low CR as Proof of Correctness

Consistency does not validate data or eliminate bias.

Forcing Consensus

Real disagreement may contain important information.

Using Subjective Comparisons for Objective Data

If reliable measurement exists, use it.

Ignoring Sensitivity

A narrow ranking may be unstable.

Changing Weights After Seeing the Result

This turns the method into rationalization.

Not Versioning the Decision

Changes in alternatives or assumptions lose traceability.

How to Integrate AHP into an Engineering Decision Journey

A robust journey can be:

Requirements → alternatives → compliance filter → AHP/MCDA → economic analysis → sensitivity → Design Review → gate → Procurement/TBE → execution → validation.

Each stage answers a different question.

AHP occupies the multi-criteria selection stage, not the entire investment process.

When Engineering Consulting Adds Value

Engineering Technical Consulting adds independence and method when a decision involves multiple disciplines or conflicting interests.

The work may include:

  • structuring the hierarchy;
  • rationalizing criteria;
  • collecting evidence;
  • facilitating comparisons;
  • calculating priorities;
  • consistency analysis;
  • stakeholder scenarios;
  • sensitivity analysis;
  • integration with TCO and the Business Case;
  • issuing the decision record.

The quality of AHP comes from decision governance, not from the software used.

Final Considerations

AHP is a powerful method for decisions in which direct assignment of weights is insufficient and qualitative and quantitative criteria need to be integrated. Its hierarchical structure and pairwise comparisons help turn preferences into relative priorities, while the consistency ratio provides a mechanism for reviewing judgments.

The method, however, does not eliminate subjectivity or replace requirements, engineering data, economic analysis, or technical authority. A low CR does not turn poor assumptions into a good decision. A professional application should filter mandatory requirements, use objective data whenever available, record judgments, test sensitivity, and preserve versions.

In engineering projects, AHP works best as part of a decision chain: requirements define boundaries; alternatives are developed; AHP organizes trade-offs; DCF and TCO quantify economics; risks and sensitivity test robustness; and governance records who approved the choice and under what conditions.

In critical decisions, an independent facilitator helps separate method, evidence, and authority, reducing the risk that AHP becomes merely a numerical justification for the preferred solution.

Learn about Owner’s Engineering

Technical References

[1] SAATY, Thomas L. A scaling method for priorities in hierarchical structures. Journal of Mathematical Psychology, v. 15, n. 3, p. 234–281, 1977. DOI: 10.1016/0022-2496(77)90033-5. Available at: https://doi.org/10.1016/0022-2496(77)90033-5

[2] SAATY, Thomas L. The analytic hierarchy process—what it is and how it is used. Mathematical Modelling, v. 9, n. 3-5, p. 161–176, 1987. DOI: 10.1016/0270-0255(87)90473-8. Available at: https://doi.org/10.1016/0270-0255(87)90473-8

[3] DEPARTMENT FOR COMMUNITIES AND LOCAL GOVERNMENT. Multi-criteria analysis: a manual. London, 2009. Available at: https://www.gov.uk/government/publications/multi-criteria-analysis-manual-for-making-government-policy

[4] INTERNATIONAL COUNCIL ON SYSTEMS ENGINEERING. Decision Analysis Working Group. West Lafayette: INCOSE. Available at: https://www.incose.org/group/decision-analysis-working-group/

[5] PROJECT MANAGEMENT INSTITUTE. The Standard for Project Management and A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 8th ed. Newtown Square: PMI, 2025. Available at: https://www.pmi.org/standards/pmbok

Frequently Asked Questions
What is the AHP method?

AHP is a multi-criteria analysis method that structures a decision into a hierarchy and uses pairwise comparisons to derive weights and relative priorities.

What is the difference between AHP and a decision matrix?

A weighted matrix can receive weights directly. AHP derives priorities through pairwise comparisons and makes it possible to measure the internal consistency of judgments.

What does the 1-to-9 scale mean in AHP?

It expresses the intensity of preference between two elements: 1 represents equality and higher values represent progressively stronger preference, with reciprocals for the inverse relationship.

What is the consistency ratio in AHP?

It is the ratio between the matrix consistency index and a reference random index. It indicates the degree of internal coherence of pairwise judgments.

Does a CR below 0.10 guarantee that the AHP is correct?

No. It is a common methodological reference for consistency, but it does not validate the criteria, data, participants, or absence of bias.

Can AHP use objective data?

Yes. Measurable data such as CAPEX, schedule, and efficiency should be preserved and integrated through value functions or compatible methods, avoiding unnecessary subjectivity.

Is AHP an MCDA method?

Yes. AHP is one of the methodologies within the Multi-Criteria Decision Analysis family.

When is AHP worth using in engineering?

When there is a hierarchy of criteria, important trade-offs, qualitative criteria, difficulty assigning weights directly, and a need for strong decision traceability.

Supplementary Technical Materials

Related Solutions

Related Services

Core Content on the Topic

Related Technical Content