in the model. In optimization models, we are concerned with maximizing or minimiz-
ing some measure of performance, expressed as a mathematical function, and we refer
to it as the objective function, or simply the objective.
1.2. SPREADSHEET MODELS
Algebra is an established language that works well for describing problems, but not
always for obtaining solutions. Algebraic solutions tend to occur in formulas, not num-
bers, but numbers most often represent decisions in the practical world. By contrast,
spreadsheets represent a practical language—one that works very effectively with
numbers. Like algebraic models, spreadsheets can be precise and compact, but there
are also complications that are unique to spreadsheets. For example, there is a differ-
ence between form and content in a spreadsheet. Two spreadsheets may look the same
in terms of layout and the numbers displayed on a computer screen, but the underlying
formulas in corresponding cells could differ. Because the information behind the dis-
play can be different even when two spreadsheets have the same on-screen appear-
ance, we can’t always tell the logical content from the form of the display. Another
complication is the lack of a single, well accepted way to build a spreadsheet represen-
tation of a given model. In an optimization model, we want to represent decision vari-
ables, an objective function, and constraints. However, that still leaves a lot of
flexibility in choosing how the logic of a particular model is incorporated into a
spreadsheet. Such flexibility would ordinarily be advantageous if the only use of a
spreadsheet were to help individuals solve problems. However, spreadsheets are per-
haps even more important as vehicles for communication. When we use spreadsheets
in this role, flexibility can sometimes lead to confusion and disrupt the intended
communication.
We will try to mitigate these complications with some design guidelines. For
example, it is helpful to create separate modules in the spreadsheet for decision vari-
ables, objective function, and constraints. To the extent that we follow such guidelines,
we may lose some flexibility in building a spreadsheet model. Moving the design pro-
cess toward standardization will, however, make the content of a spreadsheet more
understandable from its form, so differences between form and content become less
problematic.
With optimization, a spreadsheet model contains the analysis that ultimately pro-
vides decision support. For this reason, the spreadsheet model should be intelligible to
its users, not just to its developer. On some occasions, a spreadsheet might come into
routine use in an organization, even when the developer moves on. New analysts may
inherit the responsibilities associated with the model, so it is vital that they, too, under-
stand how the spreadsheet works. For that matter, the decision maker may also move
on. For the organization to retain the learning that has taken place, successive decision
makers must also understand the spreadsheet. In yet another scenario, the analyst
develops a model for one-time use but then discovers a need to reuse it several
months later in a different context. In such a situation, it’s important that the analyst
understands the original model, lest the passage of time obscure its purpose and
4
Chapter 1 Introduction to Spreadsheet Models for Optimization