This shows you the differences between two versions of the page.
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, | + | * In the case of the loss of functionality to AutoLit or Synthesis |
* In the case of the loss of functionality to any other key/ | * In the case of the loss of functionality to any other key/ | ||
- | * 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 |
- | * 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 ==== |