Intelligent Systems

Volume III, Number 4 November, 1996

A quarterly newsletter for clients and friends of Chenault Systems

Visit Our New Web Site

We now have a small, but growing, really cool web page. Our full Internet address is:

New Area Code

Thanks to Southwestern Bell we have a new area code for our Carrollton corporate office. Our corporate phone numbers with the new area code are as follows:

Our prior area code was 214. This should be obvious, but there has been some confusion, especially for our out-of-state contacts.

Client/Server Systems

It seems that everywhere we have projects, meetings or making initial client calls, we are asked what the term "client/server" means. Client server is a sophisticated PC based system.. Client/server systems attempt to bring about the best of two worlds: the sheer control of mainframes, with the low cost, fast software development and ease-of-use of PC's. Client/server refers to the interaction between a workstation PC and a centralized database server PC. Like a mainframe system, client/server is capable of exerting strong central control of data integrity and security. These tasks are handled by the operating system (NT, Novell, etc.) instead of user applications, which has decreased the amount of programming involved. Since data is stored centrally, client/server enables the network administrator to back up work centrally and to perform periodic maintenance against data stored in a central and secure location. Since applications run entirely on the client (workstation PC) systems and only database requests are handled centrally (by the server PC), processor-intensive interfaces (Windows) are performed by the local processors and local memory. Client/server is particularly efficient when handing ad hoc reports (or queries). A more traditional file/server system often responds to simple requests by retrieving large amounts of ineffective data. A client/server systems only returns those records you requested.

Client/server systems are relatively new. They evolved from file server systems, which have been around for over 10 years now. Client and file servers were born out of a need for lower cost computing compared to host (mainframe or mid-range) based computers. Mainframe and mid-range computers have provided dependable performance, but at an immense cost. Mainframe and mid-range purchase prices are enormous compared to PC servers, but the largest costs are annual maintenance fees. The "performance/price ratio" for today's Pentium based server is far larger than processing cycles for the traditional mainframe or mid-range.

PC server based computing came about because of organizational reasons. Mainframe costs from centralized MIS departments were charged to user departments such as accounting, engineering, human resources, manufacturing, etc. People were forced to wait in line for high cost computing, which created the need for competition for the MIS department. This necessity was largely responsible for the creation of the desktop computer, which led to networks, file/server and client/server. In the early 1980's, some large company MIS departments actually outlawed the PC. That was short-lived because employees just turned around and bought these inexpensive machines on their own. Competition from local area networks were shunned as well, but they are now well accepted.

Therefore, the real problem with mainframe or mid-range processing has always been the huge backlog of applications waiting to be addressed by the internal MIS area. Early PC users decided to build their own applications; they were sometimes clumsy, but easier to understand than mainframe applications. End users found they could get things done faster with a PC than having to fill out the forms requesting service from the central MIS group.

It could be said the client/server movement started as a "grass roots" interest. It was pushed upon many companies and MIS organizations were caught unaware by computer literate end-users. The movement began in the mid-80's and accelerated rapidly in the late 80's and early 90's. Client/server was as much a "declaration of independence" from MIS, as it was a new technology.

Sometimes client/server implementation were overdue, over budget and fell short of expectations. The first users were experimenting without a road map for success. Today, most MIS groups have become closer to the end users in the wake of this unmanaged growth and are performing more service and with control. The customers (users) are now setting policy. MIS organizations, with the blessing of senior management, have the opportunity to deploy new client/server technology with an understanding of the following guidelines for success:

• Develop a plan. Make sure there is a good design to minimize network traffic and segregate processing between the client and server. As many graphical Window applications as possible must be kept on the local PC and kept off the server (client). Multiple Windows applications, with multiple users on a busy network, can cause serious degradation and slow down any system. Make sure at least 40% of development time is allocated to testing to avoid unpleasant surprises. Client/server systems must be properly implemented or face inevitable political opposition.
• Recognize that the client/server movement was a non-MIS circumstance. MIS groups who push greater user computer literacy will experience less pain during the technology changes.
• Understand that whoever is in charge of implementation must have maximum authority to complete the project (that's why you hired him, remember). Too little authority can mean failure, with the blame going to the wrong person or group.
• Listen to the "renegade power users". They were the ones who probably started the revolution in the first place by circumventing MIS policy and provoking change. Learn which one of these individuals can provide valuable input to the project.
• Stay away from the "corporate strategy" manifestation (paralysis through analysis). Overall corporate wide strategies are fine. However, when the project is just beginning, they can discourage the action oriented behavior that we all want in a business. Also, compare your organization's technology to your competitors.

Summary

The main issue behind moving to client/server is profitability. Mainframe and mid-range hardware and software are expensive to buy and keep. Mainframe and mid-range maintenance cost and large MIS staffs are enough to make CEO's see red instead of black. The answer is not constantly re-organizing the MIS area; real leadership involves constantly re-thinking systems with objectivity and an open mind.

 "We trained hard.., but it seemed that every time we were beginning to form up into teams, we would be reorganized... I was to learn later in life that we tend to meet any new situation by reorganizing; and a wonderful method it can be for creating the illusion of progress while producing confusion, inefficiency, and demoralization." -- Petronious Arbiter, 210 B.C.

E-Mail: Chenault Systems,Inc.

Copyright © 1998-99 by Chenault Systems, Inc.
All rights reserved.
Click here for additional legal and trademark information.