Auto-sync: 2026-04-24 04:02
This commit is contained in:
49
wiki/concepts/Normal-Change.md
Normal file
49
wiki/concepts/Normal-Change.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: "Normal Change"
|
||||
type: concept
|
||||
tags: [Change-Management, ITSM, CAB, Change-Window]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Normal Change(正常变更)是一种包含一定风险或影响的变更类型,需要变更咨询委员会(CAB)的审批,并可能需要跨团队协调。与 Standard Change 不同,Normal Change 需要明确的变更窗口来执行。
|
||||
|
||||
## Characteristics
|
||||
|
||||
|| Attribute | Value |
|
||||
|-----------|--------|
|
||||
| Approval Required | 是(CAB 审批) |
|
||||
| CAB Involvement | 必须 |
|
||||
| Automation Level | 部分自动化或无 |
|
||||
| Risk Level | 中-高(需评估) |
|
||||
| Change Window | 需要明确的时间窗口 |
|
||||
|
||||
## Process Flow
|
||||
|
||||
1. **Request**:产品团队提交变更请求
|
||||
2. **Assessment**:评估变更的风险和影响
|
||||
3. **CAB Review**:变更咨询委员会审批
|
||||
4. **Scheduling**:安排变更窗口
|
||||
5. **Execution**:在变更窗口内执行
|
||||
6. **Verification**:验证变更结果
|
||||
7. **Closure**:完成变更记录
|
||||
|
||||
## Relationship with Standard Change
|
||||
|
||||
Normal Change 的理想状态是通过自动化逐步将其归入 Standard Change 范畴:
|
||||
|
||||
- 识别重复的 Normal Change
|
||||
- 评估风险并制定标准化流程
|
||||
- 通过 IaC + CI/CD 实现自动化
|
||||
- 将 Normal Change 转化为 Standard Change
|
||||
|
||||
## Example Use Cases
|
||||
|
||||
- 跨账户的网络架构变更
|
||||
- 需要 CAB 审批的安全策略更新
|
||||
- 涉及多个团队协调的基础设施迁移
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
Reference in New Issue
Block a user