Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 2CUL E-Resources Unit staff:  ~250 hours across 2CUL staff including open Columbia position.
  • 2CUL Batch processing: 20 hours
  • Cornell Library IT: 10 hours+. Does not yet include estimate for Discovery & Access related work

Appendix 1: Costs

Licensing the products:

RM at Cornell

License fees - $11,693/year plus one time set up $1969 (includes data population services) and a onetime consultation fee of $3990

360 COUNTER at Cornell - 10,450/year plus onetime set up $688

Consortial -~$14,000 total, split between CULs for first year.  $20,000 total years 2+.

  • Standard pricing is about 20k for you all but since this is a pilot (and you all are good PQ customers), we can cut that to 8K for the year of the pilot and see how it goes.  There is also an implementation fee of $2,000 and a consulting fee of $3995.  We can create a statement of work to be sure we are aware of what the implementation looks like.  This will allow you to take time to work on the project without limitations and see how it works for you.

Cost recovery opportunities:

...

Cost recovery opportunities:

  • Innovative ERM License fee - currently approximately $7,500-$8,000/year.  This is paid until September 31, 2014.
  • Innovative ERM server - Once we get through the migration to the linux VM, our server cost for the III ERM will be about $2000/year as the server is currently spec'd.  (We may need to adjust its provisioning depending on actual performance once it's up and running in production.)  The support contract with III is in the ballpark of $10K/year.  Let me know if you need more specific numbers than that - chris

Benefits and potential savings:

  • Record loads into III - requires considerable attention for week every month. wear and tear on body and soul. Impact on patrons (updated holdings, public display inaccurate and slow), staff (stress and ability to focus on other work) 10-20 hours per month.  Some of the time saved could be spent handling more frequent Serials Solutions MARC updates loads, keeping Voyager and the ERM in closer sync.
  • License, resource, contacts information already in knowledgebase for many resources - III system is all hand entry for resource and license records.
  • Selectors will be able to access the system with relatively little training to view title lists, license terms, contact information.  As a web based tool, this will be possible remotely (during a conference).  III system has limited simultaneous connections and requires considerable training to get new users up to speed.

360 COUNTER at Cornell

License fees $10,450/year plus onetime set up $688

Benefits and potential savings: 

  • Annual harvesting of usage statistics - This will be mostly automated - SUSHI compliant resources each month, Non-SUSHI resources 2x yearly. System alerts us when changes are coming, usage harvesting data is out of date, - Sally Lockwood currently spends 12 weeks at about 75% of her time to harvest.  If we can recover 50-70% of this time to handle only the more complicated issues and updating the system, considerable effort is recovered.
  • Selectors will be able to access the system and make custom consolidated reports.  This is possible, but complicated in the current "system"

RM-CE for 2CUL-

License fees - $14,000 total, split between CULs for first year.  $20,000 total years 2+.

  • Standard pricing is about 20k for you all but since this is a pilot (and you all are good PQ customers), we can cut that to 8K for the year of the pilot and see how it goes.  There is also an implementation fee of $2,000 and a consulting fee of $3995.  We can create a statement of work to be sure we are aware of what the implementation looks like.  This will allow you to take time to work on the project without limitations and see how it works for you.

Benefits and potential savings:

  • Platform changes and other resource maintenance  - One person/process can make the changes for both institutions when both CULs have content in the same collections. 
  • Alerts monitoring
  • Comparison of e-collections will be considerably easier.  This will help with collection development decisions, shared workflow.

Appendix 1: Costs

...

Appendix 2: Implementation Details

...