Nested Knowledge

Bringing Systematic Review to Life

User Tools

Site Tools


wiki:policies:disaster

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
wiki:policies:disaster [2023/10/10 20:18]
katcow
wiki:policies:disaster [2023/10/10 20:48]
katcow [Business Continuity Strategies]
Line 66: Line 66:
 === Loss of Function of Critical Applications === === Loss of Function of Critical Applications ===
  
-  * In the case of the loss of functionality to AutoLit or Synthesis, the CTO will be notified and we will send out a Site Disruption message to all users. The CTO and development team will assess the extent of any lost capabilities and timeline to restoration, and then communicate with company leadership regarding a recovery plan of specific functions.+  * In the case of the loss of functionality to AutoLit or Synthesis for at 30 or more minutes, the CTO will be notified and we will send out a Site Disruption message to all users. The CTO and development team will assess the extent of any lost capabilities and timeline to restoration, and then communicate with company leadership regarding a recovery plan of specific functions.
   * In the case of the loss of functionality to any other key/critical applications, the CTO will be notified; Site Disruption messages will only be sent to users in the case that this impacts end user functions. In consultation with company leadership, the CTO and development team will create a plan to either restore function or shift to a different software provider.   * In the case of the loss of functionality to any other key/critical applications, the CTO will be notified; Site Disruption messages will only be sent to users in the case that this impacts end user functions. In consultation with company leadership, the CTO and development team will create a plan to either restore function or shift to a different software provider.
-  * In case of outages, the CEO will email account representatives for customers with a proposed restoration timeline and details regarding the outage. +  * In case of outages, the CEO or another leader will email account representatives for customers with a proposed restoration timeline and details regarding the outage.
-      * Outages will also be communicated on Twitter @nestedknowledge+
  
 === Recession Planning === === Recession Planning ===
Line 79: Line 78:
   * In the event that Nested Knowledge loses our CTO, we will elevate our head engineer to replace the duties and hire an additional engineer as soon as feasible.   * In the event that Nested Knowledge loses our CTO, we will elevate our head engineer to replace the duties and hire an additional engineer as soon as feasible.
   * In the event that Nested Knowledge loses our COO, we will hire an already trained Operations Manager and Bookkeeper to aid with record keeping and financial operations.   * In the event that Nested Knowledge loses our COO, we will hire an already trained Operations Manager and Bookkeeper to aid with record keeping and financial operations.
 +
  
 ==== Compliance Statement ==== ==== Compliance Statement ====
wiki/policies/disaster.txt · Last modified: 2024/03/04 00:00 by katcow