7 things that are wrong with many Enterprise IT systems?

The Enterprise IT organization is an interesting entity.  The following are some observations I have made and are interesting problems to try and solve.

1. The main priority of many people in Enterprise IT is to protect their jobs.  Due to the crappy way that many companies have treated their IT organizations.  It is a thankless job in many companies. In the past, efforts have been made to outsource the job to other companies and India.  So, the people who are still around have developed a harsh survival instinct to do whatever it takes to protect their job.
2. Too many nice people who try to do the right thing are the victims not the heroes.
3. 80% or more of enterprise IT is full of people who are not technical by education. I have been spoiled working in product development at HP, Apple, and Microsoft where you hire the the best technical people to develop products.  These are what I consider technical staff.  They really know how things work and be so valuable people will pay money for them.  Other than Amazon Web Services, what enterprise IT has built an IT system so well that people would pay money for it?
4. So the 20% of enterprise IT that are technical, can they make the really tough decisions?  Many times no, because the decisions in most enterprise IT systems are not made by the most technical people it is made by the people who have the strongest survival instinct.
5. The Cloud is a threat to the monopoly of enterprise IT.  Until the Cloud, users had to use the enterprise e-mail system, CRM, file servers, web hosting, etc.  Now the business units have choice.
6. The private cloud's #1 goal in many companies is to shut down the choice of going outside the enterprise IT monopoly.
7. The private cloud will be much more expensive than the public cloud, because the private cloud's goal is to protect jobs where the public cloud's goal is to reduce costs which means higher utilization of all resources including people.  Cloud environments have one admin per 1,000+ servers.  Many enterprises have one admin per 10-20 servers.  Some have moved to 100.  Few have achieved 1,000.

Huh, these things sound like they could be in a Dilbert cartoon.  They probably have been.

Here is today's Dilbert cartoon.

Analyst Roundtable: ARM in the data center

On Dec 19, 2012 10a will be a webinar discussing the ARM chip in the data center.  The webinar is here.

Power matters: using ARM to reduce data center costsA consumer using a computer to shop, email, search, or any of the other myriad tasks now possible, usually measures power consumption by the dollar figure on the monthly electrical bill. But as two recent, highly controversial articles in the New York Times reiterated, U.S. data centers backing up those tasks consume as much as two percent of the nation’s power consumption. Long before the articles appeared, data centers were aware of the problem and had begun employing various strategies to lower cooling costs, eliminate redundancies, and improve power usage effectiveness (PUE).

Another solution is deploying ultra-low power servers that reduce data center power needs – in a sense, reinventing the server. How does the efficiency of this solution stack up against the alternatives? What are some specific use cases? And, what’s the future for ARM-based server solutions? For answers to these and many other questions, join GigaOM Pro and our sponsor Calxeda for “Power matters: using ARM to reduce data center costs,” a free analyst roundtable webinar on Wednesday, December 19, 2012, at 10 a.m. PT.

I'll be on the webinar and Barry Evans from Calxeda.

Our panel of experts includes:

• Adam Lesser, Cleantech curator at GigaOM

• Dave Ohara, GigaOM Pro analyst and founder, GreenM3

• Simon Anderson, CEO, DreamHost

• Barry Evans, CEO, Calxeda

Think Different, Infrastructure as an executive position, example Google's SVP Urs Hoelzle

3 years ago I was introduced to how differently Google thinks of the word infrastructure when a Google guy I met said he worked on Google Infrastructure.  My context was from thinking of the definition.

Definition of INFRASTRUCTURE

1

: the underlying foundation or basic framework (as of a system or organization)

2

: the permanent installations required for military purposes

3

: the system of public works of a country, state, or region;also : the resources (as personnel, buildings, or equipment) required for an activity

So, he worked in the data center group.   No, he worked on Google Infrastructure.  Search - the underlying foundation or basic framework of the company.  Cities are built on infrastructure which is where we commonly get the use of the word.

The term typically refers to the technical structures that support a society, such as roads,bridges, water supply, sewers, electrical grids, telecommunications, and so forth, and can be defined as "the physical components of interrelated systems providing commodities and services essential to enable, sustain, or enhance societal living conditions."^[3]

Google goes far in its use of Infrastructure to the point where Urs Hoelzle says he is an Infrastructure Czar.

Urs Hölzle, Google’s infrastructure czar tells us what the Cloud really is and what it is supposed to do.

It was nearly five years ago when I last spent time with Urs Hölzle, Google’s infrastructure czar. (His official title is SVP of operations.) It was around that time he introduced me (and several others) to many of the concepts (such as cloud and big data) that are now part of the technology sector’s vernacular. Hölzle was company’s first VP of engineering, and he has led the development of Google’s technical infrastructure.

Hölzle’s current responsibilities include the design and operation of the servers, networks and data centers that power Google. It would be an understatement to say that he is amongst the folks who have shaped the modern web-infrastructure and cloud-related standards. When I had a chance to chat with him recently, my question was, “How do you define the cloud?”

...

Others might disagree, but Hölzle believes Google’s common infrastructure gives it a technological and financial edge over on-premise solutions. “We’re able to avoid some of that fragmentation and build on a common infrastructure,” says Hölzle. “That’s actually one of the big advantages of the cloud.”

Do you have an infrastructure czar or VP at your Web2.0, cloud company?  If not, you may have a hard time competing against those who have figured out how important infrastructure is.

Are you blind in the the data center world? You can't see and remember everything, so at times yes

If you asked an experienced data center person how many times a day they are blind to what is going on. They don't know. Why?  Because, you are asking them to see what they don't perceive, how many times you miss seeing something. 

i-Perception has a post on research done to discover the frequency of when people miss a fight.

If you don't think this research applies, then you are probably of a mindset that you have a photographic memory and can remember all kind of details.  But, it is impossible to have a perfect photographic memory.

The Truth About Photographic Memory

It's impossible to recover images with perfect accuracy. The myth of photographic memory.

By William Lee Adams, published on March 01, 2006 - last reviewed on August 07, 2008     

59-year-old Akira Haraguchi recited from memory the first 83,431 decimal places of pi, earning a spot in the Guinness World Records.

He must have a photographic memory, right? Not so. According to mounting evidence, it's impossible to recall images with near perfect accuracy.

When a professor studied Eidetic (photographic memory), he found they were not perfect.

Alan Searleman, a professor of psychology at St. Lawrence University in New York, says eidetic imagery comes closest to being photographic. When shown an unfamiliar image for 30 seconds, so-called "eidetikers" can vividly describe the image—for example, how many petals are on a flower in a garden scene. They report "seeing" the image, and their eyes appear to scan across the image as they describe it. Still, their reports sometimes contain errors, and their accuracy fades after just a few minutes. Says Searleman, "If they were truly 'photographic' in nature, you wouldn't expect any errors at all."

Now, you may think you are the exception, but consider this reason why we don't have photographic memory.  

Although psychologists don't know why children lose the ability, the loss of this skill may be functional: Were humans to remember every single image, it would be difficult to make it through the day.

And, even if you do have photographic memory, does everyone else in your data center team?

So, how many mistakes and errors in judgement are made because people are absolutely sure they saw something or sure that something did not occur, when in fact they are wrong.

Being wrong is painful, and the reality is we are blind every day.  Yet, how many systems, processes, and management decisions all make the assumption that you see everything and remember all the details. That everyone has a perfect photographic memory.

With the adoption of Mobile, real-time computing is an everyday occurrence

Real-time computing is typically thought of control systems for mission critical computers - airplanes that cant' fall out of the sky, nuclear plants, oil refineries, pharmaceutical manufacturing.

(Electronics & Computer Science / Computer Science) denoting or relating to a data-processing system in which a computer receives constantly changing data, such as information relating to air-traffic control, travel booking systems, etc., and processes it sufficiently rapidly to be able to control the source of the data

The desktop could do real-time things, but it wasn't designed to be a real-time computer.  Sometimes there are long delays where you get hour glass or spinning wheel. A real-time system was used because failure of the system to respond in an accepted amount of time was not acceptable.

With the rapid growth of Mobile and people's expectation of a good UI experience.  What app succeeds that makes users wait? or even worse wait longer at random times.  In the users eye, the app is broken.  That app will quickly lose users and fail.  Guess what users expect real-time response. 

I found this table of user response time.  The 0.1 second is a general rule of thumb.  But, what mobile users would wait 10 seconds?

able 7-1 Maximum acceptable response times for typical events

UI Event	Maximum Acceptable Response Time
Mouse click, pointer movement, window movement or resizing, keypress, button press, drawing gesture, other UI input event involving hand-eye co-ordination	0.1 second
Displaying progress indicators, completing ordinary user commands (e.g. closing a window), completing background tasks (e.g. reformatting a table)	1.0 second
Displaying a graph or anything else a typical user would expect to take time (e.g. displaying a new list of all a company's financial transactions for an accounting period)	10.0 seconds
Accepting and processing all user input to any task	10.0 seconds

And, does even 0.10 second feel too long.  If you are playing a game a 0.10 delay could totally change the game experience.

Guess what users expectations are that systems perform like real time systems.