TACSIT Configuration Settings and Services RFP
Facilitating Configuration of Tactical Situation Displays
The Object Management Group® (OMG®) has issued a request for proposal (RFP) for Tactical Situation display configurations and settings. This RFP seeks proposals that will provide a solution to the problem of specifying the configuration of a TACSIT display (a TACSIT display being an application displaying geospatial tactical situations to one or more users) so as to facilitate a standard and reusable way for organizations to be able to specify and configure applications with TACSIT displays.
Overview
The domain of Combat Management Systems (CMS) is characterized by a variety of underlying computing platforms, with different and often incompatible means of providing interactive displays. Standards-based services are essential for interoperable and open systems
There is general agreement of what is considered the Tactical Situation (TACSIT) display within a tactical / strategic display system, also referred to as the GeoSit (Geographic Situation) or Geospatial Information System (GIS) display. The TACSIT component is the software often built on top of a GIS toolkit that provides user awareness of entities in the operational space relative to certain geo-spatial context(s). The TACSIT, by its nature, displays entities called tracks in their proper geographic location overlaid on a visual representation of a map while including additional annotations and decision aides to support the operator. The TACSIT is distinct from other display applications that work around, or in conjunction with it.
This RFP solicits proposals for the following:
- TACSIT Configuration Metamodel: Proposals shall provide a metamodel describing:
- The elements and attributes of visual items that can form part of a TACSIT display and the effect of the attributes on the visual appearance and behavior of those items embedded in a particular TACSIT display instance.
- The logical service interfaces that are needed to manage and access configuration objects and attributes by users (and administrators/maintainers) of a system that implements one or more TACSIT displays presented to one or more end users.
- TACSIT Configuration PSM: Proposals shall include at least one platform specific implementation of how a TACSIT configuration may be specified, stored and accessed by a TACSIT display.
A proposal for a standard for a TACSIT Configuration Interface shall include one or more of the following:
- A platform-independent metamodel (PIM) describing elements of TACSIT configuration and their attributes captured in UML as an XMI representation.
- Platform-specific metamodels (PSM) that instantiate the PIM on a specific technology or platform.
Consideration of aspects of security that need to be applied to implementers of the proposal who are targeting secure environments.
Intended Use Case and Applicability
There are many capabilities and services necessary to successfully implement a TACSIT software component. Within this broader context of TACSIT services, there are several aspects to be considered such as Controllers, Maps, Tracks, Geometric, and Configuration. This specification RFP is targeted at the Configuration Services necessary for TACSIT software component and related displays for providing a user with a consistent and tailored set of tactical situation displays.
Configuration Services provide a means to specify, store, and modify display configuration settings of the TACSIT software component and related displays. Some general examples of Configuration Services include the color schemes of displays, geographic projections to use, symbology set to display entities (tracks), the screen location and size of various tactically relevant displays, and other related display features.
The specification solicited by this RFP is focused on the technical means for representing these concepts and shall have no recommendations for what the various settings should be for any context. There are myriad use-cases, usability factors, and research studies in different contexts to provide guidance on what the values or settings should be. The solicited specification shall provides a consistent and standard means of expressing them these in a software-readable format.
Important details & deadline
- RFP Document
- The RFP document may be downloaded as OMG Document c4i/2026-3-18.
- The RFP document may be downloaded as OMG Document c4i/2026-3-18.
- Letter of Intent (LoI) Deadline
- Letters of Intent must be received by October 15, 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.
- Letters of Intent must be received by October 15, 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 March 30, 2027.
- 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.
- 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.