Laserfiche WebLink
SOLICITATION # CH16012 <br />8.7.1 Offeror must describe how it manages the end of life activities of closing down a service to a <br />Purchasing Entity and safely deprovisioning it before the Offeror is no longer contractually obligated to <br />maintain the service, include planned and unplanned activities. An Offeror's response should include detail <br />on how an Offeror maintains security of the data during this phase of an SLA, if the Offeror provides for <br />redundancy during migration, and how portable the data is during migration. <br />The end of life activities for each Purchasing Entity will vary based on the type of service they are currently <br />using and the service that they will be moving too. All Purchasing Entities will be notified in advance of any <br />end of life service so that the Purchasing Entity can work with Carahsoft and the service providers to <br />develop a plan exporting and transitioning data. <br />8.7.2 Offeror must describe how it intends to provide an orderly return of data back to the Purchasing <br />Entity, include any description in your SLA that describes the return of data to a customer. <br />At all times during the course of the Service, the Purchasing Entities will have access and ownership of <br />their data. The Purchasing Entity is free to download or access the data through a variety of means based <br />on the service at any time during their service period. <br />8.8 Service or Data Recovery <br />8.8.1 Describe how you would respond to the following situations; include any contingency plan or <br />a. Extended downtime. <br />CA <br />APM <br />If unable to resolve in a timely manner, all customers will be notified via email to the <br />registered admin <br />MAA <br />Customers are kept abreast with progress during incidents, including outages. CA <br />utilizes best -of -breed notification system which enables customer contacts to self - <br />subscribe to different types of notifications that they would be interested in. A DR plan <br />has been created should the extended down time result in DR declaration. <br />CA Agile <br />We would failover to our warm data center in order to restore access to the application <br />as quickly as possible. This is done according to our Disaster Recovery Plan <br />ASM <br />If unable to resolve in a timely manner, all customers will be notified via email to the <br />registered admin. Failover from the primary to DR site may be utilized if the extended <br />amount of time warrants declaration of DR. <br />Google <br />Due the redundant nature of the Google infrastruture there is no expectation of any extended <br />downtime. If a data center in use by any of your end users suffers a catatrophic failure, Google's <br />d namic health monitoring would just reroute the session to a different data center. <br />AODocs <br />All the AODocs data is hosted on the Google Cloud Platform infrastructure. AODocs does not <br />manage any physical infrastructure. Due the redundant nature of the Google infrastruture there is <br />no expectation of any extended downtime. If a data center in use by any of your end users suffers <br />a catatrophic failure, Google's dynamic health monitoring would just reroute the session to a <br />different data center. <br />Virtru <br />Notify users that Virtru service is unavailable, and recommend that they use their offline encryption <br />tools and backups to perform emergency functions. <br />Salesforce <br />Salesforce has maintained high levels of availability across all Salesforce instances since <br />inception. As the only on -demand vendor to provide daily service -quality data on a public Web site <br />(http://trust.salesforce.com), Salesforce proves that we are the leader in availability. And by <br />making its track record completely transparent, Salesforce proves we are worthy of our customers' <br />trust. To ensure maximum uptime and continuous availability, Salesforce provides the best <br />carahsoft carahsoft <br />