2014-07-29 Weekly Team Meeting notes

Date

Attendees

Goals

  • Review key deliverables

  • Review draft Event assessment and DR declaration procedure
  • Review External Interfaces matrix

Discussion items

  • Key deliverables known at this time are:
    • Disaster declaration procedure.
    • Document repository.
    • Communications Plan (including contact info).
    • External Interfaces plan.
    • Departmental responsibilities.
    • All agreed that this list seems comprehensive based on what we know at this time.  We can add to the list as we go along, if we find additional gaps.
  • All had input for the Event Assessment and DR declaration document.  Bruce will incorporate those changes.
    • For each type of event, what functions are impacted, who is impacted?
    • re: ETA to restore the outage, who do we ask for this info?  Who do we communicate with during an outage (Emergency response team?  University team?)
    • ask Pam - what is the minimum estimated time to communicate with and assemble the KFS DR team after a DR declaration?
    • To answer "how long can the University afford to be offline?", what are the mission critical functions, tolerances for outage, dept managers?  Do we need to conduct a KFS Business Impact Analysis within the scope of this project?  (see first bullet as well)
  • Shilpa agreed to begin laying out a Communications plan, using information already in the DR playbook as a starting point.
  • Dave is working on the Bottomline DR plan, related to this.
  • Dave agreed to work on filling in the External Interfaces matrix with information he is familiar with.
  • Several new items identified:
    • We will probably need to advise departments on their need to retain source documents for current day's transactions, in case needed for re-entry during a DR event.
    • How would we account or ascertain data loss after an event?
    • Should departments track time spent on a DR event?

 

TimeItemWhoNotes
    

Action items