November 09, 2009
A New 3000, to Mitigate Risks
At this fall's e3000 Community Meet, ScreenJet's Alan Yeo shared an unexpected story. His company helped to establish a new HP 3000 customer site within the past year. While there's a lot of talk about the risk of remaining on the HP 3000 due to the vendor's exit in 2010, this company saw a 3000 app as a way to avoid the trouble of falling behind.
In our 3-minute video (click on the embed above, or view it on our YouTube channel), Yeo related the case study. A 3000 solution beat out IBM iSeries apps and outlasted the promises of a migration too often postponed.
They were in a position where they hadn't been allowed to do anything for years — because the answer to everything they wanted to do was, “wait until the new ERP system comes in.” They said they needed to do something, so they looked in their group to see who was doing what. The best systems they had in the group happened to be HP 3000 systems. Even though they had IBM i5 apps running.
There's risk in any choice, because IT management never provides a foolproof solution. Tales at the Meet's Roundtable outlined the merits of migrating bugs (to keep auditors happy) and training a third party to manage an application that's understood by only one IT pro at a corporation.
Nobody can mistake a single 3000 startup as a trend, not as 2010 waits at the end of next month. But risk is in the eye of the customer. This one has good reasons for taking up with MPE/iX apps for the foreseeable future.
"The group's strategy was to implement a new ERP system," Yeo said, "but they hadn't gotten around to doing it for five years. Then the economic climate changes, and suddenly you haven't got $10 million in cash to do it."
It's the kind of story more easily shared when you can look your audience in the eye. That kind of contact makes a good case for more Meets in the years to come.
Use our search engine to find 20 years
of HP 3000 news and articles
The comments to this entry are closed.