Professional Documents
Culture Documents
Week 7 Data Envelopment Analysis Linear Programming Technique
Week 7 Data Envelopment Analysis Linear Programming Technique
80 2 3
5 4 1
60
8
7
40
20
0
0 10 20 30 50 60
40
# Business Customers
Note: There is some “efficient” trade-off between the number of individual
versus business customers that any one bank can achieve, but what is it?
Extending to multiple outputs ...
Branches 2, 3, 4, 5, 7, 8 are less than 100% “efficient”
80 2
COMPOSITE BRANCH or ENTITY
3
5 4 1
60
8
7
40
20
0
0 10 20 30 40 50 60
# Individual Customers
“Pareto-Koopman efficiency” along the frontier - cannot increase an output (or decrease
an input) without compensating decrease in other outputs (or increase in other inputs).
Extending to multiple outputs ...
“Nearest” efficient points define a reference set and a linear combination of the
reference set inputs and outputs defines a hypothetical composite unit (HCU)
Reference set for #5 = {1,6}
Efficiency Score=73.4% 80 2 3
5 4 1
60
8
7
40
20
0
0 10 20 30 40 50 60
# Individual Customers
“Pareto-Koopman efficiency” along the frontier - cannot increase an output (or decrease
an input) without compensating decrease in other outputs (or increase in other inputs).
DEA and Efficient
Frontiers
• DEA uses an efficient frontier to define multiple I/O productivity
• Frontier defines the (observed) efficient trade-off among inputs
and outputs within a set of DMUs.
• Relative distance to the frontier defines efficiency
• “Nearest point” on frontier defines an efficient comparison unit
(hypothetical comparison unit (HCU))
• Differences in inputs and output between DMU and HCU define
productivity “gaps” (improvement potential)
Inputs Outputs
u O
k
j
Ek 1N j jk
v I
i1
i ik
To evaluate a give unit, e, choose nonnegative weights to
solve ...
max
Ee s.t.
Ek �
100, k
1,...,
K$
max Q 𝑢! 𝑂! '
Which can be formulated! " #
𝑠. 𝑡.
& Normalize weighted input of
Q 𝑣% 𝐼%' = 1 e to one
%"#
$ &
Q 𝑢! 𝑂! ( ≤ Q 𝑣% 𝐼% 𝑘=
!"# %"# 1, . . . , 𝐾
( ,
𝑢 ! ≥ 0, 𝑗=
𝑣% ≥ 1, . . . , 𝑀
0, 𝑖=
1, . . . , 𝑁
Using the results: Efficiency Vs. Profit
Matrix
High Profit
Under-performing Best practice
potential leaders comparison group
Low High
Eff. Eff.
Low Profit
DEA
Design
• “Ambivalence” about inputs and outputs - all should be
relatively important!
• “Approximate similarity” among DMUs
• objectives
• technology
• Provides relative efficiency only
• choice of units to include matters
• inclusion of “global leader” unit
may be desirable
• Experimenting with different I/O combinations may be
necessary
DEA
• Summary
Addresses fundamental productivity • Role of DEA
measurement problems due to ... • “data mining” to generate hypotheses
• complexity of service outputs
• evaluation/measurement
• variability in service outputs
• benchmarking to identify “best practice”
• Takes advantage of service operating units
environment
• large numbers of similar facilities • Caveats
• diversity of • “black box” - No information on root
practices/management/environment causes of inefficiency
• Provides useful information • Be aware of assumptions (e.g.
• objective measures of productivity linearity)
• reference set of comparable units • Can be sensitive to selection of
• excess use of inputs measure inputs/outputs
• returns to scale measure
Computing Efficiency of
DMUs
TO COMPUTE EFFICIENCY OF BRANCH # 1
MAXIMIZE Efficiency of #1 = (48 x Weight_Bus + 68 x Weight_Individual)/(160 x Weight_Labor)
DECISION VARIABLES: Weight_Bus, Weight_Individual, Weight_Labor
SUBJECT TO CONSTRAINTS: Branch # Business # Individual
Customers
• 160 x Weight_Labor = 1 (Normalize the denominator to calculate efficiency) Customers