![]() April 1999 Why Spreadsheets Should Be in OR/MS Practitioners' Tool Kits By Thomas A. Grossman Jr. Spreadsheets have the potential to revolutionize management science. They are certainly revolutionizing management science as experienced by tens of thousands of business school students every year, who as end-user modelers now get to actually do management science rather than study algorithms they'll never be able to access, or learn how to become "informed consumers" of a micro-niche of the management consulting industry. However, spreadsheets don't seem to be getting much attention in the practice community. In this article we argue that spreadsheets have an important place in the practitioner's tool kit. Science is at the center of OR/MS, but application of OR/MS is as much art and craft as it is science. Skilled craftsmen know it's important to choose the right tool for the job, and smart OR practitioners recognize the value of selecting the best software tool for each activity. Spreadsheets provide real benefits to OR practitioners. Here's why: 1. Spreadsheets are more powerful for "real" OR modeling than is generally realized, and getting more so rapidly. 2. Spreadsheets provide an integrated platform that meet many practitioner needs better than specialized OR software. 3. Spreadsheets are useful for quick prototyping, even of models that will ultimately be written in special-purpose software. 4. Spreadsheets provide an excellent communication tool for non-technical clients. When not to use spreadsheets Spreadsheets are a source of worry to some OR professionals, and the notion of using spreadsheets for OR/MS particularly by naive end user modelers can induce gnashing of teeth and darkening of countenances. Criticisms of spreadsheets for OR/MS are often valid, since (like any software) spreadsheets have definite limitations. So before we discuss using spreadsheets for management science, let's talk about not using spreadsheets for management science. There will always be models and applications where spreadsheets just plain won't work, or where spreadsheets could be made to work but are not appropriate. It is a universal truth of programming that special-purpose software has big advantages over general-purpose software whenever size, scope, complexity or requisite technical expertise are sufficiently large. Spreadsheets are slower, dumber, less efficient and less scaleable than stand-alone management science software, and always will be. If your model is big and complex and hard, then DON'T USE SPREADSHEETS. Examples where spreadsheets generally don't make sense include models where the algebraic representation has more than two or three indices; complex queueing simulations; models where "standard" LP/QP/IP techniques are insufficient and custom algorithms are required; and models with highly complex data pre-processing. Also, spreadsheet models probably don't make sense in production IT environments. However, if your model is small (don't forget that "small" gets bigger every day!) and more-or-less straightforward, you're crazy not to use spreadsheets. Why would anyone want to implement, say, a 200-variable transportation problem in anything other than a spreadsheet? Spreadsheets are useful for big problems, too. Industry users routinely optimize spreadsheet LP models with 15,000 decision variables (although at that size model management and debugging issues would argue for a transition to a modeling language such as AMPL) and quadratic programs with 500 decision variables. Spreadsheets are a great integrated platform for the unsung but vital activities of OR practice: data management, reporting and graphing. These issues don't get much attention in the research literature, but they are key to the day-to-day business of practitioners. Due to their flexibility, ubiquity and ease of use, spreadsheets can be a good choice for data management and report generation, and are often the best choice for graphing. (Again, up to a point: When the datasets are too large, swap the spreadsheet for a database. If the graph is too complicated, use Mathematica. Your mileage will vary.) If you're an OR/MS project leader stuck in O'Hare Airport, why not use the Excel Solver that's already sitting on your laptop to whip up a prototype instead of waiting for a young OR associate back home to program the matrix generator for you? With an easy interface, built-in linear and non-linear optimizers, and available add-in packages for simulation and meta-heuristics, spreadsheets are a very pleasant environment for prototyping and general hacking. (Also, Solver provides a quick method for solving a system of linear equations: Feed the equations to Solver as constraints, create a dummy OBJ, and go. No matrix manipulations nor programming required.) Non-technical communication tool Spreadsheets are tremendously valuable as a tool for communicating model functionality to non-technical clients. It is well-known that getting clients to "buy in" to OR/MS models is a difficult challenge. Who among us with practice experience has not witnessed eyes glazing over, women fainting, and strong men weeping in the face of an algebraic LP formulation? Like most normal human beings, our clients and potential clients don't understand our algebraic formulations. But clients LIKE spreadsheet models! They provide a concrete representation of a model that ordinary people often find easier to understand than the more powerful abstract algebraic representation that OR/MS professionals use. Unlike specialized OR software, spreadsheet models automatically provide "what-if" tools without additional programming. You can hand someone a laptop with Excel and have them change a number to "see for themselves." If you can implement your model (even a scaled-down version) so the client actually understands it, why not do it? I believe that OR practitioners owe it to themselves to learn at least something about doing management science in spreadsheets. Yes, the latest interior point algorithm implemented in assembler and running on networked workstations will be a zillion times faster than the Excel Solver. But in the blink of an eye, Solver on a cheap Pentium can optimize problems that we could barely solve 10 or 20 years ago. There are plenty of profitable consulting engagements that use run-of- the-mill 500-variable LPs or 100-variable binary IPs that spreadsheets can generally handle without difficulty. Why not program them in an easy computing environment that the client might just be able to maintain on their own? Spreadsheets offer OR/MS practitioners many benefits in terms of number-crunching, implementing, prototyping, and communicating. They can enhance client acceptance and provide convenient data management. Spreadsheets are a cheap and useful addition to the practitioner's tool kit. If you are a practitioner with a varied practice, you might well find that a day spent learning how to do OR in spreadsheets will pay off for you in some pleasing ways. The accompanying story suggests where to get started finding resources for spreadsheet OR. Further reading Leon, Przasnyski and Seal [1996] provide examples and survey results on the use of spreadsheets by OR practitioners. See Decisioneering [1999] for several spreadsheet simulation modeling success stories; TRW and Bankers Trust are particularly interesting. Fylstra et al. [1998] discuss the technical details of the Solver. Conway and Ragsdale [1997] provide useful guidelines for formulating optimization models in spreadsheets. Savage [1997] discusses the weaknesses and benefits of spreadsheets. Cragg and King [1993] discuss problems with spreadsheet models in general, and identify opportunities for OR practice. Powell [1995] discusses the craft skills of modeling. Plane [1994] makes the case for end user modeling. Acknowledgements Thanks to Steve Powell and Peter Horner for comments on an early draft. Sources
Tom Grossman of the University of Calgary is president of the INFORMS Education Forum and a former practitioner with Decision Focus (now Talus Solutions). He can be reached via http://www.ucalgary.ca/~grossman OR/MS Today copyright © 1999 by the Institute for Operations Research and the Management Sciences. All rights reserved. Lionheart Publishing, Inc. 506 Roswell Street, Suite 220, Marietta, GA 30060, USA Phone: 770-431-0867 | Fax: 770-432-6969 E-mail: lpi@lionhrtpub.com URL: http://www.lionhrtpub.com Web Site © Copyright 1999 by Lionheart Publishing, Inc. All rights reserved. |