10.07.2015 Views

FLEXIBILITY IN DESIGN - Title Page - MIT

FLEXIBILITY IN DESIGN - Title Page - MIT

FLEXIBILITY IN DESIGN - Title Page - MIT

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

de Neufville + Scholtes D R A F T September 30, 2009Box 2.1__________________________________________________________________________Valuing a XXXXXXX new example – Stefan to developThe value of a Parking Garage depends upon the number of users. In many cases, these areuncertain, for example when the garage serves a shopping mall whose future success isunknown.In this particular example, explained in detail in Chapter 3, the average actual systemperformance, measured by the average net present value of about $1.9M, is quite different fromthe system performance of $3.1 M obtained from the estimate of the average demand scenario.This deviation of the estimate from the performance of the fixed projection model is too stark tobe a chance effect. The great difference between the estimate of the actual average valueobtained by considering the various demand scenarios, and the number calculated using anaverage demand, is due to the capacity limitations of the garage. It cannot accept additional carsif the demand is high, so it cannot counterbalance the losses if demand is low. Thus, the actualresults are much lower than anticipated by an analysis based on average values.____________________________________________________________________________Box 2.2_____________________________________________________________________The gap between designers and forecastersOne of the chief designers of the Iridium satellite system for global telephone service visited <strong>MIT</strong>after the financial collapse of the venture. In sharing his experience with the design, he indicatedthat one of his greatest difficulties was getting the correct forecast of future use, and therefore offixing the specifications of the system.What the designer wanted was a definite fix on the number of users. He wanted to usethis number to optimize the size and capabilities of the individual satellites and of the fleet. Thedifficulty of getting this commitment from the marketing and forecasting team frustrated him.He was of course asking the wrong question. No forecasters could precisely anticipatethe actual demand for an untested service that would be deployed a decade later in competitionwith other rapidly evolving forms of technology – cell phones in particular. In retrospect, theforecast he used was about 20 times too high.The right question for the designer would have been: “what range of usage might exist?”The answer to this question would have given him some idea about how he could stage thedeployment of the system, to learn about the actual demand, and then to know how to shape thefuture development of the system to accommodate the actual needs.____________________________________________________________________Part 1: Chapters 1 to 3 <strong>Page</strong> 34 of 69

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!