Migration Costs

Because existing members invest heavily in hardware, a library that joins the CLC is assessed a $10,000 fee payable over a five year period. We are currently defining conditions in which we would waive that fee.

The library will pay any data conversion or data migration costs directly to the library’s ILS and/or Polaris. These costs vary.

The CLC also requires:

1. That the library maintains a firewall between itself and the CLC. The CLC licenses Check Point firewall. You will be required to buy a Check Point box. The cost varies with the number of nodes on your LAN ($850 for limited or $1400 for unlimited). CLC pays for software licensing and maintenance.
2. That the library has staff or contractors who can maintain in-library hardware, software and LAN (if any). Library Tech staff must be able to interface with CLC staff and attend a quarterly meeting. Use of the CLC’s Web Help Desk (for consortium-level l support) is required. Use of Help Desk for library internal issues is optional.
3. That the library use virus protection that scans in real time and is updated daily on every workstation in the library. CLC negotiates group pricing to Symantic’s console-based product. There is no direct charge to the library for this. However, the library must install and support it. Because we don’t manage configuration of the library’s internal LAN and workstations, the CLC cannot support the library’s installation. The CLC contracts with Semantic for support.
4. That the library pays for Client Access and Terminal Server licenses for Microsoft Server 2008. Participation in TechSoup by CLC member libraries keeps cost to a minimum. Smaller libraries spend less than $100. These are required on a per-staff-workstation basis but installed on servers at the CLC and managed by us.
5. That the library contract with U.S. Cargo for material delivery for a minimum of three stops a week. Libraries that do not currently use U.S. Cargo should contact the State Library of Ohio.

The CLC prefers (and strongly recommends) that all ILS system traffic flow directly to the CLC Data Center and not over OPLIN. Libraries that choose not to do this may experience delays and slow-downs during peak times. The CLC is not responsible for and cannot troubleshoot network problems and traffic delays that occur outside of the CLC network. A variety of configurations are already in place. To bring system traffic directly to the CLC Data Center the library may:

1. Move one end of the library’s existing OPLIN circuit so that it terminates at the CLC. This may involve some cost. AT&T may require a two year commitment. OPLIN will continue to pay the month to month and the CLC will provide access to the Internet.
2. Keep the library’s existing service as it is and get another circuit (From OPLIN or another provider) for Polaris traffic to the CLC. This has the advantage of ensuring full bandwidth for all ILS functions and separates it from Internet traffic.
3. Move the libraries existing OPLIN circuit as in #1 above, but add an additional circuit from another provider (some of our libraries use Road Runner) for all Internet traffic.

The CLC staff will work the library to determine the most reliable and cost effective measure for connecting the library to the CLC on a case-by-case basis.

The CLC also recommends:

1. That the library take full advantage of the CLC’s EnvisionWare license. Each library is responsible for any needed equipment and manages their own EnvisionWare installation but CLC staff supports integration with Polaris via SIP.