Differences

This shows you the differences between two versions of the page.

--- faqs:evergreen_companies:faqs [2014/10/16 19:54] – [1) Should I use a vendor with Evergreen?] phasefx
+++ faqs:evergreen_companies:faqs [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Frequently Asked Questions  ======
-These are the frequently asked questions page for the [[faqs:evergreen_companies| list of Evergreen Paid Support Services]]
+These are the frequently asked questions for the [[faqs:evergreen_companies| list of Evergreen Paid Support Services]]
 **A note on the word "vendor":** traditionally, a vendor is a merchant that sells products.  Evergreen is not usually sold as a product, as it is freely available to all who want to use, modify, and/or distribute the software.  In this document we're going to use vendor as a shorthand to refer to anyone, whether a company, or an individual, or a non-profit organization, that offers Evergreen "services" in exchange for money.
@@ Line 25: / Line 25: @@
 ===== 2) How do I "vet" a vendor? =====
-The questions you may want to ask a vendor will vary by the type of work that you may want to use the vendor for. When hiring a vendor for migrating to Evergreen, one key first question to ask is if the vendor has ever migrated another customer from your current ILS to Evergreen. You may also want to ask for a reference of one of their customers who was migrated from that same ILS brand and/or version.
+==== Questioning the vendor directly ====
-When hiring a vendor for support, make sure to ask how many library employees are allowed to submit support requests. Also, ask for expected response times to emergency help requests, and what hours of the days will they be available to respond to help requests.
+Just like you would interview a potential new hire, you should interview the vendor.  You should ask for references, particularly from customers similar to you and/or receiving the same services.  Additional questions may vary by the types of services you're looking for:
-When hiring a vendor for development, ask how long do you have to find bugs or issues in their development without inquiring extra costs.
+  * hosting
+    * What service-level agreements do you offer for uptime?  What reparations do you offer for downtime?
+    * What is your backup policy?  Your disaster plan?  What are the potential points of failure?
+    * What redundancies do you have?  Do you have more than one data center?  What redundancies do they have?  Power sources?  Internet connections?
+    * What are you responsible for and what is out of scope of a hosting contract?
+  * support
+    * What service-level agreements do you offer for response time?  How do you escalate support tickets?
+    * What support tiers do you offer?  How many people may we designate to interact with your support system?
+    * What are the normal support hours?  Do you offer after-hours support?
+    * What does support cover exactly, and what is out of scope of a support contract?
+  * training
+    * What are your policies for recording and redistributing sessions and training materials?
+  * software development
+    * How do you interact with the wider Evergreen development community?  What can we expect concerning our changes ever making it into an official Evergreen release?
+    * What are your policies for acceptance testing and bug reporting?
+  * data migration
+    * What experience do you have with the software we're coming from?  Could you perform our data extraction?
+    * Do you offer test loads?  Do we have input in the data mapping?
+    * What are your policies for resolving data-related issues post-migration?
-When hiring a vendor for hosting, ask about their service-level agreements.
 ===== 3) What information should I have available for the vendor(s)? =====