On the first business day of 2008, the new year offers some opportunity to define the finish of your Transition Era. This is the 12-month period in which HP promises to wrap up its patch development for the system. HP hasn't confirmed it, but perhaps this is final year to have an impact on the release of the completed 3000 beta patches still not tested to HP's standards.

Things are changing and HP's role is coming to a close, at least in the cubicles of HP's 3000 labs.

This year also holds the prospect for being a period where HP doesn't change its ending date for servicing the 3000 community. With no changes, this strategy would give the migration companies — some of whom, like MB Foster and Speedware, have been preparing for migration service and offering it since 2002 — a spark to prod some sites into action.

A new year can arrive with resolutions for 3000 community members, where they are leaving the platform in an orderly procession or staying until 2027. Resolutions work best when they are positive statements, rather than negative denials of existing actions. With that in mind, here's a few to consider taking up and practicing during 2008.

You might resolve to

• Take HP at its word about the exit date of the vendor from the marketplace. While some customers are happier with the chance to call HP a support provider through 2010, the company could move on and give the migration suppliers and third parties a chance to develop business in the market.
• Beta test a few patches that will benefit your fellow customers during 2008. Dozens of repairs and a score of improvements are locked inside HP's support customer environment. HP still has not announced a program to deal with whatever is still on the test shelf when 2008 wraps up — or 2010, if releasing a beta patch to general release is possible after this year.
• Establish a detailed migration plan or a sustainability plan for your HP 3000 operations. Planning shows command and confidence, and it's the least costly step of a transition.