The workspace for reliability and resilience engineering.
可靠性模型
The Global Centre for Risk and Innovation (GCRI) · Reliability and resilience · Run R-3730 · Example interface, not a record
依赖关系图
节点:资产 · 边:依赖关系
失效模式
| N3 | 8811 | 8 | Critical |
| N4 | 5317 | 25 | 正常 |
| N5 | 4984 | 14 | 正常 |
| N6 | 5367 | 42 | 正常 |
移除条件下的级联规模
GCRI · 可靠性模型。 可靠性模型:示例名称和示意性数值,并非记录。
流程如何运行。
Process explorer · Process
可靠性与韧性工程:运营韧性
8 个步骤·4 个阶段
流程
可靠性与韧性工程:运营韧性
Basel defines operational resilience as delivering critical operations through disruption; the UK PRA uses important business services and impact tolerances.
01 Services and tolerance
- 01Important business services or critical operationsDataset · Programme ownerUnder PRA rules a firm identifies its important business services; Basel says critical operations. Resilience delivers them in disruption.
- 02Set impact toleranceStep · Programme ownerFor each important business service the firm sets an impact tolerance, the maximum tolerable disruption.
02 绘图与检验
- 03制图步骤 · 计划负责人企业记录交付每项重要业务服务所需的条件。巴塞尔委员会要求银行梳理相互联系和相互依存关系。
- 04严重但合理的情景模型 · 项目负责人情景是严重但合理的中断事件。巴塞尔委员会列举了大流行病、网络事件、技术故障和自然灾害。
- 05Scenario testingExercise · Programme ownerThe firm regularly tests whether each important business service stays within its impact tolerance in a severe but plausible disruption.
03 Fix
- 06识别脆弱性步骤 · 计划负责人如果能力无法满足所述容忍度,政策应当弥补这一差距。巴塞尔框架将这项任务交由董事会监督。
- 07Act to remain within toleranceStep · Programme ownerThe firm must ensure it can remain within its impact tolerance for each important business service.
04 管理机构
- 08Self-assessment and management body approvalDecision · Management bodyThe firm prepares and regularly updates a written self-assessment. Its management body approves the services and the self-assessment.
Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval. The two vocabularies differ; the outline names both.
吸收、适应、恢复。
Reliability asks how often a component fails; resilience asks how a system performs during and after disruption. The resilience curve (performance against time through a disruption) makes recovery speed and degraded performance explicit. Interdependent networks need joint restoration planning, because one network’s recovery waits on another’s.
谁维护本页面。
Critical Infrastructure stewards reliability and resilience engineering: it keeps this description current and reviews how the method is applied across the platforms.
Where this page’s references lead.
阅读本页时所对照的机构和文件。状态和版本会变化;每个链接都指向发布机构。
问题与解答。
为什么由一个机构托管所有方法页面?
如何对方法页面提出更正建议?
从本页贡献证据。
Reports 是联合体的季刊。您对该主题的了解可以成为下一期中的证据、案例或更正,署名归您,并在属于您本人作品时以 CC BY 4.0 发布。
- 电子邮件网关 GW-GCRI从本页发送证据、更正、案例、方法、审查、翻译或概况投稿。它会带上本页标签送达,由负责的编辑接收。
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- 报告GCRI查看所有贡献方式贡献类型、各自的评审方式、您获得的署名、许可协议,以及绝不接受的内容。
切勿发送个人数据、敏感基础设施细节或您无权分享的任何内容。贡献在使用前会经过审查;发送贡献不赋予署名权或编辑权,赞助也绝不能换取研究结论。
法律文件。
本网站上的地图、数据和图表仅作为背景和一般信息展示。它们不是建议、预测或预警;信息的局限见免责声明和数据说明。