Public Schedule

Current OMG Technology Adoption Processes Under Way
Last updated: Friday, 02-Aug-2013 07:01:14 EDT

Specifications which have been approved by the OMG membership are available to everyone, but only OMG members have access to specifications under development. This page lists OMG Request processes for technology submissions which are open to both members and the general public for comment or response. For more information on the OMG technology adoption process, please see the Process Technology FAQ.

Please note that the actual Request documents are freely available; simply click on the document number below to get the document in several different formats. However, the internal mechanics of the OMG process are available only to members by clicking on the process name.

A catalog of our published specifications is available here. If you're interested in learning more about the OMG and the benefits of becoming a member, please contact our Business Development staff.

Pending Requests for Information:

Contract Information Exchange Model Request For Information (document bmi/2013-03-06)
Providing standardized Contract Information Exchange Model (CIEM) facilitates the acquisition of goods and services through the open, exchange of contractual information between offerors and bidders during the transparent negotiation process. The dynamic, rapid, agile and flexible requirements of Cloud Computing make it an excellent usage scenario for CIEM. However, the acquisition process is far larger than cloud services. The CIEM is intended to support the larger process. The CIEM is also intended to support third party, automated or semi-automated brokers in a transparent, repeatable, non-reputable, enforceable, auditable acquisition process. The CIEM may include taxonomies, ontologies, rules, and data structures required to capture the kind of agreement, scope of work to be performed and the terms and conditions associated with the scope of work. The purpose of this RFI is to identify existing whole or partial standards applicable to CIEM, identify gaps between the standards and to solicit proposals for filling the gaps.

Hardware Abstraction Layer for Robots RFI (document robotics/2013-06-06)
This RFI is the first step towards standardization of the application programming interface to access hardware devices such as motors and sensors. Currently, porting existing software to different systems, including device drivers in the development of embedded systems, requires considerable effort. For example, turning on an LED or operating a motor on different hardware may require many days because the application program interfaces to control sensors and motors are uniquely defined by the device manufacturers. It is necessary to unify these interfaces. A Hardware Abstraction Layer is an open platform to standardize the specifications of the software implementation of robotics and control systems. A Hardware Abstraction Layer provides the base portion of a software platform for robotics and control systems, and aims to enable applications to run on different hardware. This increases the portability and reusability of the software, resulting in improved quality, lower costs and improved productivity. It is expected to improve convenience for users and developers.

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 Instrumentation RFP (document c4i/2011-12-03)
Command, Control, Computers, Communication, and Intelligence (C4I) systems are often distributed real-time systems with many applications integrated over a computer network. Understanding and debugging these systems is challenging, especially as they grow in complexity. Live run-time access to internal application status and statistics is critical to the understanding, monitoring, and management of these systems. Unfortunately, while tools are available to collect the various types of operating-system level information, there is no standard way to instrument application code and distribute the resulting data to other applications and analysts. The objective of this RFP is to provide a standard method to collect and distribute internal application data and status information by defining: o A minimally intrusive API for application instrumentation. The application developer would use this API to instrument the application code to record key variables as it is running. The collected data can then be processed in a lower priority thread and/or published on the network. o A distribution mechanism that allows configuration of quality-of-service parameters for distributing the collected data. o Configuration and remote control. A remote control mechanism that allows the control of the data collection and distribution of data at run-time.

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

Archetype Modeling Language (AML) (A UML Profile for Modeling Archetypes) RFP (document health/2012-07-01)
The objective of this RFP is to provide a standard for modeling Archetype Models (AMs) using UML, to support the representation of Clinical Information Modeling Initiative (CIMI) artifacts in UML. Archetypes are Platform Independent Models (PIMs), which are developed as a set of constraints on a specific Reference Model (RM). This RFP solicits proposals for an UML Profile, to be known as the "Archetype Modeling Language" (AML). The AML Profile will be developed as an aggregation of three sub-profiles, which together meet the requirements of archetype modeling. The three sub-profiles of the AML Profile will include: - Reference Model Profile (RMP): This profile will enable the specification of reference models, upon which archetypes can be based. - Constraint Model Profile (CMP): This profile will support the specification of constraints on a given reference model, to enable the development of archetypes, including Clinical Information Models (CIMs). - A Terminology Binding Profile (TBP): This profile will support the binding of information models to terminology, with optional support for binding to CTS2. Terminology bindings will include:
1. Value Bindings: Linkage of the data model to value domains, which restrict the valid value of an attribute to a set of values that corresponds to a set of meanings recorded in an external terminology;
2. Semantic Bindings: Defining the meaning of model elements, using concepts in an external terminology; and
3. Constraint Bindings: Specifying constraints on the information model, using concepts and relationships defined in an external terminology. This set of three UML sub-profiles (which together constitute the AML) will enable the specification of CIMI clinical model content (using the CIMI Reference Model), and the generation of CIMI clinical model artefacts, such as the Archetype Definition Language (ADL). While the transformation of AML models to an instance of the Archetype Object Model v1.5 (AOM-1.5) is optional, this transformation must be possible. The Archetype Definition Language (ADL) is a serialization of the Archetype Object Model.

Common Variability Language (CVL) RFP with AB changes (document ad/2009-12-03)
The objective of this RFP is to enable the specification of the variability in product line models in order to support seamless product line modeling across the whole product line engineering process. This CVL RFP requests a specification language including a metamodel, semantics and concrete syntax for variability specification. Variability specifications shall relate to a base product line model that describes the whole product line and shall comprise: a variability model with the following elements: a model of possible choices and relationships between those choices and the base model resolution models which resolve variability (by a set of choices) and thus define specific product models. CVL shall support base models in languages that are defined by means of MOF-compliant metamodels, including UML and Domain Specific Languages.

DDS Security RFP (document mars/2010-12-37)
The Data Distribution Service for Real-Time Systems (DDS) is the Object Management Group (OMG) standard for data-centric publish subscribe. The objective of this RFP is to define the set of Extensions to DDS required to provide Information Assurance for systems built using DDS.

Decision Model and Notation RFP (document bmi/2011-03-04)
This RFP solicits proposals for a standard Decision Model notation and metamodel and associated interchange format. Decision Models are developed to define how businesses make decisions, usually as a part of a business process model (covered by the OMG BPMN standard in Business Process Management Solutions). Such models are both business (for example, using business vocabularies per OMG SBVR) and IT (for example, mapping to rule engines per OMG PRR in Business Rule Management Systems). DMN will potentially galvanize the business analyst community into modeling decisions with vigor and to the subsequent benefit of their processes.

Dependability Assurance Framework For Safety-Sensitive Consumer Devices RFP (document sysa/2013-03-20)
The term "Safety-Sensitive Consumer device" (SSCD) refers to a category of industrial products used by consumer users, including automobiles, service robots, medical devices and clinical systems, and smart houses. Unlike traditional industrial machinery, such consumer devices must be dependable because they are used in diverse, open and dynamic environments where the need for safety, reliability and even availability of such devices is no longer an option but a requirement. The challenge is to develop a solution that satisfies this dependability requirement in cost-efficient way, preserving the affordable prices of SSCDs for the mass-market. A Dependability Assurance Framework (DAF) extends engineering approaches with additional viewpoints describing the assurance case, conceptual model for describing properties and process models. This would allow us to justify given properties throughout engineering processes by using explicit argumentation and evidence. The objective of this RFP is to produce a specification for building justifiably dependable SSCDs by specifying: 1. One or more Dependability Conceptual Models (DCMs) defining the factors of dependability, 2. One or more templates to be used to construct Dependability Assurance Cases (DACs) for SSCDs, and 3. One or more Dependability Process Models (DPMs) that define rapid and iterative processes for engineering dependable SSCDs. The response is expected to include generic customizable templates for DAC, as well as generic models for DCM and DPM, all supported by specific examples.

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

Finite State Machine Component for RTC (FSM4RTC) RFP (document robotics/2013-06-11)
The Robotic Technology Components (RTC) is an Object Management Group (OMG) specification for the component model and certain important infrastructure services applicable to the domain of robotic software development. In robotic software development, Finite State Machines (FSMs) are frequently used (even within a single system) in various styles and users want to reuse them. Moreover communication between RTC components and between state machines is done using some data structures through well-defined input/output ports in order to communicate state information. Although the RTC provides the specification of FSM components, it does not provide data models and methods/operations to be used in the FSM components in order to send events with parameters to components, get current states, send/receive the notification of state transitions and the definition of FSM. These features are usually required to simply interface an FSM with external tools for monitoring purposes. This RFP solicits proposals for an extension to the RTC specification as a solution to these problems. This extension will make the FSM component of RTC more applicable to real robotic software development.

Foundation for the Agile Creation and Enactment of Software Engineering Methods RFP (document ad/2011-06-26)
An agile approach to software engineering methods is one that supports practitioners of software engineering (architects, designers, developers, programmers, testers, deployers, analysts and project managers) in dynamically adapting and customizing their methods during the preparation and execution of a project, controlled through company specific governance, use of examples and other means. In contrast to previous approaches in this area, which have provided support mainly for process engineers, the goal here is to provide direct support for practitioners as the main target group. The objective of this RFP is to obtain a foundation for the agile creation and enactment of software engineering methods (that themselves may be agile or more traditional) by development practitioners themselves. This foundation is to consist of a kernel of software engineering domain concepts and relationships that is extensible (scalable), flexible and easy to use, and a domain-specific modeling language that allows developers to describe the essentials of their current and future practices and methods. These practices and methods can then be supported by tools based on this common foundation, and they can further be composed, simulated, applied, compared, enacted, tailored, used, adapted, evaluated and measured by practitioners as well as taught and researched by academic and research communities

Information Exchange Framework (IEF) Information Exchange Policy Vocabulary (IEPV) RFP (document mars/2011-03-15)
The objective of Information Exchange Framework (IEF) Policy Vocabulary is to enhance the ability of organizations to describe the rules governing the sharing and protection of information. The IEF Information Exchange Policy Vocabulary RFP seeks to provide a robust vocabulary for expressing the policies, rules and constraints governing the release and exchange of information between information systems participating in an information sharing agreement. This specification will provide a formal vocabulary that is able to express the nouns and verbs used to construct statements that can be encoded as a set of human and machine readable policies and then enforced by software applications and services. This RFP solicits proposals for a formal vocabulary that can be expressed in one or more software enforceable policy languages. Submissions should specify how these policies are sufficient to permit rigorous modeling, validation and enforcement.

Information Exchange Framework Information Exchange Policy-based Packaging Services (IEPPS) RFP (document mars/2011-12-12)
The Information Exchange Framework (IEF) Policy-based Packaging Service (PS) will provide organizations an automated way to apply user defined policies that govern the sharing and protection of information. Information exchange policies will be described in accordance with the Information Exchange Policy Vocabulary (IEPV) (Request for Proposal (RFP): mars/2011-03-15). This RFP solicits proposals for a service specification describing the application-visible interface(s) and behavior of the packaging services. This includes services for data aggregation and marshalling; data guarding and filtering; syntactic and semantic validation; tag and label processing; data transformation; release control; and routing. The proposals should describe how the service interacts with the middleware and communication networks. In addition, it should address issues related to security, privacy, Quality of Service (QoS), logging, and auditing.

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

MDA Tool Component RFP (document ad/2006-06-09)
This Request for Proposal (RFP) is one of a series of RFPs related to the development of the MDA Tool Component (MDATC) specification. The objective of this RFP is to provide a standard specification to define and package the material used to customize a tooling environment, in order to apply MDA to a specific domain or context. This packaging unit is called "MDA Tool Component". In support of this objective, the RFP solicits proposals for: · a specification of the definition and packaging aspects of MDA Tool Components

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.

Management of Regulation and Compliance (MRC) (document bmi/2009-09-24)
Most businesses have to comply with regulation. This requires more than simply applying regulations "as they come". People in those business have to decide what their enterprises need to do in order to comply. They need software tools to support them in: 1. Interpreting what regulations mean to their enterprise 2. Assessing the impact of the regulations on the enterprise’s policies and operations 3. Deciding how to react (and documenting why), and distributing policies and guidance for compliance 4. Demonstrating that compliance policies are being followed across the enterprise and that they are effective. The objective of this RFP is a specification from which such tools could be developed. The RFP solicits proposals for the following: • A metamodel of interpreted regulation and compliance actions, with a supporting vocabulary. A specification for interchange of model instances, i.e. for interpretations and compliance actions for instances of regulation

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.

Naval Meteorological & Oceanographic System Interface RFP (document c4i/2008-12-02)
This RFP solicits proposals for the specification of a Generic Meteorological Interface to all the Ship users. It aims to reduce the complexity of the interface between the Meteorological & Oceanographic System and the other units of the Combat System and to define the data interfaces between them.

Naval Navigation System Interface RFP (document c4i/2007-12-01)
This RFP solicits for a Naval Navigation System Interface (NNSI) that will address the quality-of-service aspects relevant for the Naval CMS domain; the NNSI will primarily provide the distribution of ship navigation and stabilization data suitable for use in a Naval CMS.

Open Architecture Radar Interface Standard (OARIS) RFP (document c4i/2012-03-06)
This RFP solicits proposals for the following: o A standard for the interface between the Combat Management System (CMS) and one or more Radars within a modular naval Combat System. o A standard that enables reuse regarding further interfaces to different categories of Combat System Equipment

Precise Semantics of UML Composite Structures RFP (document ad/2011-12-07)
The objective of this RFP is to solicit specifications containing more precise semantics for UML composite structures and their extensions (e.g., profiles) to enable execution, model checking, and reduce ambiguities in UML 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 semantics for all the metaclasses supporting the ability of classifiers to have both an internal structure (comprising a network of linked parts) and an external structure (consisting of one or more ports). The specification should cover both structural semantics (e.g. the runtime manifestations of connectors, ports, and parts) and behavioral semantics (e.g. life-cycles of composite objects and their constituents, the nature and characteristics of flows through ports and connectors). Proposals shall build on the precise semantics of fUML, which specifies the execution semantics of a computationally complete and compact subset of UML 2 to support execution of activities.

RIA Dynamic Component Model RFP (document mars/2013-03-28)
The Rich Internet Application (RIA) domain provides client-side functionalities like visualization, user interactions, and device control for internet-based distributed applications. Usually, a RIA Application is rendered with a RIA runtime engine (referred to as a RIA Platform), which behaves like a typical application or native component. In an Enterprise business application, master data like product codes or basic data like order information are retrieved and/or referenced frequently by all subsequent applications. To increase the reusability of applications, front-end RIA Applications should be componentized as server-side/back-end distributed business components such as EJB, OSGi, and CCM. Moreover, this RIA componentization should be done under no-compilation (XML and JavaScript) and runtime deployment environment (no pre-installation, e.g., HTML) conditions so that a RIA Application can be treated as a RIA Component by another RIA application. This RFP solicits proposals for the following: o A standard RIA Dynamic Component Model (RDCM) which defines the services necessary to dynamically construct a RIA Application using RIA Components specific to a single, homogenous RIA Platform. The goal is a specification defining a format for declaring interfaces for exposing properties and methods within the RIA Application, as well as, how to use interfaces at development time and/or runtime in a RIA Platform. Submissions developed in response to this RFP should address the following: o A Vocabulary defining a RIA Component interface. This vocabulary defines the terminology used in the RIA development community including event information, property, method, and event handler. o A Platform Independent Model (PIM) of the component model which maps the preceding vocabulary including: o Mechanisms for the dynamic deployment of RIA Components, consisting of interface descriptions (IDL) and implementations (RIA Application source code). o Mechanisms for dynamically instantiating implementations and dynamically binding interfaces while executing a RIA Application. o Mechanisms for calling interfaces and exchanging data including dynamically declared custom data types. o Platform Specific Models (PSM) implementing the preceding PIM for specific deployment platforms, including JavaScript. The RDCM RFP does not apply to: o Presentation issues (layout and look & feel) of a RIA Application. o Specifications addressing bi-dimensional and tri-dimensional computer based graphics. o Instantiations of RIA runtime engines based on an OS application or native component. o Data exchanged between RIA runtime engines. o Server-side/back-end web applications.

Records Management Services Version 2 RFP (document gov/2009-12-05)
The OMG adopted the Records Management Services specification (Beta-1: http://www.omg.org/spec/RMS/1.0/Beta1/) in June 2009. Provision for specifying context dependent Attribute Profiles was established, but specific instances were not. Additionally, no fine grained compliance points were defined. Compliant implementations are constrained to implement the specification in toto. This RFP solicits proposals for the following: · The provision of one or more Attribute Profiles minimally supporting DoD 5015.02 compliant Records Management Environments. · The addition of compliance points to subset service operations and profile attribution as it is affected by the subsetting. This will allow RMS to be provisioned on a scale that suits the business needs of diverse organizations.

Remote Procedure Calls (RPC) over Data Distribution Service (DDS) RFP (document mars/2012-06-29)
The Data Distribution Service for Real-Time Systems (DDS) is an Object Management Group (OMG) specification for real-time and data-centric publish/subscribe. The DDS standard has been widely adopted and applied across application domains including Aerospace and Defense, Transportation, SCADA, and Financial. In many of these domains, DDS is often the only middleware technology used to build complex and large-scale distributed systems. In these systems, DDS is used to represent and share distributed state, to distribute event, and to execute commands. Although DDS provides first class support for distributed state and event, it makes it a bit cumbersome to express commands, or put it in another way, it does not provide first class support for synchronous two way interactions, thus leading users to implement their own ad hoc solution over DDS. This RFP calls for a systematic solution to this problem by means of a Remote Procedure Calls (RPC) extension to the DDS specification. This extension will allow commands to be naturally represented as remote method invocations.

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.

Value Delivery Metamodel (VDM) RFP (document bmi/2009-03-09)
This RFP solicits proposals for a metamodel specification for modeling customer value delivery, based on the concept of a value chain. A value chain, as originally defined by Porter (see reference 1, Section 6.4.2, page 33), “disaggregates a firm into its strategically relevant activities in order to understand the behavior of costs and the existing and potential sources of differentiation”. According to Porter, a Value Chain is composed of a set of Value Activities, “the physical and technologically distinct activities that a firm performs”, and Margin, “the difference between total value and the collective cost of performing the value activities” (see reference 1). A primary value chain represents a chain of activities that contribute directly to delivery of end-customer value. Other value chains exist within the enterprise (support services) to produce value for internal customers. There are typically are multiple value chains for different products or lines of business. Consequently, each value chain is a use-case of enterprise capabilities required to produce a desired customer value. A value delivery model will include multiple value chains that may include participants in an extended enterprise and represent the sharing of capabilities across multiple value chains. The Value Delivery Metamodel shall • Provide support for high level abstractions that meet the needs of top management for strategic planning, including aggregation of cost, quality and timeliness measures for product or line of business value chains. • Provide support for analysis of value chain activities to understand the detailed costs, quality and timeliness in the context of customer value delivery and to associate market differentiators with the capabilities that achieve those differentiators. • Establish the linkages between value delivery activities and organizations unit (s) identifying the various roles those organizations play in relationship to those activities.. • Support identification of business capabilities that may be consolidated as shared services or engaged as alternative sources. • Enable exchange of value delivery models between different modeling tools. • Establish a linkage between comparative differentiators and appropriate elements within the Business Motivation Model (BMM) • Establish a linkage between competitive strategies and appropriate elements within the Business Motivation Model Value chain modeling is essential for understanding and managing a SOA because services are engaged in multiple business contexts, and their impact on these different contexts must be considered in the design of the service and its performance characteristics. The availability of a standard value delivery metamodel will advance the state of the art in business modeling, supporting more effective planning and analysis of enterprise operations. A standard model will enable tool vendors to develop more sophisticated modeling and analysis techniques and will enable users to migrate to the tools that best address their needs. This RFP does not require a normative notation or form of expression for value delivery models since the specifics of value delivery views may evolve, and product differentiation will promote the development of innovative views in different modeling tools.

Web-enabled DDS RFP (document mars/2009-09-19)
The Data Distribution Service for Real-Time Systems (DDS) is the Object Management Group (OMG) standard for data-centric publish subscribe. The objective of this RFP is to facilitate the use of DDS from web-client applications. The OMG DDS standard has experienced a record-breaking adoption within the Aerospace and Defense domains, and is swiftly expanding into new domains such as Transportation, Financial Services, and SCADA. To sustain and further propel its adoption, it is essential to expand the kinds of applications and technologies that can easily access DDS data and benefit from DDS’s performance and quality of service. An important class of applications that would greatly benefit from a simple, standards-based access to DDS are web-based applications. Both client-side web applications, such as those programmed using technologies like JavaScript or AJAX, as well as server-side web applications programmed using scripting languages like PHP, Perl, Ruby, and Python. The OMG DDS standard defines local interfaces that can be used by an application to access a virtual “Global Data Space” where applications can publish and subscribe data. These interfaces are realized in concrete programming languages such as C/C++, Java, .NET, or ADA from their IDL description. An application using the DDS API language bindings will need to load a programming-language specific library that implements these local interfaces and uses the DDS Interoperability Wire Protocol to communicate with the “Global Data Space” implemented collaboratively with other DDS applications on the network. The need to load a programming-language specific implementation library limits the potential use of DDS to applications written in one of the supported programming languages. For example if there are no DDS implementations that support scripting languages like Perl, PHP, Ruby, or Python, then a program written in those languages cannot directly use DDS. Furthermore, there are deployment scenarios where it is impossible or impractical to load a library in the client computer. All the client can do is access a web page and perhaps load into the browser code that it will execute within the environment of the browser (e.g. JavaScript or Flash). These scenarios are currently precluded from being able to consume or produce data in the DDS Global Data Space. To support these use cases, this RFP solicits proposals for exposing DDS via a variety of web-friendly protocols such that client applications do not need to load any libraries in order to produce and consume data in the DDS Global Data Space. Furthermore, web applications, including applications that execute inside a web browser, will be able to use DDS to Publish and Subscribe information and thereby benefit from the Performance, Scalability, and Quality of Service (QoS) available in the DDS Implementations.

Current Specification Revision Processes (available to members only:

2nd Dynamic Deployment and Configuration for RTC (DDC4RTC) 1.0 FTF

2nd NIEM-UML FTF

2nd OCL 2.4 RTF

ADM KDM 1.4 RTF

AMI4CCM 1.1 (AMICCM) RTF

Abstract Syntax Tree Metamodel 1.0 (ASTM) RTF

Action Language for fUML 1.1 (ALF) RTF

Automated Function Point 1.0 FTF

BMM 1.2 RTF

BPMN 2.1 RTF

Canonical XMI FTF 2

Case Management Model and Notation 1.0 (CMMN 1.0) FTF

Common Terminology Services 2 (CTS2) 1.1 Revision Task Force

Common Terminology Services 2 (CTS2) 1.2 Revision Task Force

Common Variability Language 1.0 (CVL) FTF

DDS-PSM-Cxx v1.1 RTF

DDS-PSM-Java v1.1 RTF

DDS-XTYPES RTF

Data Distribution Interoperability 2.2 RTF

DateTime Vocabulary (DTV) 1.1 RTF

Diagram Definition 1.1 RTF

EXPRESS Metamodel 1.1 RTF

Essence 1.0 FTF

GEMS 1.3 RTF

IDL 3.5 FTF

IDL to C++11 1.1 RTF

IDL to C++11 1.2 RTF

IFML 1.0 FTF

MARTE 1.2 RTF

MDMI 1.1 RTF

MOF 2 Core 2.5 RTF

OARIS 1.0 FTF

Ontology Definition Metamodel (ODM) 1.1 RTF

PRR 1.1 RTF

QVT RTF 1.2

Records Management Services V1.1 (RMS) RTF

Requirements Interchange Format V1.2 (ReqIF) RTF

Robotic Interaction Service Framework 1.1 RTF

Ruby CORBA Language Mapping 1.3 (RCLM) RTF

SACM 1.1 RTF

SBVR 1.2 RTF

SBVR 1.3 RTF

SBVR RTF

Second Property and Casualty Information Model 1.0 FTF

Services Directory 1.0 (ServD) FTF

SoaML 1.1 RTF

Structured Metrics Metamodel 1.1 RTF

SysML 1.4 RTF

TelcoML 1.1 RTF

TestIF 1.0 FTF

UML Profile for BPMN Processes 1.0 (BPMNProfile) FTF

UPDM 2.2 RTF

Unified Modeling Language 2.5 (UML) FTF

VSIPL_1.5_and VSIPL++_1.3_RTF

XMI 2.5 RTF

XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF

fUML 1.2 RTF

Copyright © 1997-2013 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact webmaster@omg.org.
For TECHNICAL questions, please contact webtech@omg.org. This site is best viewed with Mozilla Firefox or Internet
Explorer versions 6.0 or later or any browser capable of viewing JavaScript and CSS 2.0. The site is using DHTML JavaScript Menu By Milonic.com.