Pending Requests for Comments:


Automated Technical Debt Measure RFC
Automated Technical Debt Measure RFC (document admtf/2017-03-01)
Automated Technical Debt Measure XMI file (document admtf/2017-03-03)
Automated Technical Debt Measure cover letter (document admtf/2017-03-06)
Automated Technical Debt Measure inventory file (document admtf/2017-03-05)

DDS-XML RFC
DDS-XML RFC cover letter (document mars/2017-02-19)
DDS-XML RFC inventory file (document mars/2017-03-04)
DDS-XML RFC zipped machine-readable files (document mars/2017-03-05)
DDS-XML RFC, updated draft clean (document mars/2017-03-01)

Pending Requests for Information:

Uncertainty RFI (document ad/2016-09-02)
# (automatically inserted in format file) # (insert descriptive text between the #process and #endprocess lines)


Pending Requests for Proposals:

Agent Metamodel and Profile (AMP) RFP (document ad/2008-09-05)
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.

Application Programming Interfaces (API) to Knowledge Bases (KB) RFP (document ad/2010-06-09)
The intent of this RFP is to request proposals for Application Programming Interfaces (API) to Knowledge Bases (KB). According to Wikipedia ([WIK-KB]), “a knowledge base is a special kind of database for knowledge management, providing the means for the computerized collection, organization, and retrieval of knowledge”. This RFP targets mainly the basic administration services as well as the retrieval and the modification of knowledge in a KB designed specifically for use with knowledge representation languages supported by OMG standards, including but not limited to those supported by the Ontology Definition Metamodel (ODM - http://www.omg.org/spec/ODM/1.0/). Proposals are sought that create a common set of APIs and interfaces for accessing namespaces and IRIs (internationalized uniform resource identifiers), documents, and other common infrastructure, some of which is modeled, for example, in the ODM RDFWeb package of the RDF metamodel, regardless of the target representation language, for knowledge representation languages that can be serialized in XML. The primary target is for accessing such KBs in the context of a tool, such as a parser, ontology editor, inference engine, or other applications where a uniform set of APIs and related services is desirable. APIs and service interfaces supporting basic queries, such as those that can be represented in SPARQL, are also desired. While this API shall be independent from the way the KB was populated and how the KB is designed and organized, the resultant API(s) and services shall be designed to complement and work in concert with ODM. It is understood that this effort may necessitate modifications to the ODM, including collaboration with ODM revisions underway to support OWL 2. This RFP solicits proposals for the following: API to retrieve raw information from a KB (resources, properties…); API to modify raw information in a KB; API to query knowledge in a KB (i.e., through reasoning); API to create instances: API to administrate the KB: add, import or remove ontology

Business Architecture Core Metamodel (BACM) RFP (document bmi/2017-03-07)
This RFP solicits proposals for a metamodel for core concepts of business architecture for business executives and other leaders to achieve the following: * Support business architecture modeling as an integration of multiple perspectives to ensure that the business architecture is consistent and enables more effective management of business complexities. * Provide views of the business architecture model that are at a level of abstraction appropriate for the understanding and analysis of business executives. * Provide models based on a standard that enables the exchange of models between different modeling tools to avoid vendor lock-in and promote competition for quality and continued improvement of modeling tools. * Support the development of consistent modeling techniques and methods to advance the business architecture discipline and support the training and certification of business architecture professionals. * Facilitate the integration of multiple models of business, whether based on OMG standards or not.

Coordination of Care Service (CCS) RFP (document health/2015-03-04)
The scope of this RFP is to define the functions or capabilities required for effective coordination of care. Recognizing that ongoing coordination of care is a collaborative activity between care team members, the Coordination of Care Service is intended to fill a void in communication that presently exists between systems and care stakeholders. This includes not only the "professional" care team, but extends to include the patient themselves and designated caregivers and family members as participants in the Care Team. Effective coordination of care involves care team collaboration, goal oriented care planning, care tracking, and interventional activities. This will include support for continual assessment and review. The ability of a care plan to support specialty care domains within the context of broader care planning is an essential feature, providing the ability to establish clinical contexts and support care planning for those contexts. This RFP will provide for the ability to: - Establish and maintain care team relationships across organizations and point-of-care systems - Enable the care team to contribute to a shared and dynamic care plan - Enable the care team to track changes through time - Enable the care team to communicate within the context of the care plan and the continuity of care record

Event Metamodel and Profile (EMP) RFP (document ad/2008-09-15)
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

Healthcare Ordering Service RFP (document health/2015-12-03)
The Ordering Service is intended to complement the existing portfolio of Service Oriented Architecture (SOA) services on the HL7 / OMG services roadmap. It manages electronic interactions between an order source and those providing requested fulfillment services, specifically recognizing that the consequences of an order are not necessarily enacted by the initial recipient, but may only be realized after a complex, multi-step workflow. The Ordering Service also defines functional behaviors surrounding the querying and management of an Ordering Service Catalog. The general behaviors of ordering, order fulfillment and results reporting are supported by appropriate Ordering Service interfaces; these operations are thought to be common regardless of the service or item being requested. This RFP solicits proposals for the following: o All necessary order creation, modification, query and retrieval functionality exposed to clients using an order management interface. o Functionality for interacting with order service catalogs, order sets and order catalog management. o Functionality supporting a workflow interface through which a system might query for orders of interest, update an order's status, retrieve requirements important to successfully execute an order, and otherwise manage order workflow. o Functionality for monitoring order status and service operations, exposed as a) an order monitoring interface, and b) an ordering service monitoring interface. o An additional interface, the order notification interface, enabling one ordering service to notify another ordering service about additions or changes to the orders it maintains.

IEF Reference Architecture RFP (document mars/2014-03-17)
The Information Exchange Framework (IEF) is an OMG initiative to develop a family of specifications for policy-driven, data-centric information sharing and safeguarding (ISS) services. These services target the automation of key policy decision and enforcement points to enable responsible information sharing across a broad range of business and operational scenarios. This Request for Proposal (RFP) seeks submissions for an overall reference architecture, reference model, and supporting materials for the IEF. The IEF Reference Architecture (RA) will be used to steer the overall IEF effort and broaden general understanding of domain requirements. The domain focus of the IEF RA includes interagency information sharing, often challenged by rapid, unpredictable changes in operational contexts (e.g., threat, risk, roles & responsibilities, scale, scope, and severity), e.g.: 1. Military (coalition and Civilian-Military) operations; 2. National Security; 3. Public Safety; 4. Crisis Management; 5. Border Security; 6. Emergency Management; and 7. Humanitarian Assistance. The IEF is focused on these environments because they require higher degrees of flexibility, agility and adaptability: often more than traditional solutions can satisfy. This RFP solicits proposals for a reference architecture for the IEF comprising: o A Platform Independent Model (PIM) for the IEF; o At least one Platform Specific Model, associating PIM elements to applicable standards; and o Operating concept and use cases for the IEF.

Information Management Metamodel (IMM) RFP (document ab/2005-12-02)
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

MDMI 2.0 RFP (document health/2017-03-08)
This RFP elicits a technical specification to address the above business needs. The MDMI 1.0 Specification addressed several of these considerations, but based upon industry implementation experience, enhancement areas have been identified and are the basis for conducting this revision effort. Previous goals addressed in the 1.0 specification (carried forward into this RFP) include: " Reducing significantly the cost and time needed to define data transformations from one message format to another. " Handle versioning issues as particular message formats evolve over time. " Allow the expedited adoption of new standards - as mapping the new standard to the existing standard will allow applications to continue to use the legacy standards thus greatly reducing the cost of new standards adoption. " Improve the interoperability and processing of end-to-end multi-step business transactions that are based on multiple message formats. Extending the functional coverage of MDMI 1.0, this RFP includes the following scope additions: " Make the MDMI Referent Index a component of the specification and add the capability to search and discover the precise Business Elements. " Make it easier for Healthcare Domain participants to understand and adopt the Standard. " Address the other issues already identified that will enhance the specification, identified in an MDMI Issues Document (health/17-03-02)

MOF to RDF Structural Mapping in Support of Linked Open Data RFP (document ad/2009-12-09)
RDF and Linked Open Data (LOD) have become important technologies for exposing, managing, analyzing, linking and federating data and metadata. This set of RDF based technologies, sometimes known as the “Semantic Web” or “Web 3.0”, are emerging as the lingua franca of data on the web. Major initiatives such as the President’s open government initiative are moving to the use of RDF & Linked Open Data as the foundation for publishing all government data and metadata in support of transparency. OMG & MOF based models should be a part of the LOD and Web 3.0 data cloud. The objective of this RFP is to define a structural mapping between OMG-MOF models and RDF to provide for better integration of MDA and LOD, to enable the ability to apply LOD capabilities to MOF compliant models and to make the information available in MOF compliant models available as LOD web resources. Any MOF based model should be able to become a LOD resource.

Metamodel Extension Facility RFP (document ad/2011-06-22)
This RFP solicits proposals for a Facility for extending and integrating metamodels that will complement and may eventually replace the current UML Profiles capability. The new Facility will be: o Able to replicate all of the semantic capabilities of the current profile mechanism; o Applicable to any metamodel or well-formed metamodel subset, not just UML; o Defined in a technically sound manner; o Able to define new diagram mappings; o Integrated with OMG platform technologies.

Multiple Vocabulary Facility (MVF) RFP (document ad/2016-03-04)
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.

OPC-UA/DDS Gateway RFP (document mars/2015-09-02)
Data Distribution Service (DDS) is a family of standards from the Object Management Group (OMG) that provide connectivity, interoperability and portability for Industrial Internet, cyber-physical, and mission-critical applications. The DDS connectivity standards cover Publish-Subscribe (DDS), Service Invocation (DDS-RPC), Interoperability (DDSI-RTPS), Information Modeling (DDS-XTYPES), Security (DDS-SECURITY), as well as programing APIs for C, C++, Java and other languages. OPC Unified Architecture (OPC-UA) is an information exchange standard for Industrial Automation and related systems created by the OPC Foundation. The OPC-UA standard provides an Addressing and Information Model for Data Access, Alarms, and Service invocation, layered over multiple transport-level protocols such as binary TCP and Web-Services. DDS and OPC-UA exhibit significant deployment similarities: Both enable independently developed applications to interoperate even when those applications come from different vendors, use different programming languages or run on different platforms and operating systems. Both have significant traction within Industrial Automation Systems. Both define standard protocols built on top of the TCP/UDP/IP Internet stacks. The two technologies coexist within the same application domains. However applications that use DDS do not interoperate with those that use OPC-UA. Technologies that bridge between DDS and OPC-UA have been developed by vendors and users. However these are based on custom mappings and therefore cannot be relied to work across vendors and products. The objective of this RFP is to define a standard, vendor-independent, configurable gateway that enables interoperability and information exchange between systems that use DDS and systems that use OPC-UA.

Safety and Reliability for UML RFP (document ad/2017-03-05)
This RFP solicits proposals for a profile and/or optionally a model library for the Unified Modeling Language that enables the following: * Capturing safety and reliability information in a system model. * Reasoning on the safety and reliability information, both directly on the model and indirectly via model transformations. * Visualising safety and reliability information. * Exchanging safety and reliability information between a system model and external tools. * Tracing between safety information, reliability information, and other information stored in a system model.

Semantic Information Modeling for Federation (SIMF) RFP (document ad/2011-12-10)
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.

TACSIT Data Exchange RFP (document c4i/2015-03-20)
The domain of military and operational Command and Control systems is characterized by a huge variety of underlying computing platforms. A standard based interface to common TACtical SITuation (TACSIT) services is thus essential for interoperable and open systems. In this scope, a first standard has already been issued by the OMG: the TACSIT Controller Interface consists of a set of interfaces to interact with TACSIT display systems. This RFP solicits now proposals for data interfaces to TACSIT systems. More specifically, it requests: • The standardisation of the data that need to be exchanged with TACSIT systems; • The standardisation of the interfaces needed to exchange data from/to TACSIT systems.

UML Operational Threat & Risk Model RFP (document sysa/2014-06-17)
In the broadest sense, organizations manage threats and risks in order to provide a systematic response to uncertainties and enhance situational awareness. Multiple communities have developed data and exchange schema and interfaces for sharing information about threats, risks and incidents that impact important government, commercial and personal assets and privacy. While each of these schema and interfaces provides value for a specific community it is difficult to federate these multiple representations to arrive at broad-based planning, simulation, assessment, situational awareness and forensics, and to then enact the appropriate courses of action. Cyber related attacks have added a new dimension that stresses traditional assessment, monitoring and mitigation strategies. This RFP calls for a conceptual model for operational threats and risks that unifies the semantics of and can provide a bridge across multiple threat and risk schema and interfaces. The conceptual model will be informed by high-level concepts as defined by the Cyber domain, existing NIEM domains and other applicable domains, but is not specific to those domains. This will enable combined Cyber, physical, criminal and natural threats and risks to be federated, understood and responded to effectively. Out of scope for this RFP is non-operational business relevant risk such as marketplace risk, credit risk, legal risk, project management risk, etc. The conceptual model will have an information exchange format based on NIEM and an explicit mapping to STIX . Other exchange formats, such as CAP may be supported as well.

UML Testing Profile V2 (UTP2) RFP (document ad/2013-12-08)
This RFP solicits proposals for the following: a UML Testing Profile as a successor specification of the UML Testing Profile 1.2 a UML Testing Profile that is applicable to a variety of domains and methodologies a UML Testing Profile enables the specification of test cases for different quality attributes and on different level of abstractions a UML Testing Profile that allows for test generation and the precise specification of test coverage

UML® Profile for ArchiMate® and ArchiMate® Meta-model RFP (document bmi/2014-12-03)
ArchiMate® is a visual design language developed by The Open Group®. It is intended to enable the description of enterprise architecture domains and their relationships and dependencies. The ArchiMate language has been used to describe portfolios of software products and components in a way akin to how a Computational Independent Model (CIM) is used in an implementation of Model Driven Architecture® (MDA®). More detailed models that would conceptually correspond to Platform Independent Models (PIM) and Platform Specific Models (PSM) are better described using UML®, BPMN, and other specifications developed by the Object Management Group® (OMG®). This specification is intended to facilitate that development approach by creating a UML Profile for ArchiMate and a MOF® meta-model of ArchiMate, thus enabling ease of use of Archimate in combination with UML, BPMN and other OMG modelling language specified in MOF, in the same tool. This RFP solicits proposals for the following: o A UML Profile for ArchiMate o A MOF Meta-model of ArchiMate

eXtremely Resource Constrained Environments DDS (DDS-XRCE) RFP (document mars/2016-03-21)
This RFP solicits proposals for a client-to-agent protocol for DDS, addressing extremely resource constrained environments characterised by aggressive sleep cycles, extra small MTUs, constrained bandwidth and computational power

Current Specification Revision Processes (available to members only:

2nd Languages, Countries and Codes 1.0 FTF
2nd SACM 2.0 FTF
ADM KDM 1.5 RTF
AMI4CCM 1.2 RTF
Application Instrumentation 1.1 RTF
Archetype Modeling Language (AML) FTF 2
Automated Enhancement Points (AEP) 1.1 RTF
Automated Source Code Maintainability Measure 1.1 RTF
Automated Source Code Performance Efficiency Measure 1.1 RTF
Automated Source Code Reliability Measure 1.1 RTF
Automated Source Code Security Measure 1.1 RTF
Automated Technical Debt Measure 1.0 FTF
BMM 1.4 RTF
DDS Consolidated XML Syntax (DDS-XML) 1.0 FTF
DDS Security 1.1 RTF
DDS-PSM-Cxx v1.1 RTF
DDS-PSM-Java v1.1 RTF
DDS-XTYPES 1.3 RTF
DDSI-RTPS 2.3 RTF
DOL 1.0 FTF 2
DateTime Vocabulary (DTV) 1.4 RTF
Decision Modeling and Notation 1.2 RTF
Diagram Definition 1.2 RTF
Essence 1.2 RTF
FIBO Business Entities 1.2 RTF
FIBO Financial Business and Commerce 1.1 RTF
FIBO Indices and Indicators 1.1 RTF
GEMS 1.5 RTF
Hardware Abstraction Layer for Robotic Technology 1.0 FTF 2
IDL to C++11 1.3 RTF
IEF Reference Architecture 1.0 FTF
Information Exchange Packaging Policy Vocabulary (IEPPV) 1.1 RTF
MARTE 1.2 RTF 2
MOF 2.6 RTF
Object Constraint Language 2.5 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
PSSM 1.0 FTF
Precise Semantics of UML Composite Structures 1.2 RTF
QVT 1.4 RTF
RPC over DDS 1.1 RTF
Records Management Services V1.1 (RMS) RTF
Requirements Interchange Format V1.3 (ReqIF) RTF
Robotic Interaction Service Framework 1.2 RTF
SBVR 1.5 RTF
Structured Metrics Metamodel 1.2 RTF
Structured Patterns Metamodel Standard (SPMS) 1.2 RTF
Structured Patterns Metamodel Standard (SPMS) 1.3 RTF
SysML 1.6 RTF
SysPISF 1.0 FTF 2
TestIF 1.1 RTF
UCM 1.0 FTF
UCM 1.1 RTF
UML 2.6 RTF
UML Profile for BPMN Processes 1.1 RTF
UML Testing Profile 2 FTF
UPDM 2.2 RTF
Unified Architecture Framework (UAF) 1.0 FTF
Unified Architecture Framework (UAF) 1.1 RTF
VDML 1.1 RTF
Web-enabled DDS 1.1 RTF
XMI 2.6 RTF
XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF
fUML 1.4 RTF