InteractiveMap of Operations Research
Back to Foundations of OR
ApplicationIntermediate01.08
Foundations of OR

Data Envelopment Analysis

Benchmark efficiency across comparable units.

Overview

Data Envelopment Analysis focuses on benchmark efficiency across comparable units. In the map of OR, it connects Efficiency frontier, CCR/BCC models, Peer units to decisions that must be modeled, solved, explained, and revised as evidence changes.

DEA uses optimization to compare decision-making units such as hospitals, branches, schools, and plants when multiple inputs and outputs matter. The practical use case is clearest in Hospitals, Bank branches, Universities, Manufacturing plants, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

Efficiency frontier

Efficiency frontier is a core checkpoint for Data Envelopment Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

CCR/BCC models

CCR/BCC models is a core checkpoint for Data Envelopment Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Peer units

Peer units is a core checkpoint for Data Envelopment Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Slack

Slack is a core checkpoint for Data Envelopment Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with Hospitals: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into Efficiency frontier, CCR/BCC models, and Peer units; define units and data sources for each one.
  3. 3Build a small instance of Data Envelopment Analysis that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

HospitalsBank branchesUniversitiesManufacturing plants
  • Hospitals: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Bank branches: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Universities: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Manufacturing plants: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.

Common pitfalls

  • Applying Data Envelopment Analysis because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating Efficiency frontier as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources