Ensuring Robustness of SOC Operations

In this section, we outline how Robustness can be established and ensured through recurring validation and and revising

 

Build Robustness

Build Robustness

 

Based in the Regular scenario, procedures for the SOC Operator are defined.

Based in the Anticipated scenario, plans are developed for how each Operator will contribute, and the benefit from each tool is anticipated, in a manner that reflect the maturity of the organisation related to the anticipated potential for leverage of SOC performance. (Leverage for Improved Performance of the SOC as a Whole )

 

VALIDATE Robustness

 

Validate Robustness

 

The SOC should recurrently validate that Robustness is maintained. Revisons of the Regular and Anticioated scenarios should be periodically.

STRESS-TEST Robustness

 

The SOC should periodically stress-test the validated Robustness through a Surprise scenario, encompassing the SOC as a whole. Surprise scenarios should evolve based on prior results.

 

STRESS-TEST Degraded Modes

A special case of stress-testing should periodically be conducted on degraded modes. The degradation should be based on updated status of tools, their inter-connectivity, and their dependency on joint platforms.- Degraded Modes