Article 46. Why some Computer System Implementations Fail.
Computer system implementation failures are of two types. In the first the systems never get completed through faulty planning and software development or the funding runs out before programming can be completed. In any case the system does not get implemented. In the second type the systems implementation plan was flawed from the start but the system gets completed yet fails to function, as it should. As an example for the first type a mid-west state’s auditors found a large number of computers in a rented storage locker. The computers were what were left of a botched attempt at automating the states drivers license offices. When the software development failed the computer hardware was hidden away in the storage locker. The new incoming governor dispersed the computers where they be could be best used throughout the state.
A second example is the inability of the FBI to get its new computer database to work. This is what I would call a double failure for even if they did get the system to work it can’t be integrated with the CIA’s database, which does work. In the mean time tax dollars continue to be poured into this failed system. The reason why they can’t adopt the CIA’s software is probably because bureaucracies have pride and they don’t admit failure easily.
System implementation planning failures are generally the fault of the CEO funding the project. It wasn’t but a few years ago when almost none of management in private companies and in government had any computer experience at all. They relied completely on their Information Resource Manager (IRM) for planning and implementation of computer systems. IRMs usually have a large computer programming staff which they want to keep busy and are willing to start programming the minute they get the go ahead.
Among computer literate personnel an organization’s computer department is known as an IBM “shop” or a Digital Equipment “shop” meaning that the organization only uses a specific type of computer hardware. It also means that only IBM or Digital Equipment software is used. When the IBM Operating System software is used all Application Programs are written to run on it. What this means is that if the organization only has IBM computers you will probably get an IBM solution. And you are unlikely to get a system that can be integrated with other non-IBM systems unless specifically requested by the CEO. What I have observed is that most IRM managers are more loyal to their “shop” whatever it is than they are to their own CEO. You can test this by sending someone to meet with your IRM who causally suggests that he should purchase a computer from another company and see how long it takes the IRM to come pounding on your door.
Systems integration is achieved when separate databases for storing data are created using the Structured Query Language (SQL) database language. This allows IBM Digital Equipment and others using SQL to access the databases. The process works this way when an IBM application program needs to retrieve or store data it uses an SQL request to find or store the data. A Digital Equipment computer can also retrieve and store data in the same database. This is the same database structure used on the Internet and allows queries to be made easily without having to write a program for the query. The FBI and CIA databases do not use SQL probably for access protection. For more information on computer systems see the following: Reader Question 5. “Efficiency and Automated Systems”, Article 21.“Centralized Purchasing- The Best Way to Balance State Budgets”, Reader Question 6. “How do you implement a Statewide Purchasing System?” and Article 28. “Making Centralized Purchasing Work using Aggressive Negotiation”. Also see Article 101. The Hampton Virginia Innovation Story, Article 102. Government Reform of California Agencies and Commissions and Article 120. Collaborative Innovation between States and Federal Government
