Ongoing support and continuous improvement

Owned by Chris Hoffman
Last updated: Nov 16, 2009Version comment

Ongoing support activities

When the deployment moves into an operations phase, the following activities must be covered:

  • Pre-operations planning activities (e.g, support planning, backups and recovery)
  • Monitor deployment to ensure system is running according to plan and requirements
    • Develop tools for monitoring
  • Perform tuning as needed
    • Develop tools for tuning
  • Provide operations phase support to users as identified in SLA.
    • Develop SLA; develop support skills, etc.
  • Provide scheduled maintenance
    • Identify scheduled maintenance needed (logs, etc)
  • Ensuring backups, DRS, etc.
  • Plan for unscheduled maintenance because something proverbial will always hit the fan
  • Upgrade hardware and software as the need arises, building in appropriate time to test
  • Track requests for new features
  • Work with CollectionSpace community

Continuous improvement and community participation

Know that in addition to ongoing support, there will always be requests for ongoing work on the CollectionSpace platform.  New features and capabilities will be called for.  Changes in your collection will test the boundaries of the system, and you will find things that do not work as well as you like.  CollectionSpace is optimized for agility and customization.  Your community of related institutions can help you meet the evolving needs placed on your collection and collection management system.