140 Kendrick Street,
Building A Suite 300
Needham, MA 02494, U.S.A.

Ph:+1-781-444 0404
Fax: +1-781-444 0320
Email: info@omg.org

Current OMG Technology Adoption Processes Under Way
Last updated: Thursday, 28-Aug-2008 14:30:54 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 Comments:

Reference Metamodel for the EXPRESS Information Modeling Language RFC (document mantis/2008-02-05)

UPDATED Draft EXPRESS Metamodel RFC -- cmof XMI (document mantis/2008-02-04)

Pending Requests for Information:

Automated Software Testing RFI (document c4i/2008-06-09)
The US Navy is interested in leveraging automated software testing as a means to reduce the cost of testing software by: · Reducing the time required to test and certify systems · Enable faster delivery of new capabilities to the fleet · Improve the quality of the software delivered This effort is being conducted in the context of the US Navy’s Open Architecture (OA) principles, which emphasize the use of widely-adopted industry standards and component-based technologies. Although OA principles are usually applied to software design and development, they can also facilitate improvements in other areas of the software life-cycle. Standards have the potential to significantly improve the Navy’s test processes, including the ability to leverage automated software testing. The purpose of this RFI is to solicit ideas, discussion, comments, recommendations, product information, user needs, and user experiences regarding the use of automated software testing.

Business Security and Authorization Policy Modeling RFI (document bmi/2008-03-13)
Data Tagging and Labeling for Security and Privacy RFI (document omg/2007-09-04)
This Request for Information (RFI) solicits information about requirements, standards, products and impact on current systems related to the development and integration of Labeling/Tagging strategies for information storage, dissemination, and use within complex, distributed, multi-level and multi-tiered systems. The OMG will use this information to initiate the technology adoption process for OMG compliant data models, interfaces, and process standards.

Dynamic Business Activity Models RFI (document bmi/2008-03-03)

Information Transformation Services RFI (document mars/2007-09-15)
The intent of an OMG Request for Information (RFI) is to gather information for the purpose of guiding a subgroup in its efforts to provide solutions to industry problems. The RFI process is used by a subgroup to canvass a targeted industry segment for one or more of the following purposes: · Acquiring general or specific information about industry requirements. · Soliciting assistance in identifying potential technology sources. · Soliciting input to validate a subgroup’s roadmap. Generally speaking, the RFI process determines which Request For Proposals (RFPs) will be issued (and, based on negative feedback, which won't) or influences the way a particular RFP is constructed.

Ontology and Vocabulary Management Information RFI (document ontology/2008-03-02)
The objective of this RFI is to explore available models and technologies for managing these management aspects of ontologies and vocabularies, with the intent of developing “standards of practice” and associated technical specifications for the purpose. The immediate objective of this RFI is to assist the OMG in determining · whether it is appropriate for OMG to develop standards at this time to address provenance, effectivity and evolution of ontology elements, what the scope of such a standards activity (or activities) should be, and whether OMG should design and deploy a repository for knowledge models

Transliteration and Transcription Services RFI (document mars/2007-09-14)
In today's world, many transliteration and transcription solutions exist and are in use by agencies such as the National Geospatial-Intelligence Agency to perform a number of functions including place name transliteration. A standardized architecture that enables the management and configuration of these products, e.g., to respond to updates in transliteration definitions by official language bodies, would enhance user choice leading to increased market size for vendors. The intent of this RFI is to gather information about Transliteration and Transcription Services. Transliteration systems could benefit greatly if they used a standard method for defining rules, interfaces and services so that they can be interoperable and the rules can be used across various transliteration/transformation engines. Creating the rules may not be part of this effort, but could be regarded as an integral part of any transliteration service. One possible solution is to find a way to standardize the definition of these rules. The information sought by this RFI will be used to establish a common rule format and common service interfaces so that we can move towards a goal of interoperable transliteration and transcription systems.

UML Profile for XBRL Global Ledger (GL) Framework RFI (document finance/2008-05-01)
This RFI is seeking participants with the skills and experience described below. Respondents are asked to address areas in which they have expertise and/or interest. A Respondent can respond to all or some of the questions. Respondents may also contribute information and perspectives not explicitly asked for if they feel the information provides useful guidance to support the RFI objectives. We are looking for: · Expressions of interest in a UML Profile for XBRL GL · Expressions of interest in specific UML models of uses of XBRL GL · Sample UML models that illustrate how the Respondent envisions using UML to model XBRL GL – based information · Examples illustrating knowledge of XBRL, XBRL GL and/or UML · Experience in similar efforts, be it in the financial industry or any other industry, to standardize information related to the semantics and syntax of information. We do not expect most Respondents will cover all of these areas, but we do hope to receive feedback from some Respondents in each area. Limited but insightful responses are welcome, as are more comprehensive responses. Sources of experience may include: · Projects by end users (from industry or government) that have attempted to standardize ERP integration, whether or not using MDA. · Explorations by academic or other research groups · Activities by vendors to build relevant tools · Initiatives by industry associations and standards groups that have already been formed or are being planned.

Value Delivery Modeling RFI (document bmi/2008-06-03)
There is a diverse community of experts and users of business analysis and modeling approaches that incorporate the concepts of value chain, value stream or value network. There are existing and emerging software tools that support such approaches. This RFI solicits input on how the OMG might provide value to the business users and tool builders by working with them to develop modeling standards for such software tools. For the purposes of this RFI, we use the phrase value delivery to refer generally to current notions of value chain, value stream, value network, supply chain, service chain and other related practices. In general, value delivery focuses on the contribution of enterprise activities to the delivery of value to a customer. This RFI seeks information on current practices, tools, techniques and standards that apply the concept of value delivery.

Pending Requests for Proposals:

Abstract Syntax Tree Metamodel ASTM (ASTM) final RFP (document admtf/2005-02-02)
The Abstract Syntax Tree Metamodel (ASTM) defines a specification for modeling elements to express abstract syntax trees (AST) representing the structure of application code. A resulting AST will be sharable among multiple tools from different vendors to support analysis, visualization, refactoring, target, mapping and transformation operations upon the represented application artifacts accurately and with high levels of automation. The Knowledge Discovery Metamodel (KDM) RFP, currently in process, provides a comprehensive high-level view of the application behavior, structure and data, but does not represent application models below the procedural level. The ASTM models constructs within programming languages, while the KDM models structural, behavioral and data information about application portfolios. ASTM is one of the sources of information for the KDM. The ASTM is expected to complement the KDM as an element of the ADM Roadmap (see Appendix B) to express fully detailed models of application artifacts.

Analysis Package RFP (document admtf/2007-12-10)
• The OMG Architecture-Driven Modernization Task Force requests proposals for metamodels which facilitate the interoperability of tools used to perform analysis of existing software systems.

Business Process Model and Notation (BPMN) 2.0 RFP (document bmi/2007-06-05)
This Request for Proposals solicits submissions that reconcile the Business Process Modeling Notation (BPMN) and the Business Process Definition Metamodel (BPDM) to specify a single language with metamodel, graphical notation and interchange format. The specification developed in response to this RFP is expected to achieve the following: o A single specification, entitled Business Process Model and Notation (BPMN 2.0), that defines the notation, metamodel and interchange format, with a modified name that preserves the “BPMN” brand. o Extension of BPMN notation to address BPDM concepts. o Changes that are required to reconcile BPMN and BPDM to a single, consistent language. o The ability to exchange business process models and their diagram layouts among process modeling tools preserving semantic integrity. o Enhancements in BPMN’s ability to: § Model orchestrations and choreographies as stand-alone or integrated models. § Support the display and interchange of different perspectives on a model that allow a user to focus on specific concerns. o Disposition of outstanding issues deferred by the respective finalization task forces for BPMN 1.1 and BPDM 1.0.

DDS for (Light-Weight) CORBA Component Model RFP (document mars/2006-02-17)
Today’s applications are being developed increasingly using component based development frameworks, such as the CORBA Component Model (CCM), Lightweight CCM (LwCCM), .NET and Enterprise Java Beans (EJB). Distributed component models greatly simplify distributed application development. In current implementations of CCM, component ports are connected across a network using CORBA. With the introduction of the Data Distribution Service (DDS) standard, data critical applications may benefit from DDS-based connections between components. This RFP solicits proposals for the following: • Extend the current LwCCM specification to support component ports which map to DDS and which enable and expose DDS functionality to the component developer.

Date-Time Foundation Vocabulary RFP (document bmi/2008-03-02)
The goal of this Request for Proposal is the development of a consistent set of Semantics of Business Vocabulary and Rules (SBVR) vocabularies, Ontology Definition Metamodel (ODM) domain theories, and Unified Modeling Language (UML) reusable models for concepts about date and time. The distinguishing characteristics of this RFP are: (a) provision of an SBVR business vocabulary for date and time concepts; and (b) the standardization of the same concepts in these multiple technologies. Specifically, this RFP solicits proposals for the following: An SBVR business vocabulary for date & time. An equivalent model in one of the ODM technologies, such as OWL. An equivalent UML class model.

Decision Support Service RFP (document health/2007-03-01)
A decision support service (DSS) uses patient data to draw conclusions regarding patients. A DSS can be conceptually understood as the guardian of one or more modules of medical knowledge, wherein each DSS knowledge module is capable of utilizing coded patient data to arrive at machine-interpretable conclusions regarding the patient under evaluation. A DSS can be used by clinical software applications to provide patient-specific care recommendations to physicians, patients, and other healthcare stakeholders. To facilitate interoperable use of DSSs, it is important that the capabilities and interfaces of DSSs are standardized. The functional requirements and conformance criteria for DSSs have been standardized in the Health Level 7 [HL7] DSS Service Functional Model (SFM) specification.[DSS-SFM] The HL7 DSS SFM achieved Draft Standard for Trial Use (DSTU) status in the September 2006 HL7 ballot. This RFP solicits proposals for the following: -A DSS specification that aligns with the HL7 DSS SFM.

Diagram Definition RFP (document ad/2007-09-02)
This RFP requests a specification with the goal of enabling the definition and exchange of diagram syntax definitions and their bindings to MOF-based abstract syntaxes. The definitions will be capable of interpretation by a class of generic modeling tool resulting in diagram editors for MOF-based metamodels. The combination of the diagram definition specification and the MOF standard thus provides a complete capability to define graphical Domain Specific Languages (DSLs). This specification further provides the opportunity to more precisely and formally define the diagram types in other MOF-based specifications such as UML and BPMN.

Entity Identification Service RFP (document health/2006-12-01)
The following text is taken from the balloted Health Level 7 (HL7) Entity Identification Service (EIS) Service Functional Model (SFM) Section 1.1. A number of references and extracts from this document are included in this RFP. It is strongly recommended that submitters read and digest the SFM as part of producing their responses to this RFP. HL7 is making this document freely available at http://www.hl7.org/dstucomments/index.cfm EIS Overview The Entity Identification Service (EIS) provides a set of service interfaces to uniquely identify various kinds of entities (e.g. people: patients, providers etc., devices) within disparate systems within a single enterprise and/or across a set of collaborating enterprises. Context – HSSP Overview The Healthcare Services Specification Project (HSSP) [http://hssp.wikispaces.com] is a joint endeavor between Health Level Seven (HL7) [http://www.hl7.org] and the Object Management Group (OMG) [http://www.omg.org]. The HSSP was chartered at the January 2005 HL7 meeting under the Electronic Health Records Technical Committee, and the project was subsequently validated by the Board of Directors of both organizations. The HSSP has several objectives. These objectives include the following: - To stimulate the adoption and use of standardized “plug-and-play” services by healthcare software product vendors - To facilitate the development of a set of implementable interface standards supporting agreed-upon services specifications to form the basis for provider purchasing and procurement decisions. - To complement and not conflict with existing HL7 work products and activities, leveraging content and lessons learned from elsewhere within the organization. Within the process, HL7 has primary responsibility for (1) identifying and prioritizing services as candidates for standardization; (2) specifying the functional requirements and conformance criteria for these services in the form of Service Functional Model (SFM) specifications such as this document; and (3) adopting these SFMs as balloted HL7 standards. These activities are coordinated by the HL7 Services Oriented Architecture SIG in collaboration with other HL7 committees, which currently include the Vocabulary Technical Committee (TC) and the Clinical Decision Support TC. Based on the HL7 SFMs, OMG will develop “Requests for Proposals” (RFPs) that are the basis of the OMG standardization process. This process allows vendors and other submitters (known as “RFP Submitters”) to propose solutions that satisfy the mandatory and optional requirements expressed in the RFP while leaving design flexibility to the submitters and implementation flexibility to the users of the standard. HL7 members will be involved in the RFP creation and evaluation process. It is important to note that the HL7 SFMs will focus on specifying the functional requirements of a service, while OMG specifications will focus on specifying the technical interface requirements of a service. In many cases, SFMs will also describe an overall coherent set of functional capabilities. These capabilities may be specialized or subdivided from both functional and informational (semantic) perspectives to provide specific “profiles” that may be used as the basis for the OMG RFPs and/or implemented.

Extensible and Dynamic Topic Types for DDS RFP (document mars/2008-06-22)
The Data Distribution Service for Real-Time Systems (DDS) is the Object Management Group (OMG) standard for data-centric publish subscribe. This standard has experienced a very successful adoption within the Aerospace and Defense domain and is swiftly expanding to new domains, such as, Transportation, Financial Services, and SCADA. To sustain and further propel its adoption it is essential to extend the DDS standard to effectively support new use cases. Specifically, the DDS standard was designed around the assumption that the types associated with topics were known at compile time. From this assumption derive a series of choices that currently make it hard to deal with (1) dynamically defined topic types without either introducing additional complexity or losing some data centric feature, e.g., content awareness, and (2) Topic data types extensibility, e.g., the ability of different parts of a system to rely on different versions of a data type for a specific topic. To address these limitations, this RFP will extend the DDS standard with an extensible Topic type system, dynamic DDS APIs, and extended data encapsulation formats.

GIOP Compression RFP (document mars/2007-06-10)
Many CORBA applications are deployed in environments with restricted bandwidth. Examples of these environments include aviation and retail banking, where applications may operate over a wide area network. Although GIOP is performant when compared to other protocols, some further optimization is possible, by minimizing the amount of information passed across the network through compression. This RFP solicits proposals for an extension to the OMG GIOP protocol to provide on-the-wire compression.

High-Assurance ORB RFP (document realtime/2004-02-14)
High Assurance embedded systems present hurdles that inhibit the use of a CORBA Object Request Broker (ORB). This RFP seeks to create a standard for ORB implementations that can be used for application development with certifiable Real-Time Operating Systems (RTOS). There are currently High Assurance certifiable RTOSs currently available as reusable software components for safety critical systems and others that are providing certification support. Additional RFPs are expected to be issued to better address the modeling and certification needs of applications using certifiable RTOSs with an ORB. This RFP solicits proposals for the following: Real-Time (static scheduling) and/or Minimum CORBA ORB functionality subsetted for use with certifiable Real-Time Operating Systems Safety Critical Language Profile for application use with CORBA CORBA Language mapping using the Safety Critical Language Profile

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

Information Models for Property and Casualty Insurance RFP (document finance/2007-06-07)
This RFP solicits proposals for ‘Information Models’ to address the data management needs of the P&C Insurance Community. It is expected that submitters of these models will utilize OMG’s Model Driven Architecture principles and related standards (http://www.omg.org/mda/). Use of existing P&C industry standards (ACORD for example) as a source of the proposed P&C Business Glossary is encouraged. Submitters of this RFP are also encouraged to review and reuse (as applicable) the ongoing work by OMG’s Finance Domain Task Force (FDTF http://fdtf.omg.org) covering Payment interoperability, security and identity management of financial transactions as well as interchange of P&C metadata. This work assumes further significance as P&C carriers look to utilize the information models towards development of P&C ‘Business Services’ to better understand and automate their business processes and functions.

Lightweight Fault Tolerance for Distributed Real-Time Systems RFP (document realtime/2006-06-06)
This RFP solicits proposals for a platform independent model for “FT-enabled” middleware extensions to support fault tolerant distributed real-time systems. This RFP also solicits a platform specific mapping (PSM) to CORBA, and Real-Time CORBA.. In contrast with the existing Fault Tolerant CORBA specification, the requested proposals should: · Define the responsibilities, interfaces, services and interactions between the FT-enabled middleware, the external fault management infrastructure and the applications, in order to enable the integration of the FT-enabled middleware into complex distributed systems with a variety of specialized fault tolerant infrastructure capabilities. · Defer to the external fault management infrastructure in order to provide services such as Fault Analysis, Fault Containment and Fault Recovery management. The FT-enabled middleware should focus on the services that provide connection management, transparent client failover between endpoints, plus detection and reporting of normal middleware faults. · Define the FT–enabled middleware interactions that support a variety of approaches to the coordination of application level state synchronization during failover. · Defer to the external fault management infrastructure and applications in order to manage state consistency. · Minimize the complexity and resource utilization of the FT-enabled middleware without putting excessive burden on the application. · Defer to the application when faults cannot be transparently masked by the FT-enabled middleware within real-time bounds.

MDA Models for Electronic Records Management Services RFP (document gov/2006-06-11)
In performing their missions, Government agencies produce records that document and support agency processes, activities, and decisions. Agencies must manage these records from creation through final disposition as integral assets to Government operations. The failure to manage records effectively exposes agencies to considerable risks related to their legal and regulatory responsibilities, continuity of business operations, and accountability to citizens for their actions. This RFP requests proposals for models for software services to support management activities for electronic records. The scope of the services to be modeled extends from record receipt, identification and capture to record disposition. Following the OMG MDA framework, models are requested that describe the business activities the services are to support (CIM), specify the logical service interfaces and functionality (PIM), and define at least one technology-specific implementation of the services interfaces (PSM). Further, while this RFP focuses on supporting records management for Government, it is acknowledged that there are an increasing number of requirements for records keeping in industry. This means that similar considerations can apply to industry and that the records management services requested by this RFP could be applicable to industry as well, though this is not an explicit mandatory requirement in this RFP.

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 Support for Semantic Structures RFP (document ad/2006-06-08)
Submitters are requested to propose incremental changes to several existing specifications in order to make MOF better capable of supporting richer and evolving models. These should be factored into new compliance levels – referred to as SMOF for the purpose of this RFP. The principle change is to allow MOF instances to add and remove metaclasses. The main specifications to be updated are: · MOF2 Core · MOF2 XMI · MOF2 IDL · UML2 Infrastructure (optionally)

Native C++ Language DDS PSM RFP (document mars/2008-03-04)
The Data Distribution Service for Real-time Systems specification consists of a UML PIM and single IDL PSM. A user of the DDS service uses a programming language API (e.g. C++ , Java) which is derived from the IDL PSM by applying the IDL to language mappings. The definition of a single IDL PSM precludes the use of many native programming language constructs, such as generics, operator overloading, etc. The result is a sub-optimal API that does not conform to the stylistic idioms of the target language, introducing a barrier to the adoption and use of the specification. This RFP solicits proposals for a Native C++ Language DDS PSM, specifically to ISO Standard C++, which would use and conform with the standard data-types and programming idioms of the language.

Naval Meteorological & Oceanographic System Interface RFP (document c4i/2008-03-05)
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.

Organization Structure Metamodel (OSM) RFP (document bei/2004-06-05)
The objective of this RFP is to solicit proposals for a metamodel to be used for specification of an organization structure and at least one mapping to a production directory schema. An organization structure metamodel consists of modeling elements used to represent organizational entities, their attributes, the relationships between them and the people assigned to them. This includes information about the organizational units that make up an enterprise and the structure and formal relationships by which they interact. This metamodel shall support the specification, analysis and modification of the organization structure of an enterprise. The concepts and associated information must be defined in business terms and must be sufficient to support a variety of organization types. The metamodel shall also support specification of future-effective organizational changes. The specification shall include a mapping of the metamodel to a runtime directory schema to provide consistent data structures for use by production applications while addressing the schema-characteristics needed for runtime performance.

PIM and PSM for Digital Intermediate Frequency Interface RFP (document sbc/2004-08-15)
This RFP solicits proposals for the following: - PIM for control interfaces of tuners and exciters in a high bandwidth digital streaming system - Data descriptors for the messages passed across the digital Intermediate Frequency (IF) platform - A UML 2.0 compliant profile that allows the modeling of system aspects, topology and data flow

PIM and PSM for Smart Antenna RFP (document sbc/2006-12-10)
A Smart antenna is an antenna array system that is aided by a processing system that processes the signals received by the array or transmitted by the array using suitable array algorithms to improve wireless system performance. This RFP establishes the requirements for developing the smart antenna interface specification to be implemented in OMG’s software radio architecture, and solicits proposals for said specification. The interfaces enable the Software Radio to manage and utilize the smart antenna subsystem.

Platform Independent and Platform Specific Model for Mobile Ad-hoc Networking RFP (document sbc/2007-12-04)
A Mobile Ad Hoc Network (MANET) is an extension to existing wireless networking technology to achievediscovery and multi-hop routing of packets across a wireless network. This RFP solicits a Platform-Independent Model (PIM) defining the necessary extensions to an OSI or TCP/IP network stack to enable Mobile Ad-hoc Networking (MANET) capabilities. The proposed PIM should be structured in a way so that it could act as a reference model for future MANET-related PIMs. The correctness and implementability of this PIM should be demonstrated through a Platform-Specific Model for MANET extensions to an existing networking stack.

Reference Models of Business Processes for Financial Services RFP (document finance/2007-03-05)
Modeling the financial processes involved in account opening and funds transfer in a formal way is a first step in a broad industry effort to make business processes across the financial services industry more efficient and secure. Reference models for these processes are intended to elucidate the security issues across inter-enterprise financial services networks, and to provide an architectural framework for further elaboration of financial processes that create, carry or consume sensitive data. The financial services industry and their suppliers will use these reference models to collaboratively identify opportunities to improve security policy and controls. In particular, it is expected that redundancies and inefficiencies in existing processes, often the cause of security issues, will be addressed. This RFP, issued by the Finance Domain Task Force (FDTF) of the OMG, therefore solicits proposals for the following: -the definition of standard reference models for account opening and funds transfer processes; and -the definition of an architectural framework based on the reference models, intended to identify opportunities for improved security and privacy mechanisms, protocols, and policies.

Retrieve, Locate, and Update Service (RLUS) RFP (document health/2006-12-02)
The following text is taken from the balloted Health Level 7 (HL7) Retrieve, Locate, Update Service (RLUS) Service Functional Model (SFM) Section 2.1. A number of references and extracts from this document are included in this RFP. It is strongly recommended that submitters read and digest the SFM as part of producing their responses to this RFP. RLUS Overview The Retrieve, Locate, and Update Service (RLUS) provides a set of interfaces through which information systems can access and manage information. RLUS allows health data to be located, accessed and updated regardless of underlying data structures, security concerns, or delivery mechanisms. RLUS explicitly occupies the service space within an information processing environment. It is independent of but compatible with underlying structures, including local security implementations, data models, or delivery mechanisms. By separating and exposing those aspects of resources that facilitate inter-organization work flows in a service layer, this specification abstracts the problem of interoperability away from underlying systems. It is this abstraction and reconfiguration that allows interoperability and system durability independent of burdensome technology integration.

Robotic Localization Service RFP (document robotics/2007-06-25)
This RFP solicits proposals for a Platform Independent Model (PIM) and at least one CORBA Platform Specific Model (PSM) or C++ PSM of Localization Service that specify • common interfaces for Localization Service to transfer data and commands • a set of common information to represent location In the context of this RFP the word “localization” means “to find the location of some physical entities through analysis of sensor data”, consistent with the common use of this term in Robotics.

SOPES IEDM RFP (document c4i/2004-06-27)
The objective of the Shared Operational Picture Exchange Services (SOPES) initiative is to enhance the ability of first responders, government, military and civilian organizations to develop and sustain a complete, timely and accurate awareness of the operational situation (Common Operational Picture). SOPES will enable users to selectively share information across and between participating organizations; providing an improved visibility of the operational environment affecting decisions and resource commitments. The intent is to provide the decision maker with relevant information in near real time and to support the challenge of tactical communication links. SOPES will also protect sensitive, private, confidential or legally significant information from general dissemination. SOPES will enable all participants within a coalition to have the same understanding of the operational scenario and environment within their area of interest. This RFP solicits proposals for the following: -A Platform Independent Model (PIM) capable of containing and representing data/information exchanged between and across boundaries within any multi-faceted enterprise in support of the preparation and management of civil and military Crisis Response Operations (CRO). -A specification describing the requirements, structure, components, relationships and conceptual understanding of the SOPES Information Exchange Data Model (IEDM) sufficiently detailed to enable the provision of: -A consistent and common understanding of exchanged data/information. -Common operational views of the data that can be developed independently. -A conceptual/logical schema of data for the design of systemÂ’s databases.

Semantics of a Foundational Subset for Executable UML Models RFP (document ad/2005-04-02)
The objective of this RFP is to enable a chain of tools that support the construction, verification, translation, and execution of computationally complete executable models. For the tool chain to link together, the interchanged models must conform to the same metamodel and semantics. By semantics, we mean the underlying meaning of exchanged models, that is, the constraints that models place on the runtime behavior of the specified system. To this end, it must be precisely defined how the elements of the metamodel specify such runtime behavior. In support of this objective, the RFP solicits proposals for the definition of a computationally complete and compact subset of UML 2.0 to be known as “Executable UML Foundation”, along with a full specification of the execution semantics of this subset. “Computationally complete” means that the subset shall be sufficiently expressive to allow definition of models that can be executed on a computer either through interpretation or as equivalent computer programs generated from the models through some kind of automated transformations. “Compact subset” means that the selected metamodel should include as small a subset of UML concepts as is practicable to achieve computational completeness. The intent is for this subset to serve as a shared semantics foundation that would support additional semantics and subset definitions covering the higher-level formalisms defined in UML, such as state machines, activities, and interactions, as well as some of the more complex actions. We would expect the subset to include much of the action model and some of the activities as required by the integration of actions and activities in UML 2.0. This RFP is, therefore, intended to be the first of a set of complementary follow-on RFPs that would build on the foundations covered in this RFP. The following is one possible partitioning of semantic domains to be covered by one or more subsequent RFPs: 1. Composite structure and components 2. State machines 3. Activities 4. Interactions 5. Complex actions

Software Metrics Metamodel RFP (document admtf/2006-09-03)
Submitters are requested to propose a SMM which facilitates the interoperability of measurements of software artifacts. Measures are comparable evaluations and, as such, are critical to software engineering and architecture driven modernization

Space System Monitor and Control Service RFP (document space/2004-06-08)
There are a variety of ground system applications in the space domain that require access to monitor data extracted from satellite (or ground segment) telemetry, as well as the ability to control satellites and ground segment facilities. But just as there are a variety of applications that require these services, there are a variety of front-end telemetry and command processing applications that provide them, each with its own interface definition. A given client application must then adhere to a variety of interfaces in order to access telemetry and command services within a ground system. This increases the cost of developing and testing the system on a mission-to-mission basis, and adds costs during operations as new client applications are added. This RFP solicits proposals for the following: - Space System Monitor and Control Service.

Spacecraft Operations Language Metamodel RFP (document space/2005-06-01)
Automation of ground station operations is crucial to efficient and cost-effective spacecraft operations. Automation is achieved when scripted procedures are used to conduct normal operations, such as configuration of ground equipment for a satellite contact, commanding the spacecraft or payload to a new configuration, commanding a spacecraft maneuver, and monitoring of spacecraft data. There are a variety of automation languages in use today. These languages are incompatible between different ground systems developers. Transfer of a satellite from one ground system to another ground system, as would occur during a ground system upgrade, is therefore more expensive due to the required conversion of thousands of lines of automation procedure code. Using a standard definition or metamodel of a spacecraft operations language would make transitions and upgrades less expensive. Other areas of benefit would be direct transfer of test and configuration procedures from the factory to operations environments and increased interoperability among ground systems. This RFP solicits proposals for the following: • A spacecraft operations language metamodel

SwA Evidence Metamodel RFP (document swa/2007-09-03)
This RFP solicits proposals for a metamodel for representing information related to Software Assurance Evidence (referred as SwA Evidence). This metamodel shall provide a common repository structure that will facilitate the exchange of information between different Software Assurance tools and services. This is the first in the series of Software Assurance (SwA) standards that include claims, arguments and evidence, that once all completed will establish a common framework for analysis and exchange of the information related to software trustworthiness. This completed framework will allow users to begin SwA activities knowing that there is interoperability between the different tools producing highly automated SwA solutions. Standardization will ensure that end users are investing not just in individual tools but also rather into a coordinated strategy. To complete framework our roadmap includes additional RFP(s) related to representation of Software Assurance Claims and Arguments. This RFP recognizes the existence of OMG specifications that are related to SwA. The response to this RFP should utilize these specifications or indicate why they are inadequate. Responders to this RFP are encouraged to reuse and possibly extend (if needed) existing OMG standards in order to make them more appropriate to the SwA domain.

TACSIT Controller Service RFP (document c4i/2007-06-16)
The domain of Combat Management Systems is characterized by a huge variety of underlying computing platforms, with different and often incompatible means of managing & reporting alerts. A standards-based interface to common TACtical SITuation (TACSIT) Controller services are essential for interoperable and open systems. This RFP solicits proposals for the following: • A standard for TACSIT Controller Interface in CMS systems, consisting of a standard set of technical services and software interfaces to interact with TACSIT display systems.

UML Profile and Metamodel for Services (UPMS) RFP (document soa/2006-09-09)
Globalization and the Internet have resulted in the need to define more loosely coupled components executing in distributed heterogeneous environments. Service Oriented Architectures (SOA) represent an approach to Information Technology (IT) development that facilitates this loose coupling while at the same time providing sufficient qualities of services necessary for acceptable solutions. There are a number of existing and emerging/evolving runtime platforms resulting in a need to abstract their commonality and define standards for interoperability and information exchange. This Request for Proposal solicits submissions for a UML Metamodel and Profile for Service (UPMS). Essentially, the UPMS RFP requests a services metamodel and profile for extending UML with capabilities applicable to modeling services using an SOA. The profile will define extensions for modeling and integrating services within and across business enterprises. UPMS will include facilities for formal specification of service contracts that may be developed directly using the profile, or abstracted from business processes. It will also include facilities for indicating which of these contracts are fulfilled by modeled service providers.

UML Profile for Advanced and Integrated Telecommunication Services RFP (document mars/2008-06-09)
Submitters are requested to propose a UML Profile for designing advanced and integrated Telecommunication services. An advanced and integrated telecom service generally means a service that exploits the convergence of communication networks - landline, wireless and voice, and in the same time takes advantage of the plethora of facilities accessible from the World Wide Web. Sensibility to user context - like presence, localization, user preferences and use of communication means (like SMS or voice messaging) are some of typical ingredients that appear in innovative telecommunication services that operators or third party service providers would like to offer to end-users. Application of model-driven techniques for an agile development of this new kind of services will be facilitated by the definition of a domain specific UML profile.

UML™ Profile for Data Distribution Service RFP (document mars/2006-09-40)
To solicit submissions for a UML™ profile which provides model-based analysis & design capabilities for systems using the Data Distribution Service (DDS). The OMG Data Distribution Service (DDS) is a middleware specification for publish-subscribe data-distribution systems with Quality of Service parameters to enable fine-tuning of data flow to satisfy performance/reliability requirements. The need to manage this complex communication, and the QoS parameters, in a coherent manner, motivates this RFP.

Current Specification Revision Processes (available to members only:

2nd CWM 1.2 RTF

2nd Lw Load Balancing (LW-LDB) FTF

2nd Model-Level Testing and Debugging FTF

2nd PLM Services V2.0 FTF

2nd UML Profile for MARTE FTF

ADM KDM 1.2 RTF

AMSM FTF 2

Ada Language Mapping 1.3 RTF

Alerts Management Service 1.0 (ALMAS) FTF

BMM 1.1 RTF

BPDM 1.1 RTF

Conversion Model FTF

DDS Interoperability RTF

Data Distribution Interoperability 2.1 RTF

Data Distribution RTF 3

EXPRESS Metamodel FTF

FTF FTF

Ground Equipment Monitoring Service 1.0 (GEMS) FTF

Lw Load Balancing FTF

MOF 2 Core RTF

MOF 2.0 Facility and Object Lifecycle FTF

MOF Model to Text RTF 1.1

OCL 2 RTF

ODM FTF 2

PAGE-OM FTF

PIM & PSM for SWRadio RTF2

PRR FTF

QVT RTF 1.1

QoS for CCM 1.1 RTF

Robotic Localization Service 1.0 (RLS) FTF

SBVR RTF

Smart Antenna FTF

SysML 1.2 RTF

SysML RTF

UML 2.2 RTF

UML 2.3 RTF

UML Profile for DDS (UML4DDS) FTF

Voice RTF 1.1

XMI for MOF 2 (XMI 2.1) RTF

XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF

Copyright © 1997-2008 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 Netscape Navigator, 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. Last Updated Tuesday, January 01, 2008