Discussion Locked

IT Infrastructure? Why does this always

0 helpful
23 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I know that this is not necessarily the question but it is something I would like to discuss. I came across this report detailing out the following:"Robust Systems are Built from the Bottom Up"
...Information technology infrastructure takes a backseat to applications investments for lack of a cost justification method. However, the infrastructure systems are breaking down in public; bringing significant attention to an issue that has been set aside far too long.

It is quite the thought provoking report. Enjoy, oh fyi, I had to register but it was free.Cheers. Matt

http://216.95.253.70/Research/ResearchHighlights/ExecutiveView/2000/04/research_notes/MI_EV_JFD_04_00_1.htm

23 replies

by duncan_sargeson

It's not that it necessarily takes a back seat - it's just that people don't want to pay for it, as, in my experience, it costs shedloads of cash.
Within my company there is no easy way to make departments pay for infrastructure, so the IT department has to pay - which, when you consider that IT is generally thought of as a major cost centre - just makes IT look more expensive than it really is.
Given that I reckon at least 80% of large businesses couldn't function at all without IT, the business users should understand that paying for infrastructure is a necessary evil, without which, they'd probably be using paper and pen again...

by angelo

I believe that it takes a "backseat" in the minds of the comptrollers and accountants because there seems to be no way to directly bill costs. We have been buildin ginfrastructure one system at a time for close to six years now. It is a measured approach and we over-engineer to be able to handle additional load.

by wayne m.

The problem with IT infrastructure is that at its best it is invisible. It only becomes visible when there are problems. It is much easier to quantify added features than lack of failures.

Probably the best approach would be for IT to track help desk calls and system outages like manufacturing plants track product failures and rework. It would take a very brave manager, however, to actually publish these numbers and give everyone a true understanding of the real state of the IT infrastructure and an understanding of what the IT staff really does.

New features are obvious. Making system failures (and the solutions) obvious is risky. If IT is blasted for problems, then everyone just plays the game of pretending nothing is wrong,and therefore the IT staff does nothing. Let's publish our true problem rates and get some recognition to the heroic efforts of the IT staff to resolve them.

by amartin

In the simple minds of the TOP's, it is best to show them who is really in control the structure of data. By writing in blank Time and underwriting down time with cost savings or even just Down Time will bring the Elite TOP's to agree it is necesary. For IT to put it in the Backseat is a failure on them. Each system is a copy of them and who they are. One bad report up front will sit the TOP's in thier place. I have Done this and every time it works or I simply under write the time in. At the end of a Job I do an After Action Review in which I give the TOP's a copy of the Job & Information of the infrastructure update. I never once have any of them complain about the bill, but did ask why no one else ever do this before. The AAR does wounders. Preplaning Proactive Strike Paper "PPSP" is the next step for my operation.

by mcse lee

Our CFO is one of those types - unless you can show defined cost savings (or better yet revenue increases), you had better not even mention infrastructure upgrades to him. Until, that is, something breaks down and the whole operation comes to a grinding halt - then it's my fault for not keeping the infrastructure up to date.

It costs more to repair the broken system(s) than it does to keep them from breaking, but how do you convey this to the "check-signers"?

by mark.l

Ahhh, the age old question. I've been around a while and this has always been an issue. I'm in agreement with some of the other responses in that IT departments have usually been regarded as cost centres only - something like a big accounting machine and/or a big filing cabinet. This is partly the fault of the IT executive for being complacent with this viewpoint. I.T. must be viewed as having some strategic business value.

Instead of huddling in the basement as a separate department, with no contact with the real business, there should be an IT component with every business unit. Only then can the techie-types begin to learn the business and advise the best way technology can provide value.

E-commerce and other technologically dependent business initiatives will change this in a big way, and very soon. To implement E-commerce effectively, you have no choice but to understand the business needs and customer's needs. Then IT can be a proactive partner in building the revenue generating aspect

by bob.bagheri

As a Sr. Network Analyst, I agree with most of the answers. But where I usually find the problem is that no one takes the time to fine tune the existing equipment to make it last 2-3 years. Every IT person wants the latest and greatest and most ofthem justify bandwitdh problmes with one solution, UPGRADE. Business leaders don't want to hear that, becasue they heard it a year earlier from you or the last IT person. Also, network equipment is behind the seen, and doesn't get the same attention as developers or LAN equipment does. Therfore, it is up to the IT staff to measure bandwidth usage and build a baseline measurement to take to management as the users outgrow the existing equipment / pipelines. IT people need to think like business people if they want the recognition they deserve.

Re,
Bob Bagheri

by al macintyre

Y2K may change the age old patterns.
Y2K forced upper management to take a hard look at the degree to which their business depended on technology whose management decisions they had seriously dropped the ball on.

e-stuff may also change age old patterns.
e-projects are falling flat on their faces in many companies because they are exposing security that is a joke & legacy systems that do not work very well.

What was good enough in the past is not good enough for the future. Pretty soon, if a company is still in business, hassles with computer security, Y2K, and e-commerce will force management to take IT infrastructure more seriously than they have justified in the past.

by georget

It's always so easy to point the finger at the CFO, the CEO, or anyone else available, when in fact the fault lies within IT.
We have to lead the change, champion the strategy and establish new partnerships within our organizations.
We have to share! We have to change our approaches to the application life cycle.
We have to communicate effectively. We have to manage relationships.
We have to develop consensus, eliminate the "battle mentality", recognize excellence and accept reasonable mistakes.
If we want management to accept our future IT infrastructures, we have to show results.

by mikej

I see several reasons:
* Communication. IT staff have a hard time communicating to non-IT people who control the funding what a "good" infrastructure means. They see what they have now works, so they don't see a problem. It's hard to translate well performing infrastructure into ROI. It can be done, but most people don't seem to take the time (see staffing below).

* Staffing. Staffing is often lower than desired, so the existing staff is spending more time putting out fires in the broken infrastructure, instead of proposing a new one to fix the problems long term.

* Time to Market. Combined with low staffing, other than putting out fires, existing staff are implementing the next major functionality to be first to the market. This is even more of a problem with ECommerce companies. They see the direct impact of getting something implemented first. They don't see the direct impact of fixing what already exists (and seems to work, even though the IT staff is working themselves to the bone to

by donq

Reading many of the above answers amazes me!

Database structuring lies at the heart of ANY business application operating on any ODBC database product within ANY operating system. As an executive defines his/her job the "nouns", "verbs", and "adjectives" make excellant database Table candidates. 1 subject per table! Records represent subject instances where Fields store related Facts. Hungarian Notation does NOT support normalized data modeling intuitively yet everyone continues usingit?? Contact Don Quigg at databyte@mindspring.com for literature defining Business Notation and the software that creates a normalized gleaning management defined explanations of what they need.

This discussion is closed to new replies.