Blade Watch

In the olden days, London Windows Support looked after London servers. New York looked after New York servers, and so on, the lines or regional demarcation were set. The problem with this is as follows:

• Inefficient use of resources
• Poor global support
• Everybody thinks local – that’s not how we do it here.

As business needs grew, this model became redundant in some of the large banks, some of the IT departments decided to operate with the business lines in a follow the sun approach. This being that the infrastructure support, the IT follows the sun, however is up, supports the systems, however is asleep does not. The idea being that a server failing at 3am London time should not mean that we need to get a London server engineer up, firstly the New York engineer, can log on see what’s going on and attempt a fix, escalating to London if necessary, key to this is an effective operations team, effective dialog between the teams, and understanding each regions way of working, until we can move towards a state where a server built in London is identical to one in France, one in New York etc.

Related posts:

1. Defining our support model is our business I’ve been speaking with Chris over the last few days...
2. Stabilize the core and everything will follow By Jake Sorofman Oracle’s bid for Sun has officially sucked...
3. What’s in and out of support Within the realms of IT, there is often the phrase...
4. HP Proliant Support Pack 8.30 HP HP Proliant Support Pack for Microsoft Windows Server 2003...
5. IBM helps bank reduce its support costs Business News RALEIGH, N.C.–(BUSINESS WIRE)– Red Hat (NYSE:RHT), the world’s...

Related posts brought to you by Yet Another Related Posts Plugin.