Offering regional and national programs, CIO (and CSO) events bring together some of the most respected names and thought leaders in information technology and security. Presented by CIOs and other senior level executives, these invitation-only programs offer timely topics and strong networking. Learn More »
Public Council Teleconference: Application Rationalization — Hidden Costs and Smart Decisions
November 17 at 11:00 am US/Eastern (GMT-5)
Join Honorio Padrón, of The Hackett Group, who will share the drivers for companies to tackle application rationalization and the results of research that define the hidden cost of complexity. Additionally, we will discuss key decision milestones—to start or not, holding the course steady and fulfilling expectations.
Virtual Desktop Cost-Benefit Analysis — Michael Jacobs, Catlin Group
The analysis contained in this presentation measures the cost of everything from the machines and licenses to the infrastructure for virtual vs. traditional desktop environments.
Honor your best senior team members - Apply for the CIO Ones to Watch Award
Get well-earned public recognition for your top up-and-coming team members, your IT organization and your enterprise. Award winners will be announced, publicized and feted in May 2010, great timing to help attract new IT recruits to your company.
Learn more about the CIO Executive Council »December 15, 2004 — CIO —
As a leading entertainment retailer with more than 800 stores, we're always looking for a competitive edge. And in the fall of 2000, we found one. Working with an outside software developer, we created our own "Listening-Viewing" system that lets customers see and hear clips from products in our stores just by scanning their bar codes.
Like many companies, we arranged to have the source code from the project put in escrow (in this case, with Iron Mountain) as a hedge against our vendor going out of business or failing to support a product we relied on. But our reason for pulling the code out of escrow was rather unique: We removed it not because we needed it, but because we acquired it; once you own the code, you don't need escrow anymore.
What happened was that our vendor was trying to market the system to our competitors. After the ensuing lawsuit (in which TWE prevailed), we took over the software company and the source code.
If you look at our investment in the system, the cost of putting the code in escrow was insignificant. I would definitely do it again.
As told to Christopher Lindquist