45 lines
1.5 KiB
Markdown
45 lines
1.5 KiB
Markdown
---
|
||
title: "Emergency Change"
|
||
type: concept
|
||
tags: [Change-Management, ITSM, Incident-Response, CAPA]
|
||
last_updated: 2026-04-14
|
||
---
|
||
|
||
## Definition
|
||
|
||
Emergency Change（紧急变更）是为了缓解事故（Incident）并尽快恢复服务到期望状态而需要立即执行的变更。与 Normal Change 不同，Emergency Change 可以在没有 CAB 预先批准的情况下执行，但事后必须通过 CAPA/Post-mortem 流程修复根因。
|
||
|
||
## Characteristics
|
||
|
||
|| Attribute | Value |
|
||
|-----------|--------|
|
||
| Approval Required | 事后审批 |
|
||
| CAB Involvement | 事后汇报 |
|
||
| Automation Level | 可部分自动化 |
|
||
| Risk Level | 高（应急执行） |
|
||
| Change Window | 即时执行 |
|
||
| Post-Process | 必须 CAPA/Post-mortem |
|
||
|
||
## Process Flow
|
||
|
||
1. **Trigger**：Incident 触发应急响应
|
||
2. **Assessment**：快速评估并决定是否执行 Emergency Change
|
||
3. **Execution**：立即执行变更以缓解事故
|
||
4. **Communication**：通知相关干系人
|
||
5. **CAPA**：事后通过 CAPA 流程修复根因
|
||
6. **Documentation**：完成变更记录和 Post-mortem
|
||
|
||
## Key Principle
|
||
|
||
> Emergency Change 的目标不是永久性补丁，而是通过 CAPA/Post-mortem 识别根本原因并制定长期解决方案。
|
||
|
||
## CAPA Process
|
||
|
||
CAPA（Corrective and Preventive Action）包含两个阶段：
|
||
- **Corrective Action**：修复当前问题的即时措施
|
||
- **Preventive Action**：预防同类问题再次发生的长期措施
|
||
|
||
## Sources
|
||
|
||
- [[ctp-topic-30-managing-change]]
|