Keystones and Rivets

Auditing IT systems

“Yip, I’ve been promoted and I’m off to New York in a few weeks”, said Big D.

The other day I was chatting online with a former colleague who now works for a business process outsourcing company specialising in corporate information solutions.  He told me he is going to be a new Director for the US, focussing on Strategic Solutions for the Americas.

I made the critical mistake of shouting this news down the corridor to my business partner Fergus.

“Start spreeeeading the nyoooosss, Haaam leevin’ tooodaaaaaayyy...”, he wailed.

Throughout my career, in each office or location, there has always been at least one person who was convinced, despite the reactions of their ‘audience’, that they are a good singer.

Fergus is very convinced.  And very loud. 

The window in my office was open.  Outside, I could see squirrels throwing themselves off the oak trees.

The Pebble grimaced, and, above the racket, cried that it sounded like, “someone smothering a crow with a whoopee cushion.”  Mercifully, he forced shut a couple of doors and calm was restored.

“The guys say ‘well done Big D’”, I typed back.  Our chat continued.

“Thanks to all...what are you up to today...when’s the next blog coming out, what’s it going to be about?”

“I’m working on it now.  It’s about systems... how traditional functional systems don’t fit with the business process view of an organisation.”

“Really?  I was just in a meeting about that very subject.  We take a look from the business process perspective, and it always spans lots of IT systems. The boundaries round processes are completely different to the demarcation between IT Systems...So why are you doing that one?”

I went on to explain that I’d been following a series of posts by bloggers Dennis Howlett and Francine McKenna about IT systems, auditing and the Big Four…

IT (still) exists for one reason

The Pebble groaned.  “Another big 2.0 conference is coming up...I’ll be reading about it for weeks.” 

My non-tecchie colleague, who freely admits that the average pebble possesses more IT knowledge than he does, spends a few hours each day trawling various media for news and information of interest to our company.

Something he hates is anything ‘2.0’.  “Who comes up with this junk...is the pen the pencil 2.0?”, is a rant I’ve heard on more than one occasion.

The other day he was scanning a few blogs and I could tell he was going he let rip once again.  It was like watching and listening to a volcano in the hours leading up to an eruption. 

“All the usual rubbish”...‘uber’...‘paradigm shift’...‘3.0’...“THREE point oh?!! - you have to be kidding me!”  At this point various items of stationery went into orbit.

After I’d stopped laughing and he’d calmed down he said, “Why don’t we set up a 2.0 Skeptic blog?”

“One blog is enough to be getting on with, thank you very much” I replied.  But I could see his point. 

The name The Pebble chose for his proposed blog was inspired by the blog of the IT Skeptic.

Cloud Computing

LUNKWILL:  Are you not as we designed you to be, the greatest, most powerful computer in all creation?
DEEP THOUGHT:  I described myself as the second greatest …Deep Thought… and such…
LUNKWILL:  Yes yes but…
DEEP THOUGHT:  …I am.
LUNKWILL:  But, but, but - this is preposterous! Are you not a greater computer than The Milliard Gargantu-Brain at Maximegalon, which can count all the atoms in a star in a millisecond?
DEEP THOUGHT:  The Milliard Gargantu-Brain, a mere abacus. Mention it not.
FOOK:  And are you not a more fiendish disputant than The Great Hyperlobic Omnicognate Neutron-Wrangler? Which can destroy -
DEEP THOUGHT:  The Great Hyperlobic Omnicognate Neutron-Wrangler can talk all four legs off an Arcturan Mega-Donkey but only I can persuade it to go for a walk afterwards. Molest me not, with this, pocket calculator stuff!
LUNKWILL:  Then what's the problem?
DEEP THOUGHT:  I speak of none, but the computer that is to come after me.

(The Hitchhiker's Guide to the Galaxy)

Nick Carr recently commented on IBM's new initiative called Project KittyHawk, which sets out to use their Blue Gene technology.  The project aspires to create a “global-scale shared computer capable of hosting the entire Internet as an application”.

There have been a range of online discussions on the back of the article as, once again, Nick Carr manages to hit more than a couple of raw nerves.

The premise of the article is that IBM Blue Gene technology is creating computers of such power that data centres can offer vast amounts of  computational power that businesses can plug into and use according to need at a particular time.

These supercomputers can emulate many individual smaller servers (virtualisation) so businesses can migrate their IT services to this new model.

Rather than data centres just offering a place to put your own servers, they can start to offer virtual servers or services, enabling new business models to be adopted.

The IBM technology is so fast that Project Kittyhawk can emulate the entire internet. 

Understanding and Valuing Data Flow

My business partner, Fergus, and I were on our travels last week around the UK.

We used a couple of planes, a few trains and an automobile.

For a change, the journeys on the trains and the planes were smooth and on-time.

The car was a different matter though.

We hit a number of traffic jams that delayed us quite a bit.  The worst was on a motorway near Leeds where we sat without moving for well over an hour.  A truck had over-turned and stopped the flow of traffic.

During our fifth game of “I Spy” we got a call from The Pebble, and explained our situation.

“You know what?  That reminds me of our discussion the other day about network routing”, he said.

“The motorway is just like a cable and you are sitting there like little packets of data when a server goes down.”

I could tell he was taking a little pleasure in our predicament.

“Well, networks don’t quite work like that...”, I began to reply.  Mercifully, another call came to my rescue before I had to go into the intricacies of communication protocols between hosts.

Eventually we got going again and during the next couple of days met a few companies, each working in different industrial sectors.  A regular topic in our discussions was how data flows through and across an organisation – and more importantly, how it is documented and portrayed to non-technical stakeholders of that data.

To investigate, analyse and communicate the data flows, some of the companies had Systems Analysts who used formal Data Flow methodologies such as Yourdon/DeMarco, SSADM and Gane-Sardon.  Others had only basic Visio diagrams to try to document how applications and functions within those applications interfaced with other applications.  Some companies, however, had no documentation at all.

Governance and Government

We weren’t sure whose chin hit the floor first.

“He did say 25 million, didn’t he?” asked The Pebble.

“Yip”, I replied.

We had just begun watching a news broadcast about the latest data security breach by a British government department, Her Majesty’s Revenue and Customs (HMRC).

25 million personal records, including the banking information for every family in the UK with a child under the age of 16, had been written with only password protection onto two CDs which were subsequently “lost in transit”.

The UK Prime Minister, Gordon Brown, said that the security breach was down to “Failure in implementing the proper procedures.”

He went on to explain that:

1. “Only authorised staff should have access to protectively marked information”
2. “Information must not be removed without appropriate authorisation”
3. “Encryption should be used whenever information is being sent”

Nuts and bolts and dataflows

“Morning…guess what?  The Bengals won yesterday”.

The Pebble loves American Football.

At this time of year, his mood on a Monday morning isn’t difficult to gauge.

If he starts to talk about his beloved team from Cincinnati, we know they won the night before and he is a happy man.  If he doesn’t say much about anything until lunchtime, then it’s a sure bet that they lost.

Mondays mornings have been a bit quiet lately.

This week, though, he was in high-spirits.  Not only had his team beaten “The Ravens”, he told us, but he had won the grand sum of £5 by betting on the match.

“All the drinks are on me”, he laughed.

We could hardly contain our excitement.

When indulging his gambling vice, The Pebble uses something called a betting exchange.  These exchanges are peer-to-peer websites that act as brokers between people who, instead of trading stocks or commodities, trade odds on the outcomes of sporting events.  The sites earn revenue by taking a commission from each winning bet.

Trying to cross No Man's Land

The Pebble and I work well together.

But he is an Arts graduate, so I have to humour him from time to time.

This entails having to listen every so often to one of his “stories” about history or politics. 

Today, for some reason, he decided to explain why the Red Army initially collapsed during the German invasion of Russia during 1941. 

“Barbarossa”, “Lebensraum”, “OKW”,  “Timoshenko”, “Smolensk”, “Stavka”…

The Pebble often talks about interesting things but occasionally he uses too much terminology.  As is sometimes the case, after a few minutes I felt my eyes glazing over.  My mind started to drift into that strange state where you feel conscious and unconscious at the same time.  The lights were on, but there was definitely nobody home.   

His talk about matters military must have had some impact though.  Through the haze I began asking myself - when did IT last go into battle with a genuine understanding of what the business was trying to do?

When did Business and IT last plan together strategically, agree tactics, and march together with clear objectives?

How about ten years ago...?

If IT does not alter an outcome, its role is meaningless

This evening I was doing battle with a mountain of post that would rival Everest. It wasn’t physically the same size, but I felt like it would take about the same amount of time to conquer. I was just about to set up base camp in some utility bills, when my daughter called to me to tell her a bedtime story.

“Here's a quick one.  An oyster went to a disco and pulled a muscle”, was my reply as I got up to go and see her.

“No Dad. My English teacher says a story should have a beginning, middle and an end. That was just a beginning and an end.” shouted my son from across the hallway.

That’s what we were all taught in school. Everything should have a beginning, middle and an end.

Well, story time is over and I've started thinking about how everything can be described in those terms - a beginning, middle and an end. It doesn’t matter if you are making a meal, driving a car or dealing with your mailbag - everything starts, goes through a process, and completes.

Those of us in the IT industry tend to think about IT systems as possessing these same qualities. We iteratively break down complex tasks into sub tasks, each of which accept input, perform computation, and returns results. So this concept is not new to us. But the tendency is to focus on the IT systems and how they work, rather than why the IT system is used. This internalised perspective, although understandable, is a huge mistake which hinders how IT is perceived by its clients – the business.

Feature: IT exists for one reason

Never underestimate the degree of clarity that a fresh pair of eyes can bring to a complex situation.

Late one Sunday night a few years ago, my business partner and I were discussing the Oil & Gas markets our new IT company could service.

In particular, we were discussing how to best use IT to maximise the financial value of a) the oil and gas products flowing through a refinery belonging to one of our clients, and b) the huge quantities of data used by the business.

We had many ideas about creating applications to provide a joined up view of how the exploration and manufacturing businesses interacted, but we were struggling to define an appropriate methodology that would put IT in a business context.