Pending Requests for Proposals:

All OMG work in progress deadlines in chronological order

Agent Metamodel and Profile (AMP) RFP
This Request for Proposal solicits submissions for an Agent Metamodel and Profile (AMP). Essentially, the AMP RFP requests a metamodel and profile for extending UML with capabilities applicable to agents and agent-based software. Submissions developed in response to this RFP will achieve the following: Clarify semantics concerned with modeling agents. Establish Agent modeling best practices utilizing OMG technologies. Develop a MOF-compliant agent metamodel to be used either standalone or via extending the existing UML metamodel with agent modeling capabilities. Enable agent model interchange between tools via XMI. Optionally facilitate modeling of Peer-to-Peer, Grid and Cloud computing, and other technologies in terms of a collection of Agents. It is expected that responses to this RFP will make good use of agent modeling capabilities already supported by the OMG.

DDS C# API Request For Proposal
The Data Distribution Service (DDS) specification consists of a UML Platform-Independent Model (PIM) and a single IDL Platform-Specific Model (PSM). As a result, DDS implementations have traditionally implemented APIs that derive directly from the IDL PSM using the standard IDL to language transformations that are available for multiple programming languages. However, often times these IDL-derived mappings preclude programmers from using native programming language constructs, such as generics, that are unavailable in IDL. The result is a suboptimal API that does not conform to the stylistic idioms of the target language, introducing a barrier to the adoption and use of DDS. Since 2012, the OMG has released DDS PSMs that derive directly from the DDS UML PIM, targeting languages like C++ and Java. These new PSMs leverage and conform to the standard data types and programming idioms of such programming languages, simplifying the adoption and use of DDS. Following that evolution, this RFP solicits proposals for a DDS PSM for the C# programming language

DDS Status Monitoring RFP
The Data-Distribution Service (DDS) provides a crucial connectivity platform to many mission critical systems. It is important to have a standardized means for monitoring the health status of the DDS platform during live operation and to use means that are robust to failures of the platform being monitored. This standard covers the information model and technical interfaces required. This RFP solicits proposals for the following: A data model defining the information required for the operational status monitoring of a DDS platform. Techniques, procedures, and interfaces to communicate the data model representing the status of the platform.

The objective of this RFP is to define a set of mechanisms to allow DDS infrastructures be deployed on, and leverage, TSN-enabled networks. To achieve this, the DDS standard(s) and implementations will need to be extended. From a DDS perspective, the integration points to be addressed for this are: Design-time system definitions to include TSN-related properties Run-time DDS implementations to leverage TSN network Deployment-time actions to instruct TSN-enabled equipment These mechanisms will define a foundation upon which different DDS vendors can create interoperable communications. Additionally, DDS vendors and others will be able to build tooling and other supporting mechanisms to facilitate the creation of DDS systems running over TSN networks.

Digital Receipt API v1.0 RFP
This RFP solicits proposals for a simplified digital receipt API in which retailers can enable the following: * API specifications that support sharing complete digital receipt data in a secure manner between various parties such as retailers, consumers, product manufacturers, and service providers. * Streamlined standard which specifies a common core of elements to be used in a digital receipt API, which can then be enriched and extended in a standard fashion with local requirements. * Provide the information and evaluation items list that indicates the actual use cases and digital receipt data.

Event Metamodel and Profile (EMP) RFP
This Request for Proposal solicits submissions for an Event Metamodel and Profile (EMP). Essentially, the EMP RFP requests a metamodel and profile for extending UML with capabilities applicable to the sensing and interpretation of events, such as monitoring, filtering, aggregation, and correlation. Submissions developed in response to this RFP will achieve the following:
  • Clarify semantics concerned with modeling events.
  • Establish Event modeling best practices utilizing OMG technologies.
  • Develop a MOF-compliant event metamodel to be used either standalone or via extending the existing UML metamodel with event modeling capabilities.
  • Enable event model interchange between tools via XMI.
It is expected that responses to this RFP will make good use of event modeling capabilities already supported by the OMG.

IDL4 to C++ Language Mapping RFP
Version 4 of the Interface Definition Language (IDL) specification extends the traditional IDL syntax and defines a comprehensive set of building blocks to categorize it. Such evolution of IDL requires the definition of a a new set of language mappings, because existing mappings, such as IDL to C++ and IDL to C++11, do not include complete coverage of the new constructs introduced in IDL version 4 and newer, and do not map well to the new building-block structure. This RFP solicits proposals for an IDL4 to C++ mapping.

Interface Definition Language v4 (IDL4) to Python Language Mapping RFP
Version 4 of the Interface Definition Language (IDL) specification extends the traditional IDL syntax and defines a comprehensive set of building blocks to categorize it. Such evolution of IDL requires the definition of a new set of language mappings, because existing mappings, such as IDL to Python, do not include complete coverage of the new constructs introduced in IDL version 4 and newer, and do not map well to the new building-block structure. This RFP solicits proposals for an IDL4 to Python mapping

Information Management Metamodel (IMM) RFP
This RFP solicits proposals for a standard metamodel to address the needs of Information Management. This includes the scope of the existing Common Warehouse Metamodel (CWM) standard but is extended to cover the following areas:
  • MOF2 Metamodel for Information Management (IMM)
  • UML2 Profile for Relational Data Modeling, with a mapping to the IMM metamodel and SQL DDL
  • UML2 Profile for Logical (Entity Relationship) Data Modeling, with a mapping to the IMM metamodel
  • UML2 Profile for XML Data Modeling, with a mapping to the IMM metamodel and XML Schema
  • UML2 Profile for Record Modeling, with a mapping to the IMM metamodel and COBOL Copybooks
  • A standardized Information Engineering data modeling notation with a mapping to the IMM metamodel

Linked Encryption Streams (LETS) RFP
This Request for Proposal solicits submissions that address standardization of Linked Encrypted Transaction Streams (LETS) that may be deployed in Distributed Immutable Data Objects (DIDO) ecosystems, among other scenarios. Examples of DIDOs are Blockchains, Distributed Ledger Technologies (DLT), InterPlanetary File System (IPFS), Distributed Data Service (DDS). Blockchains and DLTs are currently in use in products such as IOTA, Bitcoin, Ethereum, Bitcoin Cash, Litecoin, Dogecoin, Hyperledger, etc. This RFP solicits specifications for proposals for the following: - Linking methods for arranging transactions into ordered structures, or 'streams' - Methods for applying encryption and digital signing to transaction elements, transaction streams or parts of transaction streams - Optionally methods for extending the semantics of the relationships among message in linked transaction streams

Multiple Vocabulary Facility (MVF) RFP
To facilitate the understanding of formal models by both domain experts and software engineers, there is a need to provide for formal association of model elements to the business concepts that they represent. Business concept definitions are expressed in natural language, and the community that shares a model may include speakers of different natural languages. Expressing concept definitions in the language most convenient to the audience is often needed in order to achieve consistent understanding. Expressing business concepts in terms of multiple, alternative languages is the role of a multiple vocabulary facility tool. While a modeling language implementation might provide such capabilities as well, the more general need is for the modeling tool to have access to model element concepts and their associations to alternative vocabularies so that the model elements can be created, displayed, and referenced with terms of a selected vocabulary. The creation of concept definitions and associated term sets shall be performed by individual model developers or developed and shared by consortia for domains of interest. Therefore the Multiple Vocabulary Facility (MVF) must support the creation and maintenance of concepts and associated vocabularies that can be shared in a standard form of import and export. To achieve these capabilities, this RFP provides for:
  • a standard means for representing the relationship between model elements and the corresponding business concept definitions and multiple term sets;
  • a standard means for accessing terms of a selected vocabulary to express a model element concept and to interpret a selected vocabulary term as a reference to a particular model element representing the associated concept.
  • a standard form for import and export of vocabularies.
It is expected that the capability for linking model elements to natural language terms and definitions in multiple languages would also be useful for MOF metamodels.

OARIS 3.0 Plot Sharing RFP
This RFP solicits proposals to extend the OARIS specification to provide support for networked sensing including the following: - Plot Sharing - Fused Track Reporting - Common Track Numbering This proposed extension is primarily driven by use cases from the naval domain as is the case for previous versions of the specification.

Pedigree and Provenance Model and Notation (PPMN) RFP
This RFP seeks proposals that will provide a solution to the problem of exchanging and displaying pedigree (lineage) and provenance (ownership and custody) information in a standard way so as to facilitate the interoperability of and exchange of data betweentools and the organizations that use them for this type of data. While other industry standards cover sections of this domain, there are currently no standards that cover the breadth sought here, in particular both pedigree and provenance. Neither do these other standards use MOF-compliant languages and so they will not easily integrate within the BPM+ suite of languages. This RFP solicits a notation and a set of overlays notations that will work well with the existing and planned BPM+ standards. Further, the most prominent standard in use, the W3C PROV [PROV] standard is primarily about digital artifacts whereas the scope of this RFP includes physical things as well. And finally, this RFP solicits the ability to capture not only what did happen to entities but also what should happen to various types of entities. This last area is included so that proper planning can be performed as communities are formed that require tracking of the pedigree and provenance of the things being created, modified, exchanges, and destroyed. This RFP solicits proposals for the following: - Pedigree and Provenance Metamodel: Proposals will provide a metamodel for describing the pedigree and provenance information related to things of interest to stakeholders. This includes: - Pedigree: the lineage of things of interest, or how they came to be, - Ownership: the ownership history of things of interest, - Custody: the custodial history of things of interest to stakeholders, and - Extensibility Mechanism: the ability to extend the metamodel with additional metadata related to the things of interest, their pedigree and their provenance. Pedigree and Provenance Notation: Proposals will provide a notation with which to display or present pedigree and provenance information to users of tools that support this standard. It is envisioned that this notation be primarily graphical but that is not mandatory. Tabular or other forms or a combination of graphical, tabular and other forms is welcome. XML Schema for Model Interchange: Proposals will include an eXtensible Markup Language (XML) schema or set of schemas for exchanging pedigree and provenance information. Future RFPs will be issued to request a set of services for exchanging and/or managing pedigree and provenance information but that is not included in this RFP.

Precise Semantics for Uncertainty Modeling (PSUM) RFP
Uncertainty has been studied in various fields, such as philosophy, physics, statistics, and finance, to describe a situation of lacking knowledge about the state of a system and/or potential future outcome(s). Uncertainty is gradually gaining more and more attention in system/software engineering these days. In particular, complex systems, such as cyber-physical systems and self-adaptive systems, typically operate in complex and unpredictable environments. It is therefore important to face, understand and explicitly specify/model uncertainty in system/software engineering. This RFP solicits proposals for a metamodel that enables the following: " Capturing uncertainty and its related concepts; " Enabling measurements of uncertainty and its related concepts.

Precise Semantics of Time for Foundational UML RFP
The objective of this RFP is to solicit specifications defining more precise semantics of time in the context of executable UML models, in order to allow model checking and to reduce ambiguities in such models. By semantics we mean the underlying meaning of models, that is, the constraints that models place on the structure and runtime behavior of the specified system. In support of this objective, the RFP solicits proposals for the precise specification of the behavioral semantics for the metaclasses related to the modeling of time in UML. Proposals shall build on the precise semantics of Foundational UML (fUML), which specifies the execution semantics of a computationally complete and compact subset of UML 2 to support execution of activities, and be consistent with the Precise Semantics of UML State Machines (PSSM).

The DDS Real-time Publish-Subscribe wire protocol (DDSI-RTPS) specification uses a Model-Driven Architecture (MDA) to describe a Platform Independent Model (PIM) of the interoperability wire protocol and its Platform Specific Mapping (PSM) to the User Datagram Protocol (UDP). The existing standard specifies only a UDP mapping of the PIM that allows conforming implementations to interoperate over UDP. The objective of this RFP is to define a standard PSM to the Transmission Control Protocol (TCP), so that implementations conforming to this specification can interoperate over TCP. Responses to this proposal shall not modify or deprecate UDP-based interoperability or the RTPS PIM.

Robotic Service Ontology RFP
A service robot is a robot that provides services to humans, or on their behalf, in the environment in which they live or work; by "service", we mean physical services as well as information services that operate in or interoperate with their surroundings, and that are primarily designed to support interaction with people. Service robots are typically designed for consumer rather than commercial purposes. They operate semi- or fully autonomously to perform the services they are designed to deliver, and are capable of decision making and acting in real and unpredictable environments to accomplish specific objectives. To describe the kind of services, capabilities and tasks that such robots might perform, including the terminology used to support rich interfaces between these services, components, sensors, and other elements in the robot's environment, common vocabularies or ontologies defining the robotic services, the related behaviors, the underlying components, and their interfaces are needed. The service robot industry is expected to grow substantially in the coming decades. However, there is no common understanding of the services that might be provided by these robots. We need a common vocabulary or ontology in order to describe robotic services and the components that comprise those services. Such an ontology will assist not only in communications among robots and between robots and the humans they support but will enable developers of both robotic services and robotic functional components to compose higher order robotic services from well-defined, consistent building blocks (components) and have confidence that the resulting services are consistent will work together as designed. IEEE [IEEE1872] provides an ontology that focuses on core (generic) terminology and capability of robot systems at a relatively high level. This ontology includes some basic concepts and definitions that can be revised and extended to meet some of the emerging requirements identified by the robotics community, but does not address requirements specific to robotic services, particularly for service robots (i.e., robots that are designed to interact with people), or meet the requirements specified herein. This RFP solicits proposals for the following: o A set of basic ontologies that provide a semantic model of robotic services and related robotic functional components that can support communications and interoperability between robotic services and enable composition of such services

Semantic Information Modeling for Federation (SIMF) RFP
The SIMF RFP asks for submissions for a standard that addresses the federation of information across different representations, levels of abstraction, communities, organizations, viewpoints, and authorities. Federation, in this context, means using independently conceived information sets together for purposes beyond those for which the individual information sets were originally defined. The purpose of SIMF is to help federate information across different authorities, vocabularies and formats. Current conceptual and logical information modeling approaches tend to be focused on a particular information modeling problem, using a particular technical approach. Examples of such technical approaches include object modeling, DBMS modeling and exchange schema modeling. SIMF seeks to address the problem of information federation by specifying standards for conceptual domain modeling, logical information modeling and model bridging relationships. SIMF submissions will define, adopt and/or adapt languages to express the conceptual domain models, logical information models and model bridging relationships needed to achieve this federation. Many if not all of these capabilities can be achieved with expert application of multiple standards and technologies. SIMF is intended to unify and tailor these capabilities, providing a standard for tools that reduce the barrier to entry and overhead required to achieve federated information.

This RFP solicits a specification that complements established mechanisms for representation of structured data files submitted as business reports, typically financial reports to regulators, in formats such as XBRL, by - Applying a business modeling approach to report definition, making reports easier to develop; - Enabling business-level expression of rules in order to manage quality; - Facilitating reuse of information across multiple reports; - Allowing use with industry- or enterprise-standard information models and ontologies; - Allowing direct linkage with enterprise information sources for report data; - Providing alternative formats for reports to allow access by a greater variety of analytical tooling while providing interoperability with XBRL-based report definitions and report submissions.

SysML v2 API and Services RFP
This RFP complements the SysML v2 RFP, and specifies the requirements for an Application Programming Interface (API) that includes services to operate on SysML v2 models, and connect SysML v2 models with models in other disciplines. The API shall be implemented by SysML v2 modeling environments, and shall support a wide range of operations related to model query, model construction, model view/viewpoint management, model analysis, model management, and model transformation for SysML v2 models. A SysML model is typically used to represent the architecture of a system and needs to be connected to models originating from other disciplines to enable a seamless digital thread. These disciplines include, but are not limited to, mechanical, electrical, software, simulation, manufacturing, supply chain, logistics, operations, and regulation. By including services to connect SysML models with models originating in other disciplines, this RFP is facilitating seamless interoperability to enable a truly integrated system model. This RFP is dependent on the SysML v2 RFP. The timeline for submissions in response to this RFP will follow the timeline of submissions in response to the SysML v2 RFP at least by one OMG technical meeting cycle.

Systems Modeling Language (SysML) v2 RFP
This RFP specifies the requirements for the next generation of the OMG Systems Modeling Language (OMG SysMLŽ v2) that are intended to address many of the limitations of the current version of OMG SysMLŽ to enable the more effective application of model-based systems engineering (MBSE). In particular, the emphasis for SysML v2 is to improve the precision, expressiveness, interoperability, and the consistency and integration of the language concepts relative to SysML v1. SysML v2 will express the core concepts required to precisely specify a system, its elements, and its environment (i.e., the system model). The language will be specified as both a SysML profile of UML and as a SysML metamodel. A complementary SysML v2 API and Services RFP is intended to further enhance interoperability by specifying standard services to access SysML v2 models.

Tactical Decision Aids RFP
This RFP solicits proposals for an interface within a Command and Control (C2) system for modular applications that assist users with their tactical decision making processes. Example decisions from the domain of military and operational Command and Control systems include: " Identification " Classification " Correlation " Threat Evaluation " Kill Assessment To provide decision support functionality, these modular applications must have access to information describing the current situation (tactical picture) as well as current tactical plans, actions in progress to support them and the resources at the system's disposal. These applications must also have the means to make automated recommendations and recommendations for user approval. Particularly to promote innovation, the interface specification must support the decoupling of these modular applications from the C2 systems to which they contribute.

UnifiedPOS Fiscal API 2.0 RFP
This RFP solicits proposals for the following: A platform independent behavioral model to describe interactions between fiscal devices or services and applications that consume them. A standard Fiscal API to register retail transactions on a fiscal device or tax authority service. A standard Fiscal API to store data into a fiscal journal

UnifiedPOS V2 Model And POS Printer API RFP
This RFP solicits proposals for the following: A platform independent behavioural model to describe interactions between device services and applications that consume them. The new model should address the shortcomings of the UnifiedPOS V1 and provide a foundation for exposing devices as services. An API to query POS printer capabilities. An API to print information on paper rolls using receipt and journal stations of the POS printer. An API to print information on a form (typically a check or credit card slip) on the slip station of the POS printer.

Current Specification Revision Processes (available to members only):

Action Language for fUML 1.2 (ALF) RTF
Alert Management Service (ALMAS) 1.3 RTF
Command and Control Interface for Navigation Systems (C2INav) 1.2 RTF
Command and Control Message Specification (C2MS) 1.1 RTF
CubeSat System Reference Model Profile (CSRM) 1.1 RTF
DDS Consolidated JSON Syntax (DDS-JSON) 1.1 RTF
DDS Consolidated XML Syntax (DDS-XML) 1.1 RTF
DDS Extensible Types (DDS-XTYPES) 1.4 RTF
DDS Security 1.2 RTF
DDS-OPC UA Gateway 1.1 RTF
Decision Model and Notation 1.5 RTF
Diagram Definition 1.2 RTF
Essence 1.3 RTF
FACE Profile for UAF (FACE) 1.1 RTF
FIBO Business Entities 1.2 RTF
FIBO Financial Business and Commerce 1.1 RTF
FIBO Foundations 1.3 RTF
FIBO Indices and Indicators 1.1 RTF
IDL to C++11 1.7 RTF
IDL4 to C# Language Mapping (IDL4-CSHARP) 1.1 RTF
IDL4 to Java Language Mapping (IDL4-Java) 1.1 RTF
Interface Definition Language 4.3 RTF
Languages, Countries and Codes 1.3 RTF
MOF to RDF Mapping 1.1 RTF
Object Constraint Language 2.5 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
Open Architecture Radar Interface Standard (OARIS) 2.1 RTF
Requirements Interchange Format V1.3 (ReqIF) RTF
Risk Analysis and Assessment Modeling Language (RAAML) 1.1 RTF
Simplified Electronic Notation for Sensor Reporting (SENSR) 1.1 RTF
Software Fault Pattern Metamodel (SFPM) 1.1 RTF
SysML 1.7 RTF
SysPhS 1.2 RTF
TACSIT Data Exchange (TEX) 1.1 RTF
UML Profile for ROSETTA (UPR) 1.1 RTF
UML Testing Profile 2 (UTP2) 2.2 RTF
Unified Architecture Framework (UAF) 1.3 RTF
UnifiedPOS 1.15.1 RTF
UnifiedPOS 1.16.2 RTF
XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF
XTCE US Government Satellite Conformance Profile 1.1 RTF