Considerations and Options for DV Service Providers running Alice Software

DRAFT

Many DV service providers run the Alice case management software application. They lack expertise to run their own HW and applications, and seek to understand options in selecting a platform.

Summary

In reviewing platforms, there are a number of options and considerations. Each DV service provider (DVSP) should make their own determination regarding the best platform for them.

Sample Platform Options:

There is an infinite variety of combinations of services. Here are four sample categories of service with examples.

1. Standalone server running DVSP’s instance of Alice with standalone DB instance in DVSP’s facility
   • HW - Standalone server in the service provider’s facility
   • SW - single copy of Alice SW owned by DVSP
   • Maintenance/DR: DVSP hires a consultant for sysadmin services/DR (basic details such as nightly backups and hardware recovery)
   • DB - standalone DB instance (rather than combined with DBs of other DVSPs)
   • Example - Transition House’s current setup
2. Server leased/owned by DVSP running DVSP’s instance of Alice in co-located facility where maintenance/disaster recovery services may be contracted.
   • HW - Standalone server in the service provider’s facility
   • SW - single copy of Alice SW owned by DVSP
   • Maintenance/DR: DVSP contracts with co-location facility for sysadmin services/DR (basic details such as nightly backups and hardware recovery)
   • DB - standalone DB instance
   • Example- Softlayer
3. SP’s instance of Alice running on “cloud” provider’s hardware in cloud facility, maintained by “cloud” provider
   • HW - Standalone server in the “cloud” facility
   • SW - single copy of Alice SW owned by DVSP
   • Maintenance/DR: included in “cloud” provider basic service contract (in theory, need to verify this)
   • DB - standalone DB instance
   • Example - Amazon Web Services or Rackspace. However, Alice won’t run on these because it’s designed for local installs only.
4. SAAS- Software as a Service (does not exist for Alice to our knowledge)
   • HW- Provided and maintained by SAASP in their location
   • SW - Provided and maintained by SAASP in their location
   • Maintenance/DR: performed by SAAS provider (in theory, need to verify this)
   • DB - Virtual partitioned DB for DVSP, may or may not be part of larger consolidated DB with other DVSPs
   • Example - salesforce.com (does not exist for Alice to our knowledge)

Summary of Considerations:

1. Technical
2. Human/Usability
3. Legal
4. Financial

Analysis of considerations. Note, SAAS is excluded as this option does not yet exist to our knowledge.

1. Technical - Option 3, Running on “cloud” provider’s HW in their facility is technically easiest for DVSPs
2. Human/Usability - Option 3, Running on “cloud” provider’s HW in their facility is easiest for DVSPs
3. Legal - If client data is subpoenaed, DVSP does not own data under Third Party Doctrine when using outside computing service providers.
4. Financial - Option 3 should be least expensive, but individual quotes may vary

Authors

Sarah Cortes

Andrew Lewman