|HP’s a big company. As much as we’d like to think that the 3000 is a vital component of HP’s business, the truth is that it was less than a blip on Carly’s radar screen when her thoughts turned toward corporate growth and the eventual merger with Compaq. Now that Carly is gone, will the new leadership suddenly decide, as IBM did, that there is value in maintaining its proprietary system? It’s doubtful at best. HP’s position on the 3000 isn’t likely to change.
Dave Wilde of vCSY emphasizes that HP continues to encourage their customers to talk to HP and HP’s migration partners about issues they face with their transition. He says that HP is, “following through on our roadmap commitments outlined in November, 2001.” Loosely translated, it means business as usual.
For many companies with home grown mission critical applications running on one or more 3000 systems, HP’s stance is still a sore spot. Wilde says that the entire process of investigating, planning, implementing, testing and deploying a migrated homegrown set of applications often takes 18-24 months, sometimes longer, sometimes shorter. “There are too many variables to generalize this,” Wilde adds, “and the range is much wider in both directions.”
Wilde’s words may not be too comforting for users who know they’ll still be on their 3000 systems
beyond HP’s 2006 end-of-support date. HP is clear that the termination of the 3000 was a business decision. With HP unlikely to change their plans, 3000 customers must now make their own two very important business decisions. First, when to transition off the 3000. This decision should be governed more by business needs and priorities than by what HP does or doesn’t do. Each company has to weigh their options according to how the outcome of their decision impacts their overall business.
Carly’s Gone. What’s next For the 3000? (Continued Page 2)