• Replies 8 replies
  • Subscribers 337 subscribers
  • Views 164 views
  • Users 0 members are here
Related

Contingency procedures for Hosted Organisations

Donald Graham
$organization

Morning all,

We moved to Hosted late last year and we want to review our contingency procedures. Whilst we can’t be 100% prepared for every eventually, we want to have some processes in place if we lost access to Tessitura and/or a stable internet connection to our site.

Previously we had some scheduled back up reports via a stored procedure that saved to our onsite network which we could refer to. Not that we are hosted this is trickier.

Can any other hosted organisations share the rough outlines of any contingency procedures they have? Main scenarios we are looking at are Hosted Services being completely down, interruption of internet to our site or internal network issues meaning some users can’t access Tessitura. With our previous contingency procedures, the main goal was to be able to get a show into our Main House space, even if we don’t have Tess at our Box Office counters.

Any help or even just some rough ideas would be greatly appreciated!

Thanks, Donald

Parents
  • $organization

    In the wake of the Wordfly outage we were galvanized to get more serious about contingency planning.  We're currently at that 80/20 point where we have done 80% of the work, and now only need to finish the remaining 20% using the remaining 80% of the effort.

    What we've done to date is attempt an exhaustive catalog of service interruption scenarios (matched with various possible durations) followed by an attempt at an exhaustive catalog of mitigation options (emailed reports, rescheduling events, working from home, etc.)  The remaining work is to connect the list of mitigation options to the scenario/duration listings.  That part I've left to other parties, as those plans are going to depend heavily what department or organization (we are a consortium) is responding.

Reply
  • $organization

    In the wake of the Wordfly outage we were galvanized to get more serious about contingency planning.  We're currently at that 80/20 point where we have done 80% of the work, and now only need to finish the remaining 20% using the remaining 80% of the effort.

    What we've done to date is attempt an exhaustive catalog of service interruption scenarios (matched with various possible durations) followed by an attempt at an exhaustive catalog of mitigation options (emailed reports, rescheduling events, working from home, etc.)  The remaining work is to connect the list of mitigation options to the scenario/duration listings.  That part I've left to other parties, as those plans are going to depend heavily what department or organization (we are a consortium) is responding.

Children