Last month, I attended the INFORMS Practice Conference in Phoenix, Arizona. That was my first practice conference and the format was very different from the Fall meeting, which focuses on academic research - at the practice conference, talks last about 50 minutes rather than 20, focus on high-level ideas and results (avoiding equations for the most part), and are supported by high-quality visual aids. Note to self: practitioners really know how to use PowerPoint. The much lower attendance (in the hundreds of people rather than thousands) and the higher registration fee allows for networking breakfasts and lunches that are just as valuable as the presentations themselves, although the talks offer fantastic opportunities to see how operations research can be applied to real-life problems, and to get a sense of the issues that truly matter to practitioners.
This is the first conference in a long time where I did not skip any talk to catch up with old friends and colleagues; the Fall meeting is notorious for its fifty tracks spread out all over the conference hotels, with a few courageous people hopping from a session to the next and many others just hanging out in the lobby. My two favorite talks were "Incorporating Adverse Selection in Consumer Credit Decisions" by Robert Phillips from Columbia University and Nomis Solutions, which dealt with the fact that if you charge your customers a high interest rate, you're mostly going to get the high-risk people who can't get a better rate anywhere else, and the naive ones who don't realize rates vary a lot from a financial institution to the next, as well as "Range Planning: Supply and Demand Uncertainty in Financial Planning" by Blake Johnson from Stanford University, which introduced the concept of range contracts, a concept Diego Klabjan, who also attended the session, and I found particularly interesting.
At one of the lunches, a young MIT alumna who now works as a consultant in DC mentioned she found the talks presented by academics much more valuable than those by practitioners, because professors' teaching background allows them to make better presentations and convey the information in simpler terms. She was apparently getting a lot more out of these talks. I see her point - while I enjoyed some of the presentations made by industry people, the most interesting ones always had a connection with academia, often because the project was an industry-university partnership. That is not only because academics are more seasoned teachers, but because they practice creativity and out-of-the-box thinking of the highest order, while industry input helps them focus on valuable endeavors rather than toy problems. The worst two presentations were industry-only projects.
In one, the "founder and CEO" of his own consulting company attempted to explain what went wrong with the demand forecasting of a product that turned out to be a lot more popular than expected (leading to massive production delays); people in the audience started bombarding him with questions regarding his analysis and it became painfully apparent he had no clue what he was talking about. While I didn't look into that person's background and I'm not referring to that person's career path in any way, that made me think that sometimes people start their own business because they're unable to find anything better to do, rather than out of true entrepreneurship, and that the quality of independent consultants out there varies a lot. That also made me think that earlier peer input could have saved that man from a really embarrassing moment.
The other talk I didn't like was a presentation where someone decided to run a Monte-Carlo simulation by adding uncertainty to parameters treated as constants in the traditional Net Present Value framework, and look at the NPV distribution and the probability of its being positive to decide whether a project is worth launching. And for this, which is standard fare in simulation software such as Palisade's DecisionTools Industrial Suite, the man claimed that he had invented a new method and put his name and the name of a co-worker on it. How preposterous. His other contribution was to change the internal rate of return depending on the volatility of the main random variable in that time period. People in the audience pointed out that the IRR was set in all companies and their organization would never make it vary like that. The presenter also said that his method ended up giving the same valuation as the Black-Scholes model, which obviously couldn't be true because of the different model and assumptions involved - a point he agreed upon when confronted by audience members. The demand planning talk I mentioned above was a real train wreck, but that one came a close second. Fortunately, those are only two among the many captivating presentations made during the conference.
I enjoyed the presentation made by the team who won the Edelman Award - Hewlett-Packard, for its "successful product management initiatives" (from this press release). The idea was that HP needed an efficient algorithm to identify revenue-generating products and products they might discontinue; in this context, a product is every little thing that makes a computer, not the whole computer itself. The HP research team tried various algorithms to determine the "portfolio coverage" (a novel concept that considers the products in relationship to each other instead of in isolation). Because of the number of products HP manufactures, algorithms had to be able to handle hundreds of thousands of variables and output an answer in a short amount of time. This is not a research problem you solve in a day, and the HP team did an excellent job explaining its progression as team members decreased the running time little by little by changing their approach and attacking the problem from different angles - a great research lesson for anyone and in particular PhD students (few of whom were in attendance, but hopefully they will be there for the repeat presentation at the Fall meeting in San Diego).
There was an awkward moment in the Q&A period (the audience wasn't allowed to ask questions during the presentations the day before where the judges determined who should win, so that was the first time attendees could make comments) when someone said that he could see the benefit from bringing running time from days down to 20 minutes, but since the algorithm is run once a month for one application and once a quarter for the other, there didn't seem to be much of a purpose in decreasing the running time to a matter of seconds using a completely different approach, which appears to have played a key role in HP getting the award. (Maybe the person who asked the question was a disgruntled finalist from one of the other teams.)
The HP team hummed and hawed and just couldn't come with an answer for three painful minutes, until another HP scientist in the audience got up and said it was important for validation runs (to check the algorithm worked correctly). That was hardly an exciting answer, although I suspect the real reason they did all this, which might have been obvious to them but which they couldn't articulate because it was early in the morning after the awards banquet the previous night, is that they wanted the ability to answer any what-if question from their bosses in real time - something you can do if the algorithm runs in twenty seconds but not in twenty minutes.
But there is no denying HP has done a superb job, applying cutting-edge operations research to a real problem they faced in managing their supply chain. Its Revenue Coverage Optimization tool has saved the company more than $500 million between 2005 and 2008, according to the Edelman press release. HP used the algorithm "to rank its Personal Systems Group offerings based on the
interrelationship between products and orders. It then identified the
“core offering,” which is composed of the most critical products in
each region. This core offering represented about 30 percent of the
ranked product portfolio. All other products were classified as HP’s
“extended offering.” Based on these findings, HP adjusted its service
level for each class of products. [... This has resulted] in lower costs and higher margins for the company," ultimately improving customer service by building inventory and decreasing lead times of core items.
Overall, the Spring practice meeting was a very enjoyable and valuable experience, which I will certainly reiterate.