Operator Coordination
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.
Intent and Responsibility
For Space Traffic Coordination, Satcat surfaces operator intent and maneuver responsibility:
- Mitigation Intent: determined by the ephemeris
CONTEXTvalue - Maneuverability Category: based on SSC classification
- Responsibility category: assigned per Rules of the Road
Intent takes one of four states. I am intending to mitigate and I am not intending to mitigate follow from the Context on an uploaded ephemeris. Assumed to mitigate is inferred where the RSO is classified Auto-COLA Maneuvering, and Intent undetermined means nothing has been declared.
RSO Details
Alongside the coordination state, each object lists RSO type, either payload, debris, or unknown, the best HBR value in Satcat databases, and an RIC breakout of covariance and robustness. Orbital elements at TCA, ephemeris metadata, and OD metrics are shown where available.
Contact Center
The Contact Center provides operator-to-operator chat, along with the other organization's contact details where they are available. Chat is available for every conjunction event, unless the other party has opted out of Satcat coordination tools.
All messages are timestamped and logged. Contact details come from the Operator Contact Information in your Organization Settings.