Pending Requests for Comments:
All OMG work in progress deadlines in chronological order
Automated Source Code Quality Measures RFC
Automated Source Code Quality Measures RFC – clean (document admtf/2018-12-01)
Cover Letter for Automated Source Code Quality Measures RFC (document admtf/2018-12-04)
Inventory for Automated Source Code Quality Measure RFC (document admtf/2018-12-05)
XMI for Automated Source Code Quality Measures (document admtf/2018-11-02)
FIBO Version 2 RFC
Conceptual Model (ancillary) in UML (Magic Draw v18.5) with CCM profile applied (document finance/2018-08-14)
FIBO 2 RFC Annex B: Business Entities - Errata3 (document finance/2018-09-24)
FIBO 2 RFC Annex D: Derivatives - Errata3 (document finance/2018-09-25)
FIBO 2 RFC Annex E: Financial Business and Commerce - Errata3 (document finance/2018-09-26)
FIBO 2 RFC Annex F: Foundations - Errata3 (document finance/2018-09-27)
FIBO 2 RFC Annex G: Indices and Indicators - Errata3 (document finance/2018-09-28)
FIBO 2 RFC Annex J: Securities - Errata3 (document finance/2018-09-29)
FIBO v2 RFC (document finance/2018-09-23)
FIBO v2 RFC - Errata2-Redline (document finance/2018-09-22)
FIBO v2 RFC - RDF/XML-serialized OWL Metadata Ontologies (informative) (document finance/2018-08-05)
FIBO v2 RFC - RDF/XML-serialized OWL Ontologies (normative) (document finance/2018-08-04)
FIBO v2 RFC cover letter (document finance/2018-08-02)
FIBO v2.0 additional ancillary file (document finance/2018-09-01)
Revised Inventory (document finance/2018-09-30)
XMI-serialized Conceptual Model (informative) with Conceptual Modeling profile applied (document finance/2018-08-15)
Pending Requests for Information:
All OMG work in progress deadlines in chronological order
Command and Control User Definition Language RFI (document space/2018-09-05)
MARTE 2.0 RFI (document ad/2018-09-04)
Pending Requests for Proposals:
All OMG work in progress deadlines in chronological order
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.
Command and Control Interface for Navigation (C2INav) RFP (document c4i/2017-12-07)
This RFP solicits a Command and Control System (C2) based Navigation System Interface that will address the relevant interfaces for the C2 systems. The Command and Control Interface for Navigation (C2INav) standard will primarily define the interface for applications to consume distributed navigation and stabilization data: specifically platform location, orientation, and movement information suitable for Naval, Land, or Air based C2 Systems.
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
CubeSat System Reference Model (CSRM) RFP (document space/2018-09-04)
Model-Based Systems Engineering (MBSE) is the formalized application of modelling to support systems engineering. The International Council on Systems Engineering (INCOSE) established the MBSE Initiative to promote, advance, and institutionalize the practice of MBSE utilizing Object Managements GroupsTM (OMGTM's Systems Modeling LanguageTM (SysMLTM). This RFP requests a standard CubeSat System Reference Model (CSRM). The CSRM will be a SysML compliant and platform-independent template model that provides building blocks that can be specialized to support MBSE CubeSat design. A common, reusable model supports lowering the cost of development and increasing the quality of CubeSat spacecraft and ground system design, whether embraced by researchers, government, or commercial engineering teams.
DDS Consolidated JSON Syntax (DDS-JSON) RFP (document mars/2018-03-01)
This RFP solicits proposals for a consolidated JSON syntax to represent DDS resources, such as Data Types, QoS Policies, DDS Entities, and DDS Data.
DDS Status Monitoring RFP (document c4i/2017-09-07)
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.
DDS-TSN RFP (document mars/2018-09-10)
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.
EDI Standard for Non-Medical Workplace Benefits Request For Proposal (document wb/2018-06-05)
Each Insurance Carrier has their own proprietary data format which aligns with their administrative systems. There tends to be a lot of commonality with regards to data needs between the various benefits administration platforms. To that extent, a common definition with a common vocabulary can be defined. As an industry, we are seeing a movement away from traditional worksite enrollment to a more group based approach. It is to this extent that a common definition will assist human resources information and benefits administration platforms in simplifying their Electronic Data Interchange (EDI) development based on this definition as it pertains to benefits enrollment. As each Insurance Carrier may also have unique attributes, underwriting and business rules, the flexibility for such divergences will be built into the common format. This will allow for communication on the more complex Insurance Carrier specific cases. The project objective is to develop a common specification among multiple Insurance Carriers for the transmission of member enrollment-related data and ongoing transactions for workplace benefits that are tested, adopted, and implemented.. The goal for the specification is that the resulting EDI feeds and data exchanges will be easily consumed by Insurance Carriers and developed by enrollment and benefits administration technology companies in the marketplace. Secondarily, by having a common specification, our long-term objective is to reduce customer onboarding timelines and reduce the ongoing costs to Insurance Carriers, benefits administration platforms, brokers, and employers. Such scalability is important given the changing landscape of benefits enrollment
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.
FACE™ Profile for UAF RFP (document c4i/2018-09-03)
This RFP solicits proposals for a Future Airborne Capability Environment (FACE) Profile for use with the OMG Unified Architecture Framework (UAF) to allow inclusion of elements from The Open Group FACE™ Technical Standard in UAF architectures. Additionally, UAF mechanisms (tables, aggregations, etc) are sought to support the organization and presentation of FACE architectural objects in UAF. This profile would provide a FACE-aware whole-enterprise context that places FACE components within a larger system-of-systems architecture, enabling description and analysis of the impact of the FACE components on complex systems.
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.
IDL4 to C# Language Mapping RFP (Clean) (document mars/2018-12-02)
Version 4 of the Interface Definition Language (IDL) specification extended the traditional IDL syntax and defined a comprehensive set of building blocks to categorize it. This evolution requires a new set of IDL to language mappings to leverage the new IDL constructs and to adapt to the new building block-based document structure. Moreover, it requires mappings to popular programming languages, such as C#, for which there was no existing language mapping. This RFP solicits proposals for an Interface Definition Language (IDL) to C# mapping.
Information Exchange Framework Information Exchange Packaging and Processing Service (IEPPS) RFP (document mars/2017-12-12)
The Information Exchange Framework (IEF) Packaging and Processing Service (PPS) enables the automation of user defined policies governing the sharing and safeguarding of data content; policies conforming to the Information Exchange Packaging Policy Vocabulary (IEPPV) (Request for Proposal (RFP): http://www.omg.org/spec/IEPPV/1.0/). This RFP solicits proposals for a service specification describing the application-visible interface(s) and behavior of the packaging and processing services outlined in the IEF Reference Architecture (http://www.omg.org/spec/IEF-RA/1.0/Beta1/). The IEPPS must provide services including: " Data Packaging: the aggregation, transformation, marking (e.g., tagging and labeling), redaction, and formatting of data for receipt in accordance with user defined policy; " Data Processing: the parsing, transformation and marshaling of received data conforming to user specified formats. The proposals must describe how the core functions of the IEPPS (including their interfaces), and interaction of the IEPPS with other IEF components, standard middleware and communication networks, data management systems, and user applications
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
Interface Definition Language v4 (IDL4) to Java Language Mapping RFP (document mars/2017-12-21)
This RFP solicits proposals for an Interface Definition Language (IDL) to Java mapping. The existing IDL-to-Java mapping (IDL to Java Language Mapping, Version 1.3 formal/2008-01-11) does not include complete coverage of the new constructs introduced in IDL version 4 and newer. Further, it does not take advantage of Java 5 and newer language constructs. It is desired to have an updated IDL to Java Language mapping that addresses these issues.
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:
- Able to replicate all of the semantic capabilities of the current profile mechanism;
- Applicable to any metamodel or well-formed metamodel subset, not just UML;
- Defined in a technically sound manner;
- Able to define new diagram mappings;
- 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.
OARIS v2.0 (Additional Sensors) RFP (document c4i/2018-06-08)
This RFP solicits proposals to extend the OARIS specification, creating OARIS version 2.0, to provide greater support for additional sensor types and their command and control requirements - sensor types such as: o Sonar Electronic Surveillance (of Radar and other radio frequency transmissions) o Electro-Optic and Infra-Red o The RFP also invites additional PSMs that have applicability for different sensor types.
Precise Semantics for Uncertainty Modeling (PSUM) RFP (document ad/2017-12-01)
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 (document ad/2017-12-07)
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).
RTPS TCP/IP PSM for DDS Interop RFP (document mars/2017-09-24)
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 (document robotics/2018-12-03)
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
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.
Simple Electronic Notation for Sensor Reporting (SENSR) RFP (document mantis/2018-09-10)
This RFP solicits proposals for a metamodel suitable for describing serialized data streams emitted by sensors, and how that data should be interpreted. This metamodel shall allow the production of tools to enable automated, unambiguous interpretation of the emitted sensor data through configuration of a system, or production of code for execution. Self-contained environmental sensors are becoming ubiquitous in our daily lives, nowhere more so than in the emerging Internet of Things (IoT) industry. The Industrial Internet Consortium (IIC) is the leading IoT technology organization, and has been operating a number of official Testbeds for experimenting with hardware sensors in dynamically networked environments. These IIC Testbeds allow for systematic investigation of a number of applications, including health care, transportation and shipping, ecological resource management, and safe and efficicent tool use in industrial settings. One emergent need has been for the manufacturers of sensors to be able to publish the required interpretation of the data that they produce via an Electronic Data Sheet. Pursuant to that need, this RFP requests specification proposals that provide the following: - a platform and vendor-independent metamodel for describing available data provided by hardware sensors, - an optional library of data types to facilitate the above sharing of interpretation.
SysML v2 API and Services RFP (document ad/2018-06-03)
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 (document ad/2017-12-02)
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.
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.
UPOSVer.1.16 Retail Communication Service Device RFP (document retail/2018-09-10)
This RFP solicits proposals for the following: Define an interface standard so that applications can be developed in the programming language and development environment of choice. The Retail store system user should be able to select their desired localization functional services that the robot is capable of and disable all others. This is because robots can have an overwhelming number of functions, such as speaking several languages and making appropriate gestures, but they are not required for every retail scenario. E.g., domestic use only deployments would not need options for international languages only the local domestic languages.
UnifiedPOS Fiscal API 2.0 RFP (document retail/2018-09-09)
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 (document retail/2017-09-05)
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):Alert Management Service (ALMAS) 1.1 RTF
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
BMM 1.4 RTF
CORBA 3.4 RTF
DDS Consolidated XML Syntax (DDS-XML) 1.1 RTF
DDS Security 1.2 RTF
DDS-PSM-Cxx v1.1 RTF
DDS-XTYPES 1.3 RTF
DOL 1.1 RTF
Decision Model and Notation 1.3 RTF
Diagram Definition 1.2 RTF
Essence 1.3 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.4 RTF
IDL to C++11 1.5 RTF
Information Exchange Packaging Policy Vocabulary (IEPPV) 1.1 RTF
Interface Definition Language 4.3 RTF
Languages, Countries and Codes 1.1 RTF
MARTE 1.3 RTF
MOF 2.6 RTF
OARIS 1.1 RTF
Object Constraint Language 2.5 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
PSSM 1.1 RTF
QVT 1.4 RTF
RPC over DDS 1.1 RTF
Requirements Interchange Format V1.3 (ReqIF) RTF
SACM 2.1 RTF
SBVR 1.5 RTF
Structured Patterns Metamodel Standard (SPMS) 1.3 RTF
SysML 1.6 RTF
SysML 1.7 RTF
SysPhS 1.1 RTF
TOIF 1.4 RTF
UCM 1.2 RTF
UML 2.6 RTF
UML Profile for BPMN Processes 1.1 RTF
UML Testing Profile 2 (UTP2) 2.1 RTF
Unified Architecture Framework (UAF) 1.1 RTF
Web-enabled DDS 1.1 RTF
XMI 2.6 RTF
XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF
XTCE US Government Satellite Conformance Profile 1.1 RTF
fUML 1.5 RTF