THE STATE UNIVERSITY SYSTEM OF FLORIDA LIBRARIES
REQUEST FOR INFORMATION (RFI)
November 16, 1998
RFI RESPONSE INFORMATION
RESPONSE DUE: DECEMBER 18, 1998
Return to:
Grady Morein, Director
John C. Pace Library
University of West Florida
11000 University Parkway
Pensacola, FL 32514
OVERVIEW
1. Purpose of RFI
2. Vendor Logistics
2.1 Invited Demonstrations
2.2 Incurring Costs
2.3 Clarification
2.4 Tentative Timetable
2.5 Submitting the Information
3. System Requirements Overview
4. Configuration Scenarios
5. Overview of Current Library Automation System
5.1 The State University System of Florida (SUS)
5.2 The SUS Library Program
5.3 The Current System
TABLES
5.4 Demographics and Environmental Data
VENDOR RESPONSE SECTION
6. Functional Questions
6.1 Acquisitions
6.2 Cataloging
6.3 Circulation
6.4 Collection Maintenance
6.5 Interlibrary Loan
6.6 OPAC/Gateway
6.7 Serials Control
6.8 System Administration
7. Cost Questions
7.1 Servers
7.2 Clients
7.3 Middle tier
7.4 Database conversion
7.5 Installation
7.6 Training
7.7 Documentation
7.8 Annual maintenance costs and warranty periods
7.9 Custom programming
7.10 Any vendor support charges not covered above
7.11 Electronic A&I Databases
7.12 Digital Library
OVERVIEW
1. Purpose of RFI
The purpose of this Request for Information (RFI) is to identify and evaluate vendors capable of providing the software, hardware and services for delivery, installation and maintenance of a statewide Integrated Library Management System for the State University System of Florida (SUS). The critical information needed from vendors must include:
- Software and service: a clear, definitive and comprehensible description of the vendor's product and service capabilities
- Hardware: a thorough and precise description of what is needed in order to operate the system and what the hardware requirements (servers, PCs, printers, and all related equipment) needed for each institution
- Staffing: staff requirements (numbers of staff and skill levels for each institution and for a central location) and a clear description of staff training provided by the vendor
- Customer References: a list of currently installed sites with appropriate descriptions of the current status of those sites and an emphasis on sites which have a similarity to needs and characteristics of the SUS of Florida
- Pricing: a clear, definitive and accurate estimate of all costs required to purchase, install, and operate the system
2. Vendor Logistics
2.1 Invited Demonstrations
2.2 Incurring Costs
2.3 Clarification
2.4 Tentative Timetable
November 16, 1998 - issue RFI
December 1, 1998 - vendor will send contact and email address to ilsrtf-l@lists.ufl.edu
December 18, 1998 - RFI proposals due
December 21, 1998-January 31, 1999 - review of RFI by SUS Digital Library Review Task Force
February 1 -March 1999 - invited vendor demonstrations for committee
April 1999 - decision on the nature and timing of an RFP
2.5 Submitting the Information
Vendors should submit fifteen (15) copies (on white unbound 8.5x11 paper) of all requested information by December 18, 1998 to:
Grady Morein, Director
John C. Pace Library
University of West Florida
11000 University Parkway
Pensacola, FL 32514
3. System Requirements Overview
The selected system should be an integrated library automation system, replacing the automated system presently being used by the SUS. The SUS requires an effective, reliable, easy-to-use system to meet the needs of each and all of the SUS libraries. The system must operate efficiently in an environment in which any of the participating institutions can:
- establish its own operating policies and procedures through independent profiles,
- control use of the integrated library system through independent password and authorization functionality,
- control access to certain files and functions through independent password and authorization functionality, and
- display its own version of the bibliographic record, handle and display different call numbers for the same bibliographic item -- both for a single location and for different locations.
In addition, it is important that the chosen system be a complete system, which is defined as the applications software, software installation, database loaders, training, documentation, maintenance, technical support, and ongoing software enhancements necessary to provide easy-to-use online real-time integrated library system incorporating the following functions:
- acquisitions
- authority control
- binding control
- cataloging and database maintenance
- circulation control, including electronic and traditional reserve services, and circulation between all SUS libraries
- digital library support (electronic researves and digital/scanned image databases)
- fiscal management (including license control management)
- integration with other automated systems at the local institutional level
- interface with the system being used by the Community Colleges of Florida
- interfaces with materials supply (book, serial, binding) vendors and with other library systems/catalogs vendors
- interlibrary loan
- inventory control
- linkages with internal and external bibliographic, full-text, numerical, image, and multimedia databases
- management information
- online public access catalog(s) (OPAC)
- serials management
- union catalog
Key questions related to these functions are presented as the Vendor Response Section.
4. Configuration Scenarios
Vendors are requested to provide three (or more) responses based upon the following three scenarios. For each scenario, use the structure in Section 7 to provide the hardware configurations and all estimated hardware and software costs for all modules necessary to support all of the basic library management system functions, as well as any separately priced modules that a modern academic library might be expected to need. See the data tables in the Section 5 for details about the State University System of Florida (SUS) libraries. Regardless of the configuration chosen,
- The individual SUS libraries, both main and branches, require total autonomy over their holdings, acquisitions, and serials control data.
- The individual SUS institutions require security over access to their patron data, even while allowing for the ability to circulate materials across institutions.
- The system must allow the ability for user-controlled session limiting and for library-controlled client limiting such that the users default to the location, branch, university of choice or the entire SUS with the option to broaden in each successive step the search and display of holdings. This limiting capability applies to both OPAC and staff functions and applies to the searching and the display of all records (bibliographic, holdings, circulation, acquisitions, serials receipts, and acquisitions data) at the university, library, branch, and location level.
Scenario 1:
One shared system and database running at a central site.
Scenario 2:
Ten institutional databases plus a union search function all running at a central site. The union view must include all bibliographic, holdings, circulation, serials, and acquisition data. Identify in Section 6.8 how this union searching is accomplished, e.g., whether with a redundant set of indexing files, through a broadcast search function, or by the creation of an 11th database duplicating all necessary data. If the latter, identify how updates are synchronized. If multiple options are possible, use Section 7 to provide the configuration and pricing for each.
Scenario 3:
Ten university databases running at the 10 separate sites (i.e., one at each university) with an 11th site supporting a union database. The union database must include all bibliographic, holdings, circulation, serials, and acquisition data. Identify whether this is accomplished through synchronized updates or linking to the local systems. If multiple options are possible, provide the configuration and pricing for each.
5. Overview of Current Library Automation System
5.1 The State University System of Florida (SUS)
The State University System of Florida consists of ten State universities: the University of Florida in Gainesville; Florida State University and Florida A&M University, in Tallahassee; the University of South Florida in Tampa; Florida Atlantic University in Boca Raton; the University of West Florida in Pensacola; the University of Central Florida in Orlando; the University of North Florida in Jacksonville; Florida International University in Miami; and Florida Gulf Coast University in Fort Myers. Twelve off-campus centers are located throughout the state. In addition, the University of Florida Institute of Food and Agricultural Sciences (IFAS) administers seven agricultural research and education centers, as well as sixty-nine county cooperative extension programs. The University of Florida and the University of South Florida operate academic health centers. The University of Florida Health Center includes medical, dental, veterinary medicine, pharmacy, health related professions, and nursing programs. The University of Florida Health Center library supports a program located in Jacksonville. The University of South Florida Medical Center includes medical, nursing, and public health programs. These Centers provide professional degree programs and post-graduate residency in a variety of clinical settings. Both the University of Florida and Florida State University have law schools.
5.2 The SUS Library Program
The SUS Library Program is comprised of the individual libraries of each institution combined with the Florida Center for Library Automation (FCLA) and the joint service programs developed by the libraries. In the 1980's, FCLA was established to provide automated cataloging, acquisitions, and circulation support to the libraries and on-line catalogs for the use of students and faculty. In recent years, the SUS Library Directors Group has broadened that purpose to encompass a significant role in providing access to electronic resources. Together, the libraries and FCLA provide an integrated program of service to all SUS students, faculty, and staff.
The SUS Library Directors Council is composed of the ten directors of the SUS Libraries and the Director of FCLA. It deals with issues relating to interaction among the ten libraries such as student use of other SUS libraries; distance education; funding for library collections and services; common management issues; joint programs management such as the SUS electronic collection; oversight of FCLA services; and sharing of expertise in areas such as collection digitization, outsourcing, contract development, etc. It provides advice on library issues, when asked, to Board of Regents staff, to the SUS Council of Academic Vice Presidents or the Council of Presidents, and to various state agencies that need information on SUS library services.
As new electronic technologies allow revolutionary possibilities for uncoupling user location from access to a document, the SUS libraries are actively collaborating in purchasing and sharing resources. They are developing extensive programs to meet the library needs of distance education students. Increasingly, they are choosing to subscribe to full text/image journals and other resources by accessing publishers' servers directly through the Internet. The resulting subscriptions to electronic files are now included in the LUIS (Library User Information System) catalogs and "hot linked" to the full text/image Internet resource through the web version called WebLUIS (http://webluis.fcla.edu). The SUS libraries are also beginning to plan for programs to digitize resources from their collections and to collect research products from their universities in digital form (e.g., Electronic Theses and Dissertations).
5.3 The Current System
The LUIS system, the basic information system for the SUS, has been greatly expanded in recent years. No longer simply an online catalog of SUS holdings, it now offers a diverse information resource.
- The OPAC (on-line public access catalog). Provides access to all of the books, journals and other materials held by the SUS Libraries. These catalogs are accessible from anywhere on or off campus. In 1996, FCLA developed a new interface to the SUS catalogs called WebLUIS, providing web access not only to the library catalogs and citation databases but also to full image and text articles linked to the libraries' resources.
- Electronic Indexes. In 1992, LUIS had expanded to include indexes to articles and reports in journals. By mid-1997, there were 27 indexes covering diverse topics in the humanities, arts, social sciences and sciences. The two most popular indexes, the General Academic Index and the Business Periodicals Index, contain links to available full text articles.
- Gateways. In 1995, LUIS was expanded to provide "gateways" by which users can gain access to catalogs of other national and international libraries. The "gateways" also provide linkages to remote information systems which deliver local services, such as CARL Uncover, OCLC's FirstSearch, the Research Libraries Group's CitaDel databases, and other resources available through the Internet.
- Off Campus Access. In 1997, the FCLA developed the essential validation technology to ensure the libraries meet publishers' licensing restrictions. This means that qualified distance learners can have access to electronic resources from off-campus locations. Individual libraries are able to subscribe to electronic files that meet specific local academic program needs and make the files accessible through the Internet to local constituencies by using the FCLA's validation service
- Bibliographic Utilities. The SUS libraries currently load bibliographic records from OCLC, RLG, Yankee Book, and other sources. Records are downloaded from dedicated OCLC workstations in ordering and cataloging.
- Conversion of Data. SUS libraries expect to convert the following data from their current automated systems:
- authority records
- bibliographic records including locally created records
- copy records
- item records
- MARC holding records
- circulation statistics for in-house and out-of-house use
- circulation transactions for items currently on loan, on hold, recall, etc.
- circulation information on outstanding fines, bills, overdue items
- order/standing order/payment records
TABLES
5.4 Demographics and Environmental Data
VENDOR RESPONSE SECTION
6. Functional Questions
6.1 Acquisitions
6.1.1 Provide examples of any system interfaces with vendor and subscription agent databases (DataSwets, Faxon Source, Yankee GOBI, etc.); with CD-ROM products to receive/download data; and with commercial and proprietary institutional accounting systems.
6.1.2 Does your system allow a library to load records for acquisitions actions and bibliographic records based on machine-readable records provided by suppliers and/or any independent bibliographic support utility? If so, which suppliers and utilities?
6.1.3 Are orders associated with the catalog bibliographic records or is there a separate file of 'pseudo' bibliographic records for orders?
6.1.4 Does your system implement Electronic Data Interchange (EDI) according to national standards (ANSI, X12), international standards (UN/EDIFACT) and related industry implementation guides? What X12 or EDIFACT transaction sets does your system use for:
6.1.4.1 sending electronic orders and claims, and receive acknowledgments and reports
6.1.4.2 receiving electronic order status reports from vendors
6.1.4.3 receiving electronic invoices, including data for price, period covered, invoice number, invoice date and currency conversion as appropriate
6.1.4.4 sending lists of desiderata to selected sites, such as vendors, publishers, other libraries
6.1.5 Does you system implementation of EDI:
6.1.5.1 allow automatic updating of records by electronic transactions, or to have staff review transactions before posting
6.1.5.2 generate error reports for failed or suspect EDI transactions
6.1.5.3 allow launching from an acquisitions record to external on-line resources, initiating browsers or other applications as appropriate without manual cut and paste of data elements
6.1.5.4 transmit, send, receive, or otherwise handle EDI data without human intervention other than in the online ILS software
6.1.5.5 update of the database with EDI transactions while the system is in use
6.1.5.6 provide an online review of messages when it is not possible or desirable to update the database with an EDI message
6.1.5.7 provide a transaction log of all EDI transactions that is viewable online or printable as an off-line job
6.1.5.8 archive all EDI data
6.1.6 Briefly describe how data for fund management is structured and what, if any, hierarchies are possible (funds, groups of funds, subfunds, etc.).
6.1.7 Does your system provide for encumbrances, payment data and fund code allocations/balances to be converted from one fiscal year to the next, either globally or partially with minimal human intervention? What fiscal-year closeout/rollover options are provided? Can each institution act independently? Can autonomous branches act independently?
6.1.8 Does your system allow for the archiving of fiscal data from previous fiscal years to be stored and accessed? Is this functionality system wide or can a local institution act independently?
6.1.9 Does your system provide direct access to a desired activity such as invoicing, without having to go through other screens or activities first?
6.1.10 Does your system provide both predefined reports and the ability to create and run custom reports without programmer or systems librarian intervention? What sofware and interfaces are used to create and design reports (Web, commercial client, proprietary client, etc.)?
6.1.11 Which of the following can be used as optional output destinations for screen capture/prints; lists/reports; purchase orders; claims; other:
6.1.11.1 workstation screen
6.1.11.2 local printer
6.1.11.3 networked printer (lprd)
6.1.11.4 e-mail
6.1.11.5 HTML file
6.1.11.6 character delimited file
6.1.11.7 structured EDI file
6.1.12 Can your system provide for storage and interactive retrieval/editing of several million orders, vendors, invoices and related records in total across all ten SUS institutions, with several fiscal years' worth of stored data and with each autonomous library having its own local data?
6.1.13 Does your system allow order records to be moved/reattached to other bibliographic records?
6.1.14 Does your system support database licensing agreement?
6.1.15 Will your system allow or supply automated order creating and fund encumbrances of downloaded data from vendor and subscription agents.
6.2 Cataloging
6.2.1 Does your system support MARC standard cataloging functions in a Windows 3.1, 95, 98 (or later) as well as NT environment? How are compatibility upgrades to platform software and MARC format changes handled in a timely manner?
6.2.2 Does your system support Z39.50 searching and retrieval of MARC records, and allow storage of selected retrieved records in local databases?
6.2.3 Is your system capable of uploading/copying/transferring bibliographic and authority records from and to a variety of vendors, including commercial book vendors, OCLC, RLIN, other libraries, screening for duplicates, using standard control numbers, such as OCLC number, ISBN, LCCN and/or ISSN? Can these records be transferred individually and in batches? Are records available virtually instantly? Describe.
6.2.4 Does your system allow easy editing of MARC records, including, but not limited to, cut and paste features, creating new records based on existing records? Does your system allow easy creation of new records? Will your system adapt to innovative methods of inputting: scanning, voice recognition, etc. as they develop in the marketplace? Describe.
6.2.5 Does your system allow easily created and edited macros, keyboard mapping of those macros, and other often repeated functions; can the user create and store input/edit templates for frequently used formats or material types?
6.2.6 Does your system support a wide variety of search capabilities, including: author, title, keyword, call number (LC, Dewey, accession style, SuDoc, etc), all subject types, specific subject types (e.g., MESH, local, Childrens); author/title; with ability to limit by format, date, location, including sub-location, language, etc.? Describe.
6.2.7 Is your system capable of configuring the display of MARC fields in any order specified, both in technical mode and the OPAC? Can different institutions use different display arrangements? Can the union view be different than any particular institution?
6.2.8 Does your system provide integrated authority control, including validating headings under authority control on bibliographic records with existing authority records, automatic claiming of authority records, and interacting with the LC and MESH authority file? Does your system provide the ability to load LC authority records in a timely manner, generate heading conflict detection reports, change headings globally, etc.? Is your system capable of batch searching a record or group of bibliographic and/or authority records against an internal or external authority file, then producing a report of problems? Can the LC authority file be loaded as a resource file separate from the library catalog file?
6.2.9 Does your system provide any call number validation? Describe.
6.2.10 Does your system support hot links from the catalog record to Internet resources via the 856 field in bibliographic, holdings and piece level records?
6.2.11 Does your system support UNICODE, or otherwise support non-Roman languages, diacritics, and special characters in the OPAC and for catalog inputting/editing? How?
6.2.12 Does your system provide statistical report options that can be user defined by date, location, sub-location, item count, cataloging source, etc.? What statistics are available?
6.2.13 How are compatibility upgrades to platform software and MARC format changes handled in a timely manner?
6.3 Circulation
6.3.1 Is there full integration of all system modules with ease of access between all files, such as patron, catalog and financial records?
6.3.2 What range of functions are available within the circulation module, and describe how the following work: checkout, hold/recall, global renewal (including electronic or e-mail notice capabilities for these two functions), reserve room, creation of records for books lacking bar codes, interlibrary loan and media booking?
6.3.3 To what extent can each institution and branch customize its own circulation module, including wording for each type of notice and for each category/class of user?
6.3.4 Describe the process a late or missing book undergoes, including at what points staff intervention is necessary:
6.3.4.1 overdue (including electronic or e-mail notice capabilities)
6.3.4.2 blocks
6.3.4.3 overrides
6.3.4.4 billing (external as well as local system)
6.3.4.5 return of billed book
6.3.4.6 replacement management for lost or missing from shelf
6.3.5 Can due dates, calendars and other user and book circulation parameters be set locally in a multi-institutional-multi-branch environment?
6.3.6 List types of statistical reports, flexibility in extracting information, and ease of local vs. centralized access to develop reports as needed.
6.3.7 Describe interactive circulation/reserves/doc delivery services, and user-initiated forms/functions available in or facilitated by your system.
6.3.8 Is there an electronic reserve system? If so, describe its system requirements and any management features, including copyright compliance and hyperlink support.
6.3.9 Describe how your system tracks items loaned to other libraries in a consortium.
6.3.10 Describe present enhancements to full circulation/reserves/document delivery automation that no other vendor offers, in particular in a multi-institutional-multi-branch environment, and what future developments within the next 10 years are guaranteed?
6.4 Collection Maintenance
6.4.1 Is your system-design philosophy committed to the implementation of open, national/international standards and, if so, how, and which have you currently implemented?
6.4.2 Does your system provide for the storage and handling of electronic resources (that is, other than library management system records) and, if so, which digital (sound and image) and text formats are accommodated and how?
6.4.3 Does your system provide for the tracking of materials "in process" (as opposed to "in circulation") and, if so, does this methodology depend on the presence of a so-called item record and does it use the circulation subsystem?
6.4.4 Does your system have the capability of formatting and printing materials- processing labels (spine, pocket, etc. labels) and/or does it interface with third-party software for the production of labels? Can it be used from cataloging, serials, and circulation modules?
6.4.5 Does your system have a full-featured binding control module and, if so, does it fully support ANSI/NISO standard Z39.76 and/or does it support the automatic collapsing of serials issue holdings to volume holdings in the MARC format?
6.4.6 Describe the system components that expedite the systematic on-shelf inventorying of a library's collections.
6.4.7 Does your system in any way exploit the MARC bibliographic 853 field and/or does your system enable the recording of resource condition and treatment data at the copy or item level?
6.4.8 Does your system provide a means for collection inventory support?
6.4.9 Does your system have the ability to support security of access to restricted reources, especially where not all SUS libraries are entitled to shared access?
6.4.10 Does your system include firewalls for subgroubs of the SUS of variable number, down to one institution only
6.5 Interlibrary Loan
6.5.1 Does your system support the ISO Interlibrary Loan Standard Protocols (10160, 10161). If so, what PDUs are supported?
6.5.2 Does your system support user initiated requests for loans or document delivery for all formats of materials including returnable materials and non-returnable materials such as photocopies and digital copies delivered electronically?
6.5.3 Does your system have the ability to capture and import bibliographic data of the requested item from both local and remote catalogs and databases?
6.5.4 Does your system inter-operate with other systems such OCLC, RLIN and DOCLINE to allow users to search, request and receive requests from these systems? If so, describe how?
6.5.5 Does the ILL subsystem use the patron data and delivery information from the local circulation system?
6.5.6 Does your system provide online verification to the patron that a request has been placed with the capability, upon proper authentication, for the user to search, modify or cancel his/her own outstanding requests?
6.5.7 Does your system provide for multiple potential lenders on a request record and automatically forward the request from one lender to the next?
6.5.8 Does your system include data values that manage and track the request which conform to those specified in NISO Z39.63 and ISO 10161 protocols, including date requested, supplier, date filled, and date returned?
6.5.9 Does your system maintain ILL statistics and produce ILL management reports based on criteria established by the local library? Describe?
6.5.10 Does your system display an institution specified copyright compliance notice before allowing a request to proceed and supply a copyright compliance report for items requested?
6.6 OPAC/Gateway
6.6.1 What user interface delivery options does your system provide (e.g., WWW)? If desired, may different user interfaces be selected for use within the SUS library facilities and for access by remote access?
6.6.2 Will your system support delivery of SUS library catalogs, SUS course reserve indexes, and locally-stored citation and full-text databases (many proprietary) using the same interface? How many of these catalogs/databases may be selected and searched at the same time?
6.6.3 What OPAC user interface customization options does your system allow for library catalogs and databases at the SUS-wide level, individual SUS institution level, institution segment level (e.g., branch library), and citation, etc. database level?
6.6.4 What search modes (e.g., BASIC, ADVANCED, COMMAND entry), search types (e.g., author, keyword, ISSN, table of contents level, etc.), and search limits (e.g., date of publication, material format, language, and SUS library location) are provided with your system? How can the SUS define, develop, and implement locally any search modes, types, and limits not provided in the base system?
6.6.5 How are complex Boolean searches (i.e., with multiple logical operators AND, OR, NOT and with proximity operators ADJ, NEAR, WITHIN, SAME) entered? What is the maximum number of search characters and terms that may be entered in a complex keyword/Boolean search?
6.6.6 What information is included on the various results screens (e.g., lists of results, various views -BRIEF, LONG, etc., of specific records, etc.)?
6.6.7 May fields included in the various views be determined, and the field labels devised, locally at the SUS and/or individual institution level?
6.6.8 How are cataloging, circulation, and acquisitions statuses displayed in the OPAC?
6.6.9 How may a user most efficiently determine whether an item listed in a citation database is available in the local library collection or in another SUS library collection (aka the hook-to-holdings function)?
6.6.10 How does your system support links to local or remote full text resources (e.g., scanned course reserve and journal images, ASCII documents, Web sites, etc.)? Does your system provide a hot link to a URL from the OPAC if the record has information in the 856 field in bibliographic, holdings and item level records?
6.6.11 How does your system allow patrons to mark/capture records and send them to an email account, a printer, or a computer disk or diskette? What record format options and sorting options are available to users? How many records may be captured/marked before processing is required? May records be captured/marked from different catalogs/databases before processing?
6.6.12 How are previous searches (i.e., search history) displayed for re-use, and in what ways may those searches be manipulated?
6.6.13 What online user requests (e.g., inquiry about items checked out, request for recall/notification of a checked-out item, request a catalog/database item via Interlibrary Loan, etc.) does your system provide?
6.6.14 Does your system provide a general user guide, a training tutorial, and in-context help for all screens? May any locally-developed (by the SUS or an individual SUS institution) tools be substituted or otherwise incorporated?
6.6.15 Does your system support the display of cross references and appropriate search redirects, based on authority file?
6.6.16 Does your system follow standards-based (NISO) display of bibliographic holdings based on serials check-in record and MARC holdings record?
6.7 Serials Control
6.7.1 Does your system have a predictive algorithm based not only on the defined pattern for the serial but also past experience in the receipt of issues for the serial? Describe the algorithm and its strengths and weaknesses.
6.7.2 Does your system accept manual input of received issue data when prediction is impossible or unreliable, or when gaps are filled?
6.7.3 Does your system support recording of receipt via scanning of the SISAC and/or UPC barcode?
6.7.4 Does your system have the ability to associate records of individual titles to membership records or other global records?
6.7.5 Does your system allow for automated expansion or collapse of check-in data?
6.7.6 Does your system support multiple types of check-in linked to the same record (i.e., one section received in full, one section received in part)?
6.7.7 Does your system allow for multiple routing procedures produced from the same record?
6.7.8 Does your system support electronic claiming as well as printed claiming? If so, is this using X12 or EDIFACT transactions?
6.7.9 Does your system make it possible to review and modify or override automatically generated claims before they are sent or transmitted?
6.7.10 Does your system support notes about the receipt, method of check-in and retention of special issues?
6.7.11 Does your system supports the USMARC Format for Holdings Data? If yes, describe in detail how the format is used ans state specifically whether holdings data in the MARC format can be imported to and exported from your system?
6.7.12 Explain how your system interfaces with binding module. Can gathering lists be generated once a defined volume is complete? Does the holdings record automatically get updated when binding is complete?
6.8 System Administration
6.8.1 Explain the degree to which this system's architecture is flexible enough to enable any of the following configurations to be used for the ten institutions in the State University System of Florida (details in Section 4):
- One shared system and database at a central site;
- Ten individual institutional databases with a union database on a single system;
- Ten individual institutional databases with a separate union database on eleven separate systems.
6.8.2 Describe the types of interoperability available in this system, particularly regarding telecommunications standards, protocols for system connectivity, data exchange formats and standards such as MARC, X12 and EDIFACT.
6.8.3 Describe the extent to which this system is locally modifiable either through the availability of well-documented source code, APIs and/or a data dictionary of all schemas to support customer data mining.
6.8.4 Describe the ease with which this system can be managed, particularly addressing the requirements for the initial installation; the availability of remotely controlled ongoing operations such as startup, performance monitoring, and shutdown; availability of a fully functional test environment simultaneous to the production environment; and the availability of built-in diagnostic tools to test data integrity.
6.8.5 Describe how you expect this system to meet performance expectations for 7 day X 24 hour online operations, while giving sub-second online response time for public and staff functions for 90% of the transactions as measured at the server and supporting loads of 1.8 million transactions in an 8-hour period with a peak hour of 200,000 transactions.
6.8.6 The SUS databases range in size from 200,000 to 3,000,000 bibliographic records, with an expected combined file size of 5,000,000. The A&I databases total 25,000,000 records with annual search totals of 6,000,000. The user populations range from 2,000 FTE to 50,000 FTE, with a combined FTE of 150,000. Daily transaction volume is from 20,000 to 400,000 per database, with a combined daily volume of 1,500,000 transactions. Annual growth for each of the above is projected at ten percent. Given these data, explain how your system would scale to meet the needs of such databases and user populations, with particular emphasis on what limits might exist for concurrent use levels, total number of records that can be supported by your system, total number of records that can be supported per file, or any other limits that might be known that would affect expansion of hardware (CPUs, disks, memory, etc.).
6.8.7 Describe the extent to which your system can provide security control for staff and public users that addresses their needs for customization by function and level of authority. In particular, describe how workstation and user identification figure into the process, what measures are taken to ensure that multiple users are blocked from destructive concurrent editing of a given record, and any significant protections offered to prevent and report unauthorized access and/or attempts to override system limitations (e.g., circulation blocks).
6.8.8 Describe how remote (i.e., not in-library) users can access the public functions of your system. Specifically address the clients available and what, if any, limitations on distribution to all eligible users may exist; how IP validation works for your system as a whole, by individual modules and by individual databases; and what method of authenticating patrons from non-valid IP addresses is used.
6.8.9 Describe how your system supports compliance with ADA requirements for access.
6.8.10 Describe the hardware and software requirements of your system. Is any specialized, unique, or vendor-proprietary hardware or operating system used for clients?
6.8.11 Are there vendor-supplied data loaders for data transfer of all data from the existing NOTIS-based system without add-on charges?
6.8.12 Describe what your pricing model is for systems configured, as described in Section 4, with particular emphasis on any additional costs (except for more hardware) for adding records to existing files of any type, increasing the number of concurrent users of any module, and/or increasing the number of files already defined in your system? Identify any "extra charge" modules that might be needed to support any of the functions described in Section 6 (e.g., EDI support).
6.8.13 FCLA has a significant investment in an IBM RS6000/SP2 multiprocessor complex running the AIX operating system. Does your system run on this computer?
6.8.14 Does your system include firewalls that allow for limiting access to proprietary and local electronic resource databases, down to one institution only.
7. COST QUESTIONS
One of the main purposes of this RF1 is to obtain accurate cost data to be used for budget planning and budget presentation to high-ranking administrators in the SUS. Any misleadingly low cost estimates supplied by vendors could place the entire procurement process in jeopardy. Therefore, the costs provided should be realistic. This means that equipment, especially servers, should be sized properly to handle the SUS identified workload with appropriately fast response times, i.e., sub-second at the server for most responses.
Please provide separate cost data for each of the three configuration scenarios described in Section 4. If your system does not support one or two of the scenarios, reply "not supported" for that scenario. For each scenario, cost estimates must include initial purchase costs plus annual costs for five years. In all cases where relevant, supply both unit costs and total costs. Use the campus statistics provided in the tables supplied with this RFI. Itemize costs using the categories listed below. Be specific in describing the components and sub-components that are required for each cost category. For items 7.1 through 7.10, provide costs only for the library management functions necessary to support public access to and technical services functions for the library catalogs. For items 7.11 and 7.12, provide the incremental costs for adding the functions to support the Abstracting and Indexing Databases identified in Table 8.
7.1 Servers – repeat for each server
7.1.1 Hardware –
7.1.1.1 CPU – list make, model and RAM size
7.1.1.2 Disk – state quantity in GB
7.1.1.3 Other – describe and price separately
7.1.2 System software
7.1.2.1 Operating system – list product and version
7.1.2.2 Database management – product and version
7.1.2.3 Other – describe and price separately
7.1.3 Application software – list & price all available modules
7.2 Clients – repeat for each type of client if more than one type, e.g., public, technical services, circulation, etc…
7.2.1 Hardware – give optimal configuration and price for a single PC
7.2.2 System software – list all software required for each type of client
7.2.3 Application software – list unit prices for each type of client
7.3 Middle tier – if proposing a 3-tier client server system provide cost data about the middle tier here
7.3.1 Hardware
7.3.2 System software
7.3.3 Application software
7.4 Data base conversion
7.5 Installation
7.6 Training
7.6.1 Operating system
7.6.2 Profile customization
7.6.3 For each application module
7.7 Documentation
7.7.1 System level
7.7.2 For each application
7.8 Annual maintenance costs & warranty periods
7.8.1 Servers
7.8.1.1 Hardware
7.8.1.2 System software
7.8.1.3 Application software
7.8.2 Clients
7.8.2.1 Hardware
7.8.2.2 System software
7.8.2.3 Application software
7.8.3 Middle tier
7.8.3.1 Hardware
7.8.3.2 System software
7.8.3.3 Application software
7.9 Custom programming – hourly rate
7.10 Any vendor support charges not covered above e.g., telephone support above a pre-specified limit
7.11 Electronic A&I Databases: provide all costs, hardware, software and other, to add the databases listed in Table 8. Do not include database license fees as these databases are already licensed by FCLA. Provide costs based on a single, shared system.
7.12 Digital Library: provide all costs, hardware, software or other, to add digital library functions to the system (i.e., commercially acquired or locally created digitized full content). Since it is not possible at this time to predict the initial size and future growth rate of documents in the digital library, provide your cost data in ways that, in your judgement, help us in planning for this function. For example, costs per X thousands of documents or costs of a digital library of various total sizes would be useful. Provide costs only for a single, shared system. Indicate whether or not your system can search for content, e.g., specific words, within a document or across populations of documents or both.
Note:
Costs of telecommunications data circuits are outside the scope of this RFI. However, the vendor should include under hardware and software, as appropriate, all telecommunications products required by both clients and servers.