incident communication expectations - raeker/ARC-Wiki-Test GitHub Wiki

Advanced Research Computing : Incident Communication Expectations

Emergency Outage Impacting Wide User Access

Follow ITS Significant Incident Process

Missing Service Window End Times 4-24 hours

User, Unit, and Unit Mangers, Communication and ITS Status page entry expected when clear window will be missed by more than 4 hours.

Unit, and Unit Managers communications and status page entry 4-8 hours.  (Eg. Morning, Noon, Night)

User communications every 8 hours or significant change (Eg. login nodes are up can access data, service still down).

Missing Service Window End Times 24 hours+

Prepare to treat like Significant Incident. Call SI coordinator for a communication SI.  Discuss with coordinator if SI is warranted.

General rule, after 24 hours, treat communication like the service went down unexpectedly.  Users expected to have access to resources and data and they do not.

⚠️ **GitHub.com Fallback** ⚠️