A knowledge base article about Major Incident: Business Process provided by the UC Berkeley IT Service Hub - Knowledge Portal
A major incident (MI) is an incident that results in significant disruption to the business and demands a response beyond the routine incident management process. Major incidents often have a separate business procedure with shorter timescales and urgency that is required to accelerate resolution process for incidents with high business impact.
The definition of what constitutes a major incident is often determined by the Service Desk and/or the Service Manager. For example, a major incident could be created if a critical business service is impacted or if there is a service outage that affects a large number of users.
Major Incident Criteria
Communications
Our primary communication between the Service Desk and the Service Providers will take place using Slack. Communications should utilize the active-issues channel on the ucbpi.slack.com instance. For access to this channel, please contact UC Berkeley's point of contact for Slack.
Here is more information on Slack and general Slack etiquette.
Crucial things in responding to a major incident are to involve right resources, communicate updates to users and stakeholders, setup conference calls to investigate and resolve the incident, and escalate when required.
Outside of Business Hours
Service managers will serve as the Major Incident Manager until the next business day of the Service Desk. They will have minimal responsibilities in this space as their primary focus will be resolving the incident.
Lisa Hisson is the process owner for incident and major incident.
Additional questions? Please send email to the ServiceNow Support team for help with your question: servicenow-support@berkeley.edu