|
Overview The “Kretzer” is a unit of measurement that measures severity of IT event. Much like the Richter scale, the Kretzer scale is base-10 logarithmic and measures the largest horizontal displacement. However, where the Richter measures geographic displacement, the Kretzer scale measures potential client displacement by an IT Event. The Kretzer unit can be abbreviated “Kzr”.
Requirements The key to handling IT/hosting events is getting the right people involved at the right time. Larger events require notification, planning, or permission from more people farther in advance. The smallest events may only require notification afterwards or possibly even not at all. Below is a list of notification actions required by certain levels of events. Note that there are no events higher than 5 Kretzers because nothing we do should ever “cause major damage to poorly constructed buildings over small regions.” Also note that events higher than 3 Kzr require permission from senior staff before they can be performed.
* 5 Kzr - Formal planning required with senior IT staff. * 4 Kzr - Formal permission required from senior IT staff. * 3 Kzr - Permission required from senior group leader * 2 Kzr - Notification of senior group leader required. Response received before action preferred. * 1 Kzr - Notification of senior group leader preferred. Notification can be done after action. * 0 Kzr - Go for it.
Defining the magnitude * Is the action taking place in a production environment? +2 Kzr * Will my actions affect a client? +1 Kzr * Does the action affect more than one client? +1 Kzr * Is the action taking place in staging? +1 Kzr * Is the action something you do regularly without consequences? -1 Kzr * Has it been tested in testing? -1 Kzr * Have you received standing permission to perform this action whenever necessary? -2 Kzr
|
|
|