17 docs tagged with "Coordination"

Asset Management holds an organization's Resident Space Objects (RSOs) and the data that keeps their orbits accurate: RSO parameters, orbit determination solutions, uploaded ephemeris, and watchlists.

The Business Directory provides affiliation and coordination context for space operators, manufacturers, and other space economy stakeholders. Each entry aggregates public data on organization identity, RSO ownership, and operational visibility. This directory supports transparency, attribution, and open communication across the Satcat platform.

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:

A conjunction event is a predicted close approach between two tracked objects. Satcat holds every CDM issued for that approach in one place, from its own screenings and from external providers, along with the ephemeris behind each message and the risk metrics derived from it. Because they sit together, the geometry, the current risk, and each operator's mitigation posture are read off one page instead of assembled by hand.

RSOs can be grouped into constellations, and each is listed with its identifiers, mean orbit, and how current its operational ephemeris is. Ephemeris is uploaded here, and objects that are not yet cataloged are held under temporary identifiers.

Operator uploads are private by default. Sharing is controlled per organization in Control Center.

Every ephemeris uploaded to Satcat carries two metadata fields. Context states what the ephemeris represents operationally, and Designation states how it was produced. Together they determine how Satcat uses the data and what is shared with other operators.

Operators use Satcat Operations to upload ephemeris for their RSOs, enabling real-time conjunction screening, mitigation planning, and intent signaling. When shared with appropriate metadata, this operational data forms the foundation for high-confidence collision risk assessments and coordination with other operators.

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.

The Operator Directory lists organizations responsible for operating satellites, including both Satcat Operations users and third-party entities. It is accessible under Directory > Operators, and serves as a contact resource for operator-to-operator coordination during active conjunction events.

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.

Every RSO carries a set of parameters. These values are used in orbit determination, ephemeris propagation, collision screening, and maneuver generation.

Rules of the Road is Satcat's coordination protocol. It assigns maneuver responsibility for each conjunction and lets operators exchange mitigation intent asynchronously, without needing to reach each other directly.

Satcat can ingest Space-Track CDMs for conjunction events and perform daily synchronization of Space-Track organization object metadata used to keep RSO context current (for example, maneuverability and other Space-Track-provided attributes).

Satcat integrates with Starlink's Space Traffic Coordination (STC) API to support Satcat-initiated actions that require authenticated access to Starlink's Space Safety system. When enabled for an organization, Satcat uses the configured credentials for Starlink-facing actions initiated from Satcat, including screening requests and operational ephemeris submission.

A watchlist is a named grouping of objects an organization tracks without owning. Watchlists are personal or shared across the organization, and they are available without an Operations subscription.