SCARS RFP Process Page

Space Communication Asset Resource Schema (SCARS) RFP

Improving integration speed and accuracy for satellite contact scheduling software

The Object Management Group® (OMG®) has issued a request for proposal (RFP) for a Space Communication Asset Resource Schema (SCARS). The Space Communication Asset Resource Schema (SCARS) RFP seeks a standard for a machine-readable data representation syntax that would enable a satellite communications service provider to describe its particular asset from the perspectives of capability, location, and operational readiness.

Overview

To transmit data between a space vehicle (SV) and the ground, the SV ground operator must schedule communication assets to establish a data link to the SV. Today, most satellite contact scheduling software requires manual entry of satellite communication asset characteristics (e.g., location, operating times, RF capabilities, obscura, etc.) for a given provider’s asset. The ability to import this information electronically would improve integration speed and accuracy.

Additionally, communication asset characteristics may change over time due to age, equipment-related events, or modifications. Conveying this updated information in a machine-readable format improves channels for dissemination, increasing the speed of availability and reducing errors. Furthermore, in a dynamic situation where communication assets may change location sporadically (e.g., mobile), be in orbit (in constant motion), or only be available during intermittent time periods (e.g., in a tactical combat situation), manual entry of asset characteristics may be impractical and prone to error.

It is envisioned that a communication service provider would make Space Communication Asset Resource (SCAR) description(s) (in the format solicited in this proposal) available to authorized satellite operators (the “users”) by pushing them and/or allowing users to pull them. Once the user’s system has received the SCAR, it will automatically be ingested into the user’s contact scheduling system. This would ensure the user always has the most up-to-date information regarding potential contact asset capability, characteristics, and availability.

Intended Use Case and Applicability

The proposed SCARS standard is intended to address the needs of communication service providers and authorized satellite operators.

The proposed SCARS standard is intended to address issues with the scheduling of resources for satellite up- and down-links. For example, when you schedule a contact, you must know what assets are available. If an asset goes down due to weather or other events, the process for scheduling alternative ground assets relies on informal knowledge, which can be problematic. The proposed standard should enable the person who owns or controls a contact asset (such as an antenna) to produce a machine-readable file with all the necessary information, enabling a smoother transition between ground assets, both for civilian and military usage scenarios.

Important details & deadline

  • RFP Document
  • Letter of Intent (LoI) Deadline
    • Letters of Intent must be received by June 01, 2026. Please use the LoI Form to send in an LoI. You DO NOT need to be an OMG member to send in an LoI.

  • Initial Submission Deadline
    • Initial Submissions must be received by August 17, 2026.
    • Submitters of Initial Submission MUST BE members of the OMG at the Domain or Contributing level.

FAQs

  • What is a Letter of Intent (LoI)?
    • A Letter of Intent is a formal notice that the organization submitting that LoI intends to submit a response to an RFP.
    • This does not represent a binding commitment, however ONLY organizations which have submitted an LoI AND which are or have subsequently become OMG members at the appropriate level, may submit an Initial Submission.

  • Who May Respond with an LoI?
    • Any organization may submit an LoI. You DO NOT need to be an OMG member to submit an LoI.

  • What is the Initial Submission Deadline?
    • The Initial Submission Deadline is the date by which an initial draft specification must be submitted to the OMG in order for this to potentially become an OMG standard specification.
    • Initial submissions do not need to be complete, but must set out the submitter’s responses to as many aspects of the RFP as possible.

  • Who Can Make an Initial Submission?
    • Any organization that is an OMG member at the appropriate level may make an Initial Submission.
    • If the RFP was issued by the Domain Technical Committee, then submitters must be Domain or Contributing members.
    • If the RFP was issued by the Platform Technical Committee, then submitters must be Platform or Contributing members.

OMG Processes Open for Public Participation

Please refer to the Current Open Processes page for further information on processes that are currently open to public participation and responses, and for pointers on what happens next.