Supported by the GlobalNOC at Indiana University

Network Change Risk Mitigation

Keywords: impact, mitigation, network change, risk

The Impact / Risk Matrix provides guidelines for when configuration changes should be made on production Internet2 Networks. Please note that during a break/fix situation this document becomes null and changes to fix the issue may be made at anytime with Senior Engineer review.

Maintenance Window / After Hours Matrix

Low ImpactMedium ImpactHigh Impact
Low Risk no no Senior Engineer Review
Medium Risk no Senior Engineer Review yes
High Risk Senior Engineer review yes yes

Definitions

No = Change can be implemented at any time

Yes = Change can be implemented with standard 72 hour maintenance notification (168 hour maintenance notification for AL2S)

Review = Senior Engineer may select either 'yes' or 'no' considering specific change request parameters

Impact needs to be considered along with each risk level. During the risk decision process you should try to mitigate as much of the impact as possible thru notification, maintenance windows, customer interaction, and proper documentation.

Risk: Potential chance of adversely impacting network services.  What is the chance of unanticipated impacts?

  • High Risk
    • Very likely or certain to adversely impact network services.
  • Medium Risk
    • May have an adverse impact to network services.
  • Low Risk
    • Very small chance of adverse impact to network services. None expected.

 

Impact: Potential level of disruption on network services.  What is the scope of unanticipated problems?

  • High Impact
    • Serious effect or degradation experienced by multiple members.
  • Medium Impact
    • Noticeable effect or degradation experienced by multiple members.
  • Low Impact
    • Noticeable effect or degradation experienced by one member.

Your request has been completed.