I caught parts of the Oracle + Sun web cast last week. Like many people, I've been thinking about the content of the web cast. In particular, Larry Ellison and other speakers mentioned moving back to the concept of integrated systems, much like in the mainframe era of the 1960's.
While I don't pretend to know much about the mainframe market in the 1960's, one thing that I do know is that the way IBM ran their business back then lead to alternatives such as the mini-computer, and ultimately paved the way for UNIX systems, still often referred to as Open Systems. The market is much different today, with multiple strong vendors, including HP, offering customers choice and driving healthy competition. Let's face it, competition keeps everyone on their toes!
Apparently, I'm not the only one questioning how great the mainframe market of the 1960's really was.
John Rymer at Forrester has a great analysis on his Forrester Blog at http://blogs.forrester.com/appdev/2010/01/peace-love-and-the-ibm-system-360.html that covers this topic rather well. He has an interesting list of the pros and cons of the mainframe era that makes for good reading.
In addition, I know that in my discussions with customers, Oracle and Oracle licensing is a very popular topic. Integrated solutions definitely help drive down the maintenance cost for that solution. However, standardization across multiple projects also drives down costs. While there are always good business cases for one off exceptions, I know that keeping those exceptions to a minimum helps drastically reduce backend support costs. It will be interesting to see how this plays out over the next year.
This is one of the first changes that will impact the UNIX business this year, and I'm sure that there are plenty more coming.
One of the reasons
that I came home between the training events in London and Frankfurt was to
cover a customer briefing at the Cupertino Executive Briefing Center -although
it also saved HP money, and let's face it, everyone's budget is still pretty
The briefing was an
overview of the HP and HP IT Transformation. However, there was a specific
deeper dive and conversation around our desktop management - everything from
asset management, self serve processes, to help desk processes. While I often
speak about mission critical environments, it is great to also have a glimpse
into the desktop and notebook environments - especially since as a user, I'm a
customer of our internal services.
It's been a two
years since I last got a new notebook, and I got to use some of the new
processes in person. Instead of waiting for my business to have available funds
for new notebooks, we now get automated e-mails when it is time to refresh our
systems. We select our user profile, and a week or two later, the system shows
up at our desk.
Then, instead of
someone from HP IT disappearing with our old and new system for half a day or
more, we log into the new notebook, finish some minor set up ourselves. Both
systems are then unplugged from the network, software is run on both systems,
and all of our settings and data are copied to the new system. Even better, I
can do this at home at night, so I'm not sitting around the office looking
useless, waiting for my systems to come back. I have much less downtime, and IT
doesn't have someone spending a lot of time just copying data from one system
to another. Even better, they have made this process easy enough that most of
my co-workers who normally call the helpdesk (or me) whenever they run into any
sort of problem now do this on their own, with no help.
But the interesting
part of this past year is seeing the impact of the economy on our help desk.
Due to the poor economy in 2009, HP pushed out the refresh on some systems by
another 6 months. It turns out, that they can see a direct co-relation to the number
of help desk calls as they did this, something that we could never track in the
past. Users of systems that are older than our usual refresh age are now
logging more calls, more downtime, and more repairs than they were in the past.
We helped save the company some money during the economic downturn, but it is
definitely driving up our maintenance budget. Since our goal here at HP is to
keep our maintenance costs low, you can bet that this will change as the
economy becomes more predictable.
However, the biggest
difference today compared to a number of years ago is that we can now track the
impact of decisions like pushing out the refresh rate for desktops and
notebooks, something we never could do in the past.
This begs the
question about what happens in a mission critical environment. There are lots
and lots of mission critical systems out there that have been in place for 5
years, 6 years, 10 years, or more. While the server life cycle definitely is
longer than desktops and notebooks, at some point, we run into the same issue -
old systems cost more to maintain than new systems (especially after the
warranty expires). Just because the system is still up and running, and has
been paid for, doesn't mean that it is cheaper than buying a new systems. We're
figuring that out at HP for our internal use.
Does this apply
outside of HP? Can you actually track the relationship between system age and
maintenance costs? What have you found?