CDM comparison shows how each mitigation plan for a conjunction event would change its risk. Every mitigation plan is reported beside a single reference CDM in the same risk metrics and the same B-plane and encounter-plane plots, so the effect of acting on it is measurable before committing to it.
A conjunction event page is everything Satcat holds on one predicted close approach. It is reached from the Conjunction Events Dashboard, and covers the following:
The dashboard is where you find the conjunction events that need attention. Filters apply across everything below, so narrowing once narrows all of it.
Details answers what the current risk is, which CDM produced it, how that CDM's geometry looks, and how the numbers have moved since the conjunction event opened.
Ephemeris comparison evaluates the conjunction risk of several ephemerides for one RSO side by side, against the conjunction data currently in effect for that RSO. Where CDM comparison on an event page examines a single close approach, ephemeris comparison covers every close approach an ephemeris produces, so an operator can identify the mitigation plan that lowers risk overall without introducing a new close approach or moving an existing one later in time.
Logs is the conjunction event's history as a single timeline. Each entry records what changed, when, and which CDM or upload caused it.
An OD quality rating indicates whether the tracking data behind a state was sufficient and processed adequately. Satcat rates the primary and secondary state of any CDM that reports OD quality metrics, and shows both per CDM in the conjunction event CDM table.
Both objects in a conjunction event carry the coordination state of their organization: what has been declared, what Satcat has inferred, and who is expected to act.
A recommendation is the action Satcat suggests for a single CDM, weighing the risk that CDM reports against how much confidence its data supports. One is generated for every CDM, so CDMs on the same conjunction event can carry different recommendations depending on the tracking data behind them, the originator, and when they were generated.
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.