Incident Prioritization for Major vs Single Incident
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2023 12:48 PM
At my organization, we are trying to revamp our Incident Priority Definitions and Criteria. Our current Incident Priority Matrix mostly covers what to do and what is considered a Major Incident Priority 1 vs Major Incident Priority 2 and so on. We don't have any criteria for a single incident being a priority 1, 2 or 3. We think there should be a distinction and different criteria for Major incident vs single incident. We are looking to see what others have for their incident priority criteria and definitions. Do you separate Major vs single incident? If so, are you willing to share how you have it structured? Happy to jump on a conference call too for further discussion. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 11:46 AM - edited ‎10-01-2024 11:46 AM
Major Incident can be driven by having multiple incidents reporting the same thing. A collection of incidents can have a child relationship to its parent Major incident.
Example
P1 - Windows SSO Authentication is down for all users (Parent)
|_____P3 - User A Unable to login to pc (Child)
|_____P3 - User B gets error when trying to login to pc (Child)
|_____P3 - User C cannot login to laptop (Child)
Solutions Design Architecture
ITILv3 | NSE2 | ServiceNow ITSM, ITOM, ITBM, CMDB & CSDM Mgmt