Skip to main content

Risk Levels

A risk level is the severity Satcat assigns to a conjunction event, set by comparing its risk metrics against risk thresholds your organization defines. Because those risk thresholds are organization-wide, High means the same thing to everyone who sees that conjunction event.

Every conjunction event carries exactly one risk level, reassigned as new CDMs arrive so that it stays current with the close approach. Admins define risk levels and their risk thresholds in Control Center, see Risk Level Config.


How a Conjunction Event Gets Its Risk Level

Each new CDM triggers a reevaluation. Satcat tests risk thresholds from the highest risk level down and assigns the first one the CDM crosses. A conjunction event that crosses none is assigned No level.

Two organization settings shape the outcome. The evaluation mode determines which of the conjunction event's CDMs is measured, which is not always the Best CDM. The stale event cutoff returns a conjunction event to No level once CDMs stop arriving for it.


Manual Overrides

When the automated assignment is not appropriate, an operator can manually set a conjunction event to another configured risk level. Saving the override locks that risk level, and it will not automatically adjust as new CDMs are received. The selected override remains until "Unlock risk level" is selected. Unlocking allows incoming CDMs to update the risk level from organization risk thresholds again. The operator can save an optional reason when setting or unlocking the override. This information appears in both the event page risk level header and the conjunction event logs.


Risk Levels on a Conjunction Event

A conjunction event shows its risk level together with how that risk level was reached: the CDM responsible, when it was assigned, which risk thresholds that CDM crossed alongside its measured values, and whether the CDM has since gone stale.

Every change is recorded on the conjunction event's log timeline with the previous and new risk level, so a reclassification traces back to the CDM that caused it.

To find conjunction events by risk level, see the Event Dashboard.