Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Goals

  • Review Communication Plan progress (Shilpa)

  • Review DR Overview (Bruce)
  • Review External interfaces matrix / plan (Dave)
  • Review target dates for all the above, along with other deliverables.

Discussion items

  • Reviewed the Communications plan that Shilpa has in progress.  This includes lists of contact info for various participants.  Following comments / questions came up:
    •  RE: the university Public Safety dept - How do we get status updates and eta re: an outage or emergency?  Who should we communicate with during a DR event?  Does Public Safety need to be informed of a DR event, or is this just an FYI for them?
    • RAVE - will RAVE be involved in any way?  Is there anything they can provide that would be a value-add to our procedure / plan?  Who is the buyer who manages RAVE?
    • UITS - when would we communicate with UITS, and with whom?  How would we get updates from UITS re: an outage they are handling?  (can Pam help with this?)
    • Can the UITS Help Desk assist us in communications to the University KFS User community?
    • Finance Systems team:  need to add Dave, Bruce and Lan to the list.  maybe also Rob (although he is not directly involved in KFS, but he made need to know status)?
    • we agreed that we should not put system or server user ID's or passwords within the Communications Plan.  Only host codes for conference #'s that may be used for DR purposes, and similar access facts.
    • Shilpa will have a revised version by end of this week.
  • Reviewed the Overview Process Flow document that Bruce has in process.
    • confirmed that by "Finance Sys team" we mean Brett's team (Mike, Bruce, Dave, Lan, Rob, Raj) 
    • for KFS DR failover - After UITS-KFS and FIN-Sys teams validate the DR environment, there should be a step for user SME's to do their validation of DR, before communicating to the broader University KFS user group.
    • Budd Bldg outage - possible alternate locations are:  the Training Room at Chaplin Cottage / Depot campus;  the Purchasing Bid room at Central Warehouse.  Both contain PC's and space available for 12 or more personnel (total of Pam's and Brett's teams).
    • Bruce will refine and provide revision this week.
  • External interfaces matrix (Dave).  Dave reviewed his progress.  He will continue to work on this with Mike.
  • Reviewed the target dates for these deliverables.  In order to complete all drafts of deliverables by 8/29, we agreed that we should try to have these drafts farther along by next mtg (8/12) and in completed draft by the following meeting (8/19).  Then have Pam and Brett review by end of that week (8/22).  Team agreed that the target (8/29) is achievable. 
    • We also need to begin the draft for the Repository. 
    • Shilpa has also looked into the Test plans, and feels we can use some of what is used for the current DR testing.
    • We recognize that the Departmental Responsibilities will be defined as we further define the base plan.
  • We agreed to send out further revisions as we have them ready, so other team members can review them and provide comments more quickly.
TimeItemWhoNotes
    

Action items

  •  

    Check with Public Safety re: how we should communicate an outage to them, also how they can provide us updates and eta's during an event.  by next meeting (Bruce Lindemann (Deactivated))

  •  Contact Buyer for RAVE to see if there's anything RAVE can help with.  (Bruce Lindemann (Deactivated))
    When do we communicate with UITS - their involvement?  Ask Pam Kriedeman.  by next meeting.  (Bruce Lindemann (Deactivated))
  •  Get DR team backups defined.  Check with Pam.  (Former user (Deleted))
  •  Continue working on various plans.  (team)
  •