Thursday, February 02, 2006

Orphaned Systems

In most large enterprises, as in societies at large, one will find on occasion a system that seems to have to owners. It exists by itself, at times, in its own little world. The users of this system are few and far between. Yet an assessment of the system indicates that all is well with it. Indeed you might open the door to its room and find neat stacks of voluminous documentation sitting next to an array of playfully sparkling LEDs. Even more intriguing is the fact that its users seem perfectly happy with it save a few minor complaints.

"Its printer sometimes does not work, but if I reboot it all works well again" says one. "I remember it taking a long time to print the cash ledger report", says another. Walking around to a graying technician who seems to find enormous gratification in greasing a flange, you might even hear the systems pedigree. The technician might furnish you with its history, in a voice that conveys the pleasure of one willing to impart information to any willing to listen. "The system is more than seven years old", he will probably tell you. "When it was first installed I remember they had a small party at the shop, in bay three. They don't have those anymore ... too much cost cutting." He then mentions the name of a fancy consulting firm and a equally well known vendor that were responsible for installing the system. "They charged more than a million bucks to put it in" he said. "Indeed everyone at the shop used to use it. The administrator used to be a Russian chap...very smart." He then shrugged.

Your architect hat goes on, and every circuit in your consulting brain lights up. History, you remind yourself, provides a chronological context of a system. Indeed it can be as valuable as your current state assessment. You warm up to an enlightening conversation and poke and prod with questions that are open ended enough to elucidate a response from the gentleman. He looks at you and cocks his head in askance. He inquires of your origins and without waiting for an answer, as if to disabuse you of any notion that his query implied negative connotations, he continues, "Smart guys! Are you going to fix the system?"

You hastily correct his incorrect assumption, not wanting to raise any expectations. "No", you say, "I am here to understand what it does. Do you know if there is anything wrong with it?"

He shrugged. "No one uses it nowadays", he said tentatively. "Till about four years ago, there used to be a lot of people running around that room. Now hardly anyone seems to use it. At the end of the quarter and year would be the time when it would be the worst."

"Who repairs the system?" you ask eagerly. He pauses, thinks and then says "I do not know. I don't think it has needed any repairs". His demeanor becomes more distant as he reaches the limit of his knowledge.

You then head over to the head of the department who has a large sign above his door saying Manager. The sign laid greater emphasis on the title than the name of the person and sought to lend gravity to it in this manner. You glance at your watch, it is time for your meeting. A brief sharp knock followed by the usual formalities sees you seated in front of a beaming middle-aged man multi-tasking between his phone, brunch and email. The sandwich disappears rapidly and having dispatched the email and hung up the phone you get his undivided attention.

Half an hour later you leave with the knowledge that the system still works, the administrator left a few years ago and that due to budget constraints no system maintenance or upgrades were performed for the last three years. So then why does not one use the system, you wonder.

(c) 2006 Vivek Pinto For more details please visit us at Wonomi Technologies