Ever wonder what all of those strange words you sometimes see in our documentation mean? This page is here to help.
Incident Commander or Coordinator / IC#
The incident commander is the person responsible for bringing any major incident to resolution. They are the highest ranking individual on any major incident call, regardless of their day-to-day rank. Their decisions made as commander are final. More info.
Typically the backup IC. The deputy's job is to support the IC during the call, providing them with any help they need. More info.
The scribe's job is to keep a log of all activities performed during the call in a written chat log on HipChat. More info.
The Duty Manager own incoming customer escalations, regular internal communication and executive escalations.
A person on the incident call who is able to help resolve issues within a particular system. Also referred to as an SME (see below). More info.
"Subject Matter Expert", someone who is an expert in a particular service or subject who can provide information to the IC, and perform resolution actions for a particular system. These would include SOC Principal Engineers and Architects, as well as the escalation engineers. More info.
Customer Engagement managers follow up with relevant customers and F5 Account Managers on any update during the incident. Once a specific customer escalation is closed by the SOC DM, the CEM will own any further communication with the specific customer(s).
The Command Staff consists of the Incident Commander, Deputy, and Scribe.
CAN stands for "Conditions" "Actions" "Needs", if an IC asks you for a CAN report, you should provide the current state of your service (condition), what actions need to be taken to return it to a healthy state (actions), and what support you need in order to perform the actions (needs).
Severity / Sev#
How severe the incident is. The "sev" of an incident determines the type of response we give. The higher the severity, the higher the likelihood of making risky actions to resolve the situation. More info.
Span of Control#
Refers to the number of direct reports you have. For example, if the IC has 10 people as direct reports on a call, they have a large span of control. We aim to make the span of control as minimal as we can while still being productive.
Someone who joins the call at a late time in the game, and provides information that completely derails the current thinking. They then leave almost immediately.
When an executive comes on the call and drops some sort of bombshell. A version of grenade throwing.