lib-MOCS-KMC364-20131012113323 velopment, which has recently seen the im- plementation of a new batch retrospective- conversion subsystem, and added COM catalog options and online authority verifi- cation during input/edit. While not the only bibliographic system to be successfully replicated, the WLN Computer System is becoming the most sys- tematically replicated main-frame facility, with a broad range of future possibilities, including that of a truly turnkey system. WLN's experience indicates that, if a sys- tem is designed for ease of maintenance at perhaps some sacrifice of efficiency, it will be readily transportable and allow others to obtain the benefits of a highly sophisticated bibliographic capability without the ever- increasing cost of original development and, more importantly, without having to support the ongoing maintenance of a unique system. A General Planning Methodology for Automation Richard W. MEYER, Beth Ann REULAND, Francisco M. DIAZ, and Frances COL- BURN: Clemson University, Clemson, South Carolina. INTRODUCTION A workable planning methodology is the logical starting place for the successful im- plementation of automation in libraries. An automation plan may develop on the basis of an informal arrangement or from the ef- forts of one individual, but just as often, automation plans are developed by com- mittees. An automation planning commit- tee must determine and execute some kind of planning methodology and is more likely to be successful if it starts with clear guide- lines, good leadership, and a thoroughly proven approach. As a summary review of the literature will bear out, many libraries have devel- oped their own planning techniques in- house. Some of these, which are addressed to the issues of cataloging rule changes and public-access catalogs, have been very well thought out .1 However, these techniques are generally not directed to planning for Communications 205 library-wide automation, and are usually designed to meet the specific needs of an individual library. Although the pattern for these studies is often similar, they do not seem to be based upon any general automa- tion design methodology. Neither, in addi- tion, does there seem to be a general meth- odology available through any external library agency. The Office of Library Man- agement Studies of the Association of Re- search Libraries has developed a number of programs designed to assist libraries with their planning efforts, some of which ap- pear to be useful in automation devel- opment. 2 But for many libraries, these pro- grams may be too broad, too time-consuming or too expensive. As an al- ternative, some libraries will need to look elsewhere for a general automation plan- ning methodology. This problem was ad- dressed by the administration of the Clem- son library, and was resolved in a unique way. BACKGROUND The Robert Muldrow Cooper Library of Clemson University has the responsibility of acquiring, preserving, and making avail- able for use the many materials needed by faculty and students in their research and instructional efforts. At a typical land- grant institution like Clemson, the amount of scholarly publishing and the pressure to develop research proposals has risen sharply in recent years . The increased needs of users working with an expanding and diversified collection have resulted in a doubling of cir- culation activity, and have required the growth of library staff by 70 percent over the last decade . Furthermore, acquisition, processing, and access problems are com- pounded by the high inflation rate of mate- rials, particularly serial publications, and manpower costs. Even though user demands heavily bur- dened the traditional manual systems, the extent of library automation at Clemson had been limited to a batch circulation sys- tem, a simple serials-listing capability, and the use of bibliographic utilities. Although it had been generally accepted for some time that the acquisitions and fund-control functions at Clemson were in need of auto- mation, no concrete approach to develop- 206 Journal of Library Automation Vol. 14/3 September 1981 ing a system had been established. In addi- tion, there was some concern that the development of an automated acquisitions system shouldn't be initiated without a clear understanding of how such an effort would affect the rest of the functions in the library. With this in mind, and as an initial part of planning, the library administration decided to implement a programmed study to determine specific needs and problems of the whole library at Clemson and to deter- mine the attendant costs and benefits of their resolution. Since developing the meth- odology for this kind of study effort in- house has been shown by experience else- where to be both expensive and time-consuming, a planning methodology was sought which could be brought in from outside the library and applied in a timely fashion. The International Business Ma- chines Corporation (IBM), through their local marketing representative, volun- teered to supply that methodology by means of an Education Industry Applica- tion Transfer Team (ATT} study. In order to implement the study, a team was orga- nized consisting of representatives from the library, from the university's Division of Administrative Programming Services (DAPS), and from the IBM Corporation. The purpose, approach, and results of that study constitute the rest of this paper. PURPOSE The Application Transfer Team method- ology was implemented to fulfill a fourfold purpose. • First, it was necessary to act on the rec- ognized need for a library-wide automation plan with something tangible that library and university administrators could use in the decision-making process. • Second, basic objectives and imple- mentation estimates were required to pro- vide groundwork to the development of sys- tems specifications and evaluation. • Third, the planning process needed to provide a forum for meaningful participa- tion by a number of library staff and users. • Fourth, the planning needed to be ac- complished rather quickly. The ATT met all these requirements. Al- though the ATT study technique is general- ized for work on any problem in the educa- tion arena, it seems particularly well suited to the library environment because it is ori- ented toward developing applications that solve production problems. The Application Transfer Team method- ology was developed by the IBM Corpora- tion for customer use. The A TT methodol- ogy evolved from IBM's Business System Planning Function, which has been opera- tional since the early 1970s. Although the methodology has been used several times in the academic environment, this is the first time, to our knowledge, that it has been used in a library operation. The strength of the ATT is that it helps members of a team with diverse backgrounds to understand the environment under study. Its final goal was "to improve operational productivity, pro- vide better service to students, and provide information which can enhance manage- ment planning and decision making."3 Put to work, the methodology is straightfor- ward and effective. From beginning to end, the A TT process took Clemson slightly more than three months elapsed time. Total work time (including all report writing) for library staff was approximately one thou- sand man hours. As the initial step with the A TT method- ology, it was necessary to engage a sponsor and to select a team . For this study, the sponsor chosen was the dean of graduate studies, who reported directly to the vice- president for academic affairs. In turn, the director of mmpnting and the director of the Division of Administrative Program- ming Services (DAPS) reported to the dean of graduate studies. Although it was not critical that the sponsor be intimately in- volved in the project, his level of authority within the university administration would help to secure acceptance of the study's rec- ommendation. The sponsor also provided cogent advice along the way, based upon his understanding of institutional resources, and he served as a communication link with other university administrative offices. The study team was chosen by the library administration with the intention of getting diverse involvement and expertise. Library staff included the associate director, the head of circulation, the serials cataloger, and a reference librarian. Although only the associate director brought significant - experience in library automation develop- ment, the head of circulation contributed substantial practical experience with auto- mation systems. The cataloger offered spe- cifics of bibliographic problems, cataloging rule changes, and serials control issues, and the reference librarian contributed a com- prehensive knowledge of information- retrieval concerns. Outside staff included the director of DAPS, who furnished details on the Clem- son computing environment, and an IBM marketing representative, who provided appropriate help with hardware capabili- ties, the ATT metnodology, and legwork. In addition, Clemson was also able to en- gage the help of a representative of IBM's Education Industry Division to guide the A TT efforts on the basis of his experience in the use of the methodology. From time to time, other IBM and DAPS staff were in- volved in assisting with interviews and re- port writing. The associate director served as team chair in order to act as spokesper- son, to coordinate team effort, and to edit the final report. METHODOLOGY The Application Transfer Team method- ology is applied in six phases. IBM recom- mends that these phases be conducted se- quentially, and that they last from five to sixteen weeks, depending on the size of the problem. Throughout the process, verbal reviews were conducted by the team with the sponsor and with the library staff. The first phase involved an organiza- tional session. Following the introduction of team members, the IBM Education In- dustry Division representative presented an overview of the methodology and explained the mechanics of the A TT study process. The team then established the scope of the study by choosing an application area on which to focus and by determining the gen- eral objectives of the final system to be im- plemented. Since part of the purpose of the project was to develop a plan for library- wide automation, it was quickly recognized by the team that the application area should be an integrated library information sys- tem. However, the IBM representative sug- gested that this scope was too broad for the study and that one functional area such as Communications 207 acquisitions be chosen, with other functions reserved for subsequent ATT studies. Given time constraints, a compromise arrange- ment was made in which serials control was determined as the scope. Since serials con- trol is a single functional area, but encom- passes nearly all bibliographic issues, it served as a microcosm of overall library op- erations. Therefore, it was generally ac- cepted that a plan that effectively accom- modated serials would constitute an integrated system plan. The organizational phase continued by determining who to in- terview during the data-collections phase and by setting up an interview schedule. This phase was concluded by developing an outline of the final report and by assigning writing responsibilities to individual team members. The data-gathering effort constituted phase two. This involved structured inter- views of representative staff of each unit of the library who were involved in routine interactions with any phase of serials con- trol at Clemson. Interviews were conducted with staff from acquisitions, cataloging, circulation, reference units, and branch li- braries as well as the university business of- fice, students, and faculty. Following an outline in the ATT, each person interviewed was asked for specific details of his work with serial publications regarding (1) interfaces (or points of inter- action), (2) concerns or needs, (3) suggested improvements, (4) expected values or bene- fits of improvements, (5) work volume, and (6) cycles. Data gathered in each of these interview sessions were immediately docu- mented in a letter to the interviewees. These letters were reviewed by those interviewed for corrections and adde::tl delail. Data from completed and documented interviews were consolidated during the third phase of the study into a matrix of each of the six questions plotted against op- erational areas of the library, graphically designating areas of the greatest concern to the largest part of the library. This compos- ite was analyzed to separate problems that could be reasonably handled by an inte- grated automation system from those that needed the attention of administrative pol- icy and direction. Functions for automation consideration were then examined in a 208 journal of Library Automation Vol. 14/3 September 1981 "blue sky" session of the committee to envi- sion what system would accommodate the specifications for serials control and access that each library unit and serials user re- quired. From this session a synthesis emerged of the architecture for an inte- grated system. 4 This architecture included a description of the basic relationships of functional modules of the system, a list of the various files needed to contain system information, and a list of data elements re- quired for bibliographic holdings, acquisi- tion, and patron records in the system data- base. Phase four called for the translation of the architecture and general system re- quirements into modules on basic access, acquisition or processing functions, and into the individual programs needed to exe- cute each module. The team divided into two parts. The IBM and DAPS personnel, with the associate director, listed the mod- ules and programs and formulated descrip- tions of each. Part of the description effort involved drafting approximate flowcharts of each program. Using algorithms devel- oped by IBM, these descriptions were used to assign estimates of person hours required to create the necessary modules. In order to determine the overall cost of system devel- opment the person-hour figures were con- verted to dollars using an average hourly cost for Clemson DAPS personnel. Committee members not involved in program/module design formed a group to evaluate anticipated benefits defined in the interviews, to collect data from library staff to support these expectations, and to assign a value to them. Benefits from reduced file maintenance, processing, and tracking time were valued as person hours saved by the new system . Additional improvements were projected for the system's capability for better fund control, more complete and immediate on-order, claiming, and in- process information, and statistical collec- tion development/use data. These benefits were assigned the value of estimated dupli- cate and inappropriate material acquired under the present system. A value was not assigned to user benefits. Faculty and stu- dent satisfaction is intangible, and variable from case to case. Enhanced user service was recognized as a substantial benefit of the proposed system, but was not quanti- fied. The cost factors determined in phase four were consolidated with derived benefit values to form a cost/benefit analysis, which constituted phase five. In the sixth and final phase an implemen- tation plan was formulated. This plan, along with recommended target dates, was presented orally to library staff and univer- sity administration. In addition, the entire process, recommendations, and plan of action were documented in a written re- port. 5 RESULTS Within the A TT report were a descrip- tion of the current library environment, ob- jectives and description of the proposed sys- tem, implementation considerations, a cost/benefits analysis, and recommenda- tions for a plan of action. Although care was taken to "walk through" the function of each module of the described system, the report was not intended to provide detailed computer program specifications ready to be coded by a programmer. It described a useful and powerful integrated serials sys- tem in sufficient detail to be a working tool in the hands of a knowledgeable systems an- alyst to match (or revise) already available systems and programs to the library's speci- fications. The report itself also served as an effective communication link with the uni- versity administration, setting out library concerns and giving rational solutions to the pervasive problem of serials control and, in the long term, to an integrated library in- formation system. The timing of the A TT study was fortu- nate for the Clemson library. The univer- sity was on the eve of an accreditation self- study. As often happens with the examination of any organization, a host of related, but unacknowledged , problems surfaced in the course of the ATT study. During the interviews, staff members felt free to bring up matters of unclear policies, misunderstood hierarchical arrangements, and staffing inadequacies throughout the li- brary. The number and importance of non- automation concerns was significant enough that an administrative report was written to articulate these problems to the university administration. 6 It is interesting to note also that, while in every instance the team received enthusiastic cooperation from all those interviewed , there was fear among some staff members that any auto- mation project would necessarily cut staff positions. Once this worry was identified, the study team was able to allay those fears by explaining the study's purpose. One of the greatest contributions of the ATT study has been the direction it has given the library for future goals and priori- ties. By focusing on the problems of serials control, the team evaluated a microcosm of library problems. Investigating these prob- lems in the environment of more limited budgets, possible future closing or freezing of the card catalog, and increased user de- mands for services has helped the library develop a course of action, a resolve of mis- sion, and a direction for future growth. The staff of DAPS and the library are conducting a review of existing software and systems potentially appropriate for a comprehensive serials control system. The ATT study was the tool successfully used to elicit university support for library automa- tion. The university has given its approval, and supplied funding, to proceed with the determination of available systems and with the development of a request for quo- tation. Communications 209 REFERENCES l. For example: University of Rochester, River Campus Libraries, Task Force on Access Sys- tems, Report (Rochester, N.Y.: Univ. of Rochester, 1980), University of California, Berkeley, General Library, Committee on Bibliographic Control, Future of the General Library Catalogs of the University of Califor- nia at Berkeley (Berkeley: Univ. of California, 1977); Pennsylvania State University Li- braries, Systems Development Department, Remote Catalog Access System: General Sys- tem Specifications (University Park: Pennsyl- vania State Univ., 1977). 2. Association of Research Libraries, Office of Management Studies, Annual Report, 1979 (Was hington, D.C.: The Association, 1979). 3. International Business Machines Corpora- tion, Application Transfer Teams: Applica- tion Description (White Plains, N.Y.: The Corporation, 1977), p.1 ; International Busi- ness Machines Corporation, Application Transfer Teams: Realizing Your Computing Syste1ns' Potential (White Plains, N.Y.: The Corporation, 1977). 4. Inte rnational Busine'iS Machines Corpora- tion , Business Systems Planning: Information Systems Planning Guide (White Plains, N.Y.: The Corporation, 1975), p.49. 5. Richard W. Meyer and others, Total Inte- grated Library Information System: A Report on the General Design Phase (Syracuse, N.Y.: ERIC Clearinghouse on Information Re- sources, 1980), ED 191446. 6. Richard W. Meyer, Cooper Library: Status and Agenda. A Report on FY 1979-80 (Clem- son, S.C.: Clemson Univ., 1980).