Catalog of OMG Domain Specifications
This page provides a catalog of OMG specifications.
Specifications are listed alphabetically.
Description of Catalog Entries
Click here
for a description of each field for specifications catalogued below.
Understanding Terms Used
In order to understand the various terms used to identify
an OMG specification as it moves through its editing cycles, consult the OMG
Specifications Tutorial.
| Specification Name: |
Air
Traffic Control (ATC) |
| Description: |
Defines
interfaces used for implementing ATC systems that follow the
Model-View-Controller paradigm. |
| Domain: |
Transportation |
| Keywords: |
ATC, design patterns, failure,
MVC, publish, recovery, subscribe |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Specification Name: |
Alert
Management Service (ALMAS) |
| Description: |
The domain of naval Combat Management Systems (CMS) is
characterized by a huge variety of underlying computing platforms,
with different and often incompatible means of managing and reporting
alerts. Standards-based alert management services are essential for
interoperable and open systems. This specification is a standard for ALert
MAnagement Service (ALMAS) in CMS systems, consisting of
a standard alerts data model and a model for an alert delivery and
lifecycle management service. |
| Domain: |
Command,
Control, Communications, Computers, Intelligence (C4I) |
| Keywords: |
alert, alert
clients, alert instance, alert template, CMS, DCOM, event |
| Latest
/ past specifications: |
|
Current version: 1.0 |
|
Past versions: n/a |
|
| Related Industry Standards: |
OASIS Common Alerting Protocol, v1.0,
http://www.oasis-open.org/committees/download.php/6334/oasis-200402-cap-core-1.0.pdf |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Application
Management and System Monitoring for CMS Systems (AMSM) |
| Description: |
This
specification provides standardization of AMSM support for naval
Combat Management Systems (CMS). |
| Domain: |
Command,
Control, Communications, Computers, Intelligence (C4I) |
| Keywords: |
Application,
Application Model, Application Specification, Configuration,
Deployment Configuration, Executable Software Element, Executable
Software Element Specification, Host, Node, Service Infrastructure,
Software System, Software System Specification, System Infrastructure,
System Topology, System Topology Specifications |
|
Latest / past specifications:
|
|
Current version: 1.1 |
|
Past versions:
1.0 |
|
| Related OMG Specifications: |
CORBA/IIOP,
DDS V1.0,
Lightweight
Logging Service |
| Related Industry Standards: |
[CIM]
CIM Schema, DMTF, V2.9.0. 5 Jan, 2005. [CIMMOF] CIM 2.2
Specification, DMTF, 14 June 1999. (DSP0004). [CIMHTTP] CIM
Operations over HTTP, DMTF, V1.1.6 January, 2003. (DSP0200). [CIMXML]
Representation of CIM in XML, DMTF, V2.1.2 May, 2002. (DSP0201).[HPI]
Hardware Platform Interface Specification, SA Forum, HPI-B-01.01
January, 2005. [REGEXP] Chapter 9, "Regular Expressions" of
the Base Definitions volume of IEEE Std 1003.1-2001. [SNMP]
Simple Network Management Protocol. [WBEM] The Web Based
Enterprise Management Initiative. See the latest version available at
http://www.dmtf.org/standards/wbem/.
[XMLSchema] XML Schema,W3C Recommendation, 28 O |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Audio
/ Visual Streams (AVSTR) |
| Description: |
Standard
interfaces that control and manage audio and video stream
exchanges with Quality of Service (QoS) constraints, where
stream is defined as a set of flows of data between objects, and a
flow is a continuous sequence of frames in a clearly identified
direction. |
| Domain: |
Telecommunications |
| Keywords: |
ATM,
connection, device, flow, media, multimedia device interface,
protocol, QoS, stream, token, virtual multimedia devices |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Property
Service |
| Related Industry Standards: |
IMA
Recommended Practice, Multimedia Systems Services Part 1: Functional
Specification; TINA Object Definition
Language (TINA-ODL) MANUAL, PBL01 |
| Specification Name: |
Bibliographic
Query Service (BQS) |
| Description: |
Specification
of interfaces that provide the ability to query a bibliographic
repository for citations of a variety of document types, and retrieve
the citation matching the query criteria. |
| Domain: |
Life Sciences Research |
| Keywords: |
attributes,
bibliography, citation, matching, metadata,
ordering, query, repository, research, search |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
BSA, Gene Expression,
Genomic Maps, Naming
Service, Property
Service, Single Nucleotide Polymorphisms, Trading
Service, XMI |
| Related Industry Standards: |
Dublin
Core Metadata Element Set, Version 1.1; Getty Thesaurus of Geographic
Names; ISO639; ISO3166; ISO8601 |
| Specification Name: |
Bimolecular
Sequence Analysis (BSA) |
| Description: |
Services for
the analysis of biological macromolecular sequence data and associated
information, including facilities for their representation,
manipulation, and analysis. |
| Domain: |
Life Sciences Research |
| Keywords: |
ambiguity code,
coding sequence, expression, genetic code, Hidden Markov Model, HMM,
profile, sequence, sequence assembly |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
BQS,
CORBA/IIOP,
Gene Expression, Genomic
Maps, Life
Cycle Service, Macromolecular Structure,
Property
Service, XMI |
| Related Industry Standards: |
Genetic Codes (National Center
for Biotechnology Information) |
| Specification Name: |
Business
Motivation Model (BMM) |
| Description: |
The Business
Motivation Model specification provides a scheme or structure for
developing, communicating, and managing business plans in an organized
manner. Specifically, the Business Motivation Model does all of the
following:
• It identifies factors that motivate the establishing of business
plans.
• It identifies and defines the elements of business plans.
• It indicates how all these factors and elements inter-relate.
Among these elements are those that provide
governance for and guidance to the business — Business Policies and
Business Rules. |
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
Business
Process Definition Metamodel (BPDM) |
| Description: |
BPDM
provides the capability to represent and model business processes
independent of notation or methodology, thus bringing these different
approaches together into a cohesive capability. This is done using a
"meta model"1 – a model of how to describe business
processes – a kind of shared vocabulary of process with well defined
connections between terms and concepts. This meta model captures the
meaning behind the notations and technologies in a way that can help
integrate them and leverage existing assets and new designs. The meta
model behind BPDM uses the OMG "Meta Object Facility" (MOF)
standard to capture business processes in this very general way and to
provide an XML syntax for storing and transferring business process
models between tools and infrastructures. Various tools, methods and
technologies can then map their way to view, understand and implement
processes to and through BPDM. |
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
Business
Process Maturity Model (BPMM) |
| Description: |
BPMM
is intended for anyone interested or involved in improving an
organization's business process related to their products and services
- whether the products and services are for internal or external use.
This includes members of appraisal teams, members of process
engineering groups, managers, and professional staff. BPMM can be used
as a process model by itself or it can be used as a framework for
improvement efforts based on other models. |
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
Business
Process Modeling Notation (BPMN) |
| Description: |
Business
people are very comfortable with visualizing business processes in a
flow-chart format. There are thousands of business analysts studying
the way companies work and defining business processes with simple
flow charts. This creates a technical gap between the format of the
initial design of business processes and the format of the languages,
such as BPEL4WS, that will execute these business processes. This gap
needs to be bridged with a formal mechanism that maps the appropriate
visualization of the business processes (a notation) to the
appropriate execution format (a BPM execution language) for these
business processes.
Interoperation of business processes at the human level, rather than
the software engine level, can be solved with standardization of the
Business Process Modeling Notation (BPMN). BPMN provides a Business
Process Diagram (BPD), which is a Diagram designed for use by the
people who design and manage business processes. BPMN also provides a
formal mapping to an execution language of BPM Systems (BPEL4WS).
Thus, BPMN provides a standard visualization mechanism for
business processes defined in an execution optimized business process
language.
NOTE: The OMG specification begins with Version 1.1 as a previous 1.0 existed in industry.
|
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
Chemical
Structure and Access Representation (CSAR) |
| Description: |
CSAR is a set
of specifications describing the management of molecular information,
chemical structure access, and retrieval processes. |
| Domain: |
Life Sciences Research |
| Keywords: |
acyclic bonds,
aromaticity, atom, bit string, bond, charge, chiral, connection table,
counterion, cyclic bonds, electrons, fingerprints, heteroatoms,
Markush structure, molecule, orbital, query structure, radical,
registerable structure, similarity search, spin state,
stereochemistry, structural keys, substructure tautomer, valence |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG
Specifications: |
XMI |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Clinical
Decision Support Service (CDSS) |
| Description: |
This
specification specifies a platform-independent model (PIM) and a
platform-specific model (PSM) for XML Web services that define the
capabilities and interfaces of a DSS. These models fulfill the
requirements specified in the normative sections of the HL7 DSS SFM
while improving the simplicity and functional completeness of the
service interface. |
| Domain: |
Healthcare |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Specification Name: |
Clinical
Observations Access Service (COAS) |
| Description: |
The Clinical
Observations Access Service (COAS) specification is a set of interfaces and data
structures with which a server can supply clinical observations. COAS provides
a mechanism to allow for the retrieval of that clinical content via a
set of established interfaces. Effectively,
COAS provides a generic retrieval capability and is independent of an
information model. The
forthcoming Retrieve, Locate, and Update Service (RLUS) specification will
supersede COAS. This is
due to, among other issues, the absence of an information model and
accepted industry constructs inhibiting marketplace adoption of COAS.
RLUS is explicitly requiring support for HL7 semantic content,
while leaving open the possibility to support other information
models. The
computational aspects of COAS were analyzed and have been considered
during the development of the RLUS RFP. |
| Domain: |
Healthcare |
| Keywords: |
access, client, coding scheme,
LQS, PIDS, policy, server, Subject of Care |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Event Service, Naming
Service, PIDS, RAD, Trading
Service |
| Related Industry Standards: |
|
| Specification Name: |
Computer
Aided Design Services (CAD) |
| Description: |
Describes an
interface standard for Mechanical Computer Aided Design (CAD) systems
that enable the interoperability of CAD, Computer Aided Manufacturing
(CAM) and Computer Aided Engineering (CAE) tools. The aim is to
provide users of design and engineering systems the ability to
seamlessly integrate, best-in-class, software across a wide variety of
CAD/CAM and CAE applications through CORBA interfaces. These standard
interfaces enable a distributed product design environment that
includes a variety of CAD systems. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
boundary
representations, CAD, data translation, design, geometry,
manufacturing, mechanical engineering,
topology |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
PDM Enablers, Property
Service |
| Specification Name: |
Currency
(CURR) |
| Description: |
Specifies a set
of business objects and related abstractions as a proposed standard to
support international currency. |
| Domain: |
Finance |
| Keywords: |
arithmetic, calculator,
currency, exchange rate, money, rounding, security |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Query Service,
Relationship
Service |
| Related Industry Standards: |
|
| Specification Name: |
Data
Acquisition from Industrial Systems (DAIS) |
| Description: |
Support of
efficient real time transfer of large amounts of data from an
industrial process to a wide range of clients and support of discovery
of parameters and update of parameter values. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
Data Access
Facility, Distribution Management System, Energy Management System,
EPRI, PLC, RTU, SCADA, UMS |
| Latest / past specifications: |
|
Current version: 1.1 |
Past versions: 1.0 |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Historical Data Acquisition from Industrial Systems,
Utility Management Systems Data Access Facility |
| Related Industry Standards: |
EPRI TR-106324;
IEC standard 1346-1; IEC standard 61970 and 61970-30x.; OPC Alarm and
events 1.02; OPC Data access version 2.03 |
| Specification Name: |
Distributed
Simulation Systems (DSS) |
| Description: |
A common
technical framework facilitating the interoperability of all types of
models and simulations among themselves and with command and control
systems, as well as facilitating the reuse of modeling and simulation
components. |
| Domain: |
Simulation |
| Keywords: |
High Level Architecture, HLA,
simulation, federation |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Related Industry Standards: |
IEEE P1516.2 |
| Specification Name: |
Gene
Expression (GENE) |
| Description: |
A
standard that addresses the representation of gene expression data and
relevant annotations, as well as mechanisms for exchanging these data. |
| Domain: |
Life Sciences Research |
| Keywords: |
array,
background, biomaterial,
biosequence
cluster,
cell line, channel, chip. cluster analysis, compound, error model,
expression, image analysis, label, quantitation type, normalization,
photolithography, probe, profile, protocol application, repeated
measurement, replicate experiments, sequence, targe5t ,time series,
virtual array |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
BQS, BSA,
Collection
Service, Life Sciences Identifiers, Query
Service, XMI |
| Related Industry Standards: |
NCBI
Taxonomy database,
http://www.ncbi.nlm.nih.gov/Taxonomy/tax.html;
World
Wide Web Consortium. 2000. Extensible Markup Language (XML) 1.0 (Second Edition);
World Wide Web Consortium. 2000. XML Schema |
| Specification Name: |
General
Ledger (LEDG) |
| Description: |
Defines
the interfaces and their semantics that are required
to enable interoperability between General Ledger systems and
accounting applications, as well as
other distributed objects and applications for accounting purposes. |
| Domain: |
Finance |
| Keywords: |
accounting, accounts payable,
accounts receivable, bookkeeping, ledger, payroll |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Related Industry Standards: |
COMPASS;
International Accounting Standards; ISO/IEC 10746-1-3; ISO/IEC
JTC1/SC21 |
| Specification Name: |
Genomic
Maps (GMAPS) |
| Description: |
A standard for representing
genomic maps and their contents. |
| Domain: |
Life Sciences Research |
| Keywords: |
assignment,
expressed sequence tag, genomic map, idiogram, linkage analysis |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Related OMG Specifications: |
BQS,
BSA,
CORBA/IIOP,
Event Service, Lexicon
Query Service, Macromolecular Structure,
PIDS, Property
Service, Query
Service, Single Nucleotide Polymorphisms |
| Specification Name: |
Ground
Equipment Management Service (GEMS) |
| Description: |
The intent of GEMS is to define a
lightweight, easy-to-use interface model suitable for control and
status of nearly all types of devices within space-related ground
systems. In truth, these devices are not unique to space
communications. Modern ground systems include many commercial devices
such as networking devices and digital archive systems. While this
specification focuses specifically on space applications, it is
designed to apply to a broad range of devices. |
| Domain: |
Space |
| Keywords: |
Consultative Committee for Space Data
Systems (CCSDS); General Command for Programmable Instrumentation (GCPI);
General Purpose Interface Bus (GPIB); Simple Network Management
Protocol (SNP); Space Link Extensions (SLE); Telemetry Tracking &
Commanding (TT&C) |
| Latest / past specifications: |
|
| Contact
Information: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
HData
RESTful Transport (HData) |
| Description: |
This specification defines how the abstract
hierarchical organization defined within the HRF specification is
access and modified through a RESTful approach, using HTTP as the
access protocol. It creates a unique mapping to a URL structure, and
defines how HTTP verbs such as GET, PUT, DELETE, etc. affect the
underlying information. |
| Domain: |
HL7 |
| Finalization
Information: |
|
|
| Specification Name: |
Historical
Data Acquisition from Industrial Systems (HDAIS) |
| Description: |
This specification defines a number of interfaces for
a time series data management facility. The motivation is to enable
integration between the various existing or emerging products that
produce or consume historical data, such as: remote terminal units,
process control units, SCADA (Supervisory Control and Data
Acquisition) systems that produce historical data to be recorded;
maintenance and persistent storage systems that consume historical
data (a historical data management facility); clients retrieving data
for discovery, presentation and update; clients retrieving data for
analysis and or input to calculations; and bridges to and from
existing OPC Historical data services. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
concurrency
control, connection interfaces, DAIS, Energy
Management System (EMS), EPRI Common Information Model (CIM), IO
interfaces, OPC, Programmed
Logic Controller (PLC), power system, Resource
Description Framework (RDF), Remote Terminal Unit (RTU), SCADA,
Utility
Management System (UMS), Water Quality and Energy Management System (WQEMS) |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Data Acquisition from Industrial Systems, Utility
Management Systems Data Access Facility, UML |
| Related Industry Standards: |
IEC
61346-1, Structuring and Naming; IEC 61970;
OLE
for Process Control (OPC), XML |
| Specification Name: |
IT
Portfolio Management Facility (ITPMF) |
| Description: |
This specification provides an
Enterprise Organization Facility platform independent model and
platform-specific interface specifications.
An enterprise organization structure consists of organizational
entities and the relationships between them.
This facility is to allow applications the ability to define,
navigate, and retrieve information defining an enterprise’s
organizational structure. This
includes information about the organizational units that make up an
enterprise, the human resources that belong to those organizational
units, and the structure and relationships that connect them all
together. |
| Domain: |
cross-domain |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Keywords: |
agreement,
blob, communication connection, contact, context, control, dependency,
deployable elements, date, event, information, interest, location,
observation, party, platform, process, requirements, service,
timestamp |
| Related OMG
Specifications: |
CWM,
MOF, RAS,
SPEM, UML,
UML Profile for EAI, UML
Profile for EDOC, XMI |
| Related Industry Standards: |
RM-ODP,
W3C
XML |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Identity
Cross-Reference Service (IXS) |
| Description: |
The scope of this specification
is the interfaces, operations, and information structure required to
uniquely identify various kinds of entities within disparate systems
within a single enterprise and/or across a set of collaborating
enterprises. These service interfaces are intended to be used within a
healthcare setting, in which the security of data exchanges is both
important and regulated by laws such as HIPAA in the United
States.
|
| Latest / past specifications: |
|
Current version: 1.0.1 |
Past versions: n/a |
|
| Domain: |
Health |
| See also: |
Retrieve,
Locate, and Update Service (RLUS) |
| Specification Name: |
Laboratory
Equipment Control Interface Specification (LECIS) |
| Description: |
LECIS
defines a discrete state and communication model for laboratory
devices. |
| Domain: |
Life Sciences Research |
| Keywords: |
DCD,
device capability dataset, event, macro command, registry, SLM,
standard laboratory module, SCD, system capability dataset, task, task
sequence controller, TSC, UNC, variable, workcell |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Related Industry Standards: |
American Society for Testing
and Materials Standard E1989-98,
W3C
XML |
| Specification Name: |
Lexicon
Query Service (LQS) |
| Description: |
Specifies
a set of common, read-only methods for accessing the content of
medical terminology systems. |
| Domain: |
Healthcare |
| Keywords: |
association,
blob, characteristic, coding scheme, concept, definition, lexical,
naming authority, pick list, registration authority, role, source,
target, terminology, usage |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Trading Service |
| Related Industry Standards: |
CEN
ENV 12264: 1995; ISO 1087:1990; ISO/IEC 7826-1,-2 : 1994; ISO/IEC
8824-1 (1994); Unified Medical Language System |
| Specification Name: |
Life
Sciences Analysis Engine (LSAE) |
| Description: |
In the Life Sciences domains there are many computer methods for
analyzing and deriving data. The goal of this specification is to
describe how to access them in an interoperable way in a distributed
environment. It includes the execution and control of computer methods
(represented as applications, programs, processes, threads, or
otherwise) and dealing with their inputs, output, and functionality.
Particularly, it addresses: both synchronous and asynchronous invocation of the remote tools; the
ability to transport data to and from the remote tools both in its
entirety and in smaller chunks; and the ability to interact with the
tools that has been already started.
|
| Domain: |
Life Sciences
Research |
| Keywords: |
client-poll
notification, controlling analysis execution, event, heartbeat, input
and output data, Java, job state, metadata, percent progress,
provider-defined events, step progress, time progress, web services |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG
Specifications: |
Event
Service, Life Sciences Identifiers, Notification
Service, Single Nucleotide Polymorphisms, XMI |
| Related Industry
Standards: |
Web Services Notification,
http://www-106.ibm.com/developerworks/library/specification/ws-notification/
Web Services
Basic Profile:
http://www.ws-i.org/docs/charters/WSBasic_Profile_Charter1-1.pdf |
| Specification Name: |
Life
Sciences Identifiers (LIS) |
| Description: |
This specification addresses
the need for a standardized naming schema for biological entities in
the Life Sciences domains, the need for a service assigning unique
identifiers complying with such naming schema, and the need for a
resolving service that specifies how to retrieve the entities
identified by such naming schema from repositories.
|
| Domain: |
Life Sciences Research |
| Keywords: |
assignment, discovery,
identifiers, Java, PSM, resolution, service, SOAP, web services |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
Gene
Expression, Life Sciences Analysis Engine, Single
Nucleotide Polymorphisms, XMI |
| Related Industry Standards: |
International
Standard for representation of dates and times
http://www.iso.ch/iso/en/prods-services/popstds/datesandtime.html |
| Specification Name: |
Macromolecular
Structure (MACSTR) |
| Description: |
The
specification of appropriate interfaces for representing and accessing
biological macromolecular structure data and associated information. |
| Domain: |
Life Sciences Research |
| Keywords: |
factory, Miller
indices, phase calculations, space group, structure factor,
temperature factor |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
BSA,
CCM, CORBA/IIOP,
Genomic Maps, MOF,
Property
Service, Time
Service |
| Specification Name: |
Management
of Event Domains |
| Description: |
Specifies
an architecture and interfaces for managing event domains (sets of one
or more event channels that are grouped together for the purposes of
management, and/or for providing enhanced capabilities to the clients
of those channels such as improved scalability.) |
| OMG Cross Reference: |
CORBAservices
Specifications |
| Specification Name: |
Metamodel
for the Federal Transition Framework (FTF) |
| Description: |
This
specification is designed to move the evolution of the Federal
Transition Framework into the general community of the OMG
(industrial, governmental, and academic). The initial standard is
therefore based on the existing release of the Federal Transition
Framework released by the President’s Office of Management and
Budget (OMB). A key aspect of this specification is to move the FTF
specification’s primary representation from an XML Schema
representation to a Platform Independent Model (PIM) of the FTF
semantics from which the XML Schema is derived as a Platform Specific
Model (PSM). This opens the evolution of the FTF to its expression in
multiple technologies (PSMs) going forward |
| Domain: |
Government |
| Keywords: |
Back Office Services
Domain, Business Analytical Services Domain, Business Areas, Business
Management Services Domain, Business Reference Model (BRM), Component
Framework, Customer Services Domain, Data Reference Model (DRM),
Digital Asset Services Domain, Government Resources Business Area,
Measurement Areas, Measurement Indicators, Mode of Delivery,
Performance Reference Model (PRM), Process Automation Services Domain,
Service Access and Delivery, Service Component Reference Model (SRM),
Service Interface and Integration, Service Platform and
Infrastructure, Services Business Area, Services for Citizens, Support
Delivery, Support Services Domain, Technical Reference Model (TRM) |
| Latest/Past
specifications: |
Current version: 1.0
Past versions: n/a
|
| Finalization
Information: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Model
for Performance-driven Government (MPG) |
| Description: |
Specifies a model that
provides a uniform basis for agencies within the U.S. Federal
Government to represent, analyze, and report on their enterprise-level
transformation activities. It specifies how key transformation
elements such as segment architecture, performance architecture, and
investment planning model content are to be represented. It supports
repository maintenance of that content and the fundamental information
required to meet transparency and accountability goals. |
| Domain: |
Government |
| Finalization
Information: |
|
| Latest / past specifications: |
|
Current version: n/a |
Past versions: n/a |
|
| Specification Name: |
Model
Driven Message Interoperability (MDMI)
formerly known as
Conversion
Models for Payment Message Standards) |
| Description: |
Provides
a declarative, model driven mechanism to perform message
transformation - not only to handle the movement of data between
different message formats, but also to create a versioning mechanism
so that new version of a message can be mapped to older version,
thereby reducing the barriers that prevent the introduction of new
versions of messages and greatly reducing the cost of change. |
| OMG Cross Reference: |
Modeling Specifications |
| Specification Name: |
Negotiation
Facility (NEG) |
| Description: |
Specifies
an architecture comprised of specifications that relate to the
OMG-compliant interfaces for distributed electronic commerce systems. |
| Domain: |
Electronic Commerce |
| Keywords: |
abstract,
active, agency, collaboration, composition, containment, delegation,
DOM, encounter, engagement, framework, jurisdiction,
resource, role, template, transition, user |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Notification
Service, Task and Session |
| Related Industry Standards: |
W3C
DOM |
| Specification Name: |
OMG
Systems Modeling Language (OMG SysML)
|
| Description: |
The
OMG Systems Modeling Language (OMG
SysML™) is a general-purpose graphical modeling language for
specifying, analyzing, designing, and verifying complex systems that may
include hardware, software, information, personnel, procedures, and
facilities. In particular, the language provides graphical representations
with a semantic foundation for modeling system requirements, behavior,
structure, and parametrics, which is used to integrate with other
engineering analysis models. SysML represents a subset of UML 2.0 with
extensions needed to satisfy the requirements of the UML™
for Systems Engineering RFP. SysML uses the OMG XML Metadata Interchange (XMI®)
to exchange modeling data between tools. |
| Domain: |
Systems Engineering |
| Keywords: |
Consult
SysML Glossary located within
http://docs.omg.org/ad/06-03-04.pdf |
| Latest / past specifications: |
|
Current version: 1.2 |
Past versions: 1.1 |
|
| Practitioner
Certification: |
|
| Contact Information: |
|
| Revision
Information: |
|
| Related OMG
Specifications: |
UML,
XMI |
| OMG Cross Reference: |
Modeling
and Metadata Specifications UML
Profile Specifications |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Party
Management Facility (PARTY) |
| Description: |
Provides
interfaces that allow external users (people, application programmers,
or other systems) to access and manipulate party related information
in a consistent and well-defined manner. |
| Domain: |
Finance |
| Keywords: |
contact information,
containment, party, PMF, property, role |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Externalization
Service, Life
Cycle Service, Naming
Service, Property
Service, Time
Service, Trading
Service, Transaction
Service |
| Specification Name: |
Person
Identification Service (PIDS) |
| Description: |
This
specification defines the interfaces that organizes person ID
management functionality to meet healthcare needs. It
is a specification of a Person Identification Service with UML models
and a complete specification in CORBA IDL.
This includes most of the functions for managing a patient
identity. The traits of
an identity in this specification used the HL7 v2.3 and the vCard
specifications. PIDS
has been used as a primary source for many of the ideas in the
forthcoming Entity Identification Service (EIS) specification. (EIS
can be seen as bringing PIDS up to date, although the additional
“Entity” abstraction provides for additional flexibility of use.) |
| Domain: |
Healthcare |
| Keywords: |
bind, CPR, EMPI, federation,
identifier, identity, MPI, matching, naming authority |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
COAS,
CORBA/IIOP, Naming
Service, RAD, Trading
Service |
| Related Industry Standards: |
HL7;
ASTM E1239; ASTM E1714; ASTM E1385; ASTM E1715 |
| Specification Name: |
Phenotype
and Genotype Object Model (PAGE-OM) |
| Description: |
Specifies the rational and functional segmentation of
genotype-phenotype information into sub-components that are
operationally distinct (the high-level objects in the model) and lays
out the natural inter-relationships between these components. |
| Domain: |
Life
Sciences |
| Keywords: |
allele
, anatomic location, assay set, assembly, association
study, block ,category, CDS, contributor, correlation
experiment, cytogenetic, derivation methods, Db xref, consensus,
disease, disease Category, environment, exon, frequency Set,
functional change, gene based, genomic, genotype, haplotype,
heterozygosity, individual, landmark , location, map, methodology,
method observation, molecular sample, neighbor variation, observable
feature, observation, oligo, ordered location, ordered map, panel,
phenotype, physical map, population, product change, residue change,
sequence, sequence map, structural change, taxon, target observation,
variation |
| Latest / past specifications: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
PIM
and PSM for Smart Antenna (smartant) |
| Description: |
This Specification supports a smart antenna subsystem that can be utilized for expanding a single
antenna system to array antenna system. The Smart Antenna
specification is physically partitioned into three major chapters: UML
Profile for Smart Antenna (SA), SA PIM, and SA
PSM. UML Profile for SA
defines a language for modeling a smart antenna system by expanding the
UML language. SA PIM provides a set of interfaces for interfacing with
the signal processing module, RF module, and controller module. SA PSM
provides a rule for transforming the elements of the Profile and
SA
PIM into the platform specific model for CORBA IDL and XML. The SA
specification is related to "Communication Channel and Equipment
Specification (formal/07-03-02)" volume in such a way that
stereotypes and class that have not been commented in the SA
specification are defined in it. |
| Domain: |
Software-based
Communications |
| Keywords: |
component,
direction of arrival (DOA), digital signal processor (DSP), facility,
field programmable gate array (FPGA), general purpose processor (GPA),
input/output (I/O), radio frequency (RF), smart antenna (SA), software
defined radio (SDR) |
| Latest / past specifications: |
|
| Related OMG Specifications: |
CORBA,
CORBA/e, OCL,
Real-time CORBA, UML,
UML Profile for
CORBA, UML Profile
for Software Radio |
| OMG Cross Reference: |
UML
Profile Specifications |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Platform
Independent Model (PIM) & Platform Specific Model (PSM) for Super
Distributed Objects (SDO) |
| Description: |
This specification abstracts existing resource interconnection
technologies into a higher layer, define their information, and
computational models in the layer, and make objects defined the models
interoperable. It does not address access control or security aspects. |
| OMG Cross Reference: |
Embedded
Intelligence Specifications |
| Specification Name: |
Product
Data Management Enablers (PDME) |
| Description: |
Standard
interfaces to Product Data Management systems, or other systems
providing similar services, from other manufacturing software systems. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
change
management, configuration management, document management, effectivity,
PDM, product structure definition, STEP |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
CAD Services, Life
Cycle Service, PLM Services, Property
Service, Query
Service, Relationship
Service, Security
Service, Time
Service, Transaction
Service, Workflow |
| Related Industry Standards: |
ISO
10303-21:1994(E), ISO 10303-41:1994(E), ISO 10303-44:1994(E), ISO
10303-203:1994(E), ISO 10303-214 Committee Draft 2, 1997,
WFMC-TC-1003, 29-Nov-94, 1.1, RM-ODP, SEMATECH Computer Integrated
Manufacturing (CIM) Application Framework Specification 1.3 |
| Specification Name: |
Product
Lifecycle Management Services (PLM) |
| Description: |
This
specification defines a Platform Independent Model (PIM) for Product
Lifecycle Management Services. Its informational model is derived from
the ISO 10303-214 STEP model by an EXPRESS-X mapping specification and
a EXPRESS-to-XMI mapping process. The functional model is derived from
the OMG PDM Enablers V1.3. The specification defines a Platform
Specific Model (PSM) applicable to the Web Services implementation
defined by a WSDL specification, with a SOAP Binding, and a XML Schema
specification. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
abstract class,
abstraction, action, action sequence, action state, activation,
EXPRESS, MDA, schema, STEP, web services, WSDL |
| Latest / past specifications: |
|
Current version: 2.1 |
Past versions: 2.0 |
|
| Related OMG Specifications: |
MOF,
PDM Enablers, UML,
XMI |
| Related Industry Standards: |
ISO
10303-11:1994; ISO 10303-14:2001; ISO CD 10303-25:2003; ISO TS
10303-28: 2002; ISO 10303-203:2000; ISO 10303-214:2000; ISO
10303-232:2001; ISO/IEC 10746,
W3C
XML Schema,
W3C
WSDL |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Production
Rule Representation (PRR) |
| Description: |
This
specification provides a standard production rule representation that is
compatible with rule engine vendors' definitions of production rules. It
can be used for interchange of business rules amongst rule modeling tools
(and other tools that support rule modeling as a function of some other
task). • It provides a standard production rule representation that is
readily mappable to business rules, as defined by business rule management
tool vendors. • It provides a standard production rule definition that
supports and encourages system vendors to support production rule
execution. • It provides an OMG MDA PIM model with a high probability of
support at the PSM level from the contributing rule engine vendors and
others, and can be included to add production rule capabilities to other
OMG metamodels. • It provides examples of how the OMG UML can be used to
support production rules in a standardized and useful way. • It provides
a standard production rule representation that can be used as the basis
for other efforts such as the W3C Rule Interchange Format and a production
rule version of RuleML. |
| OMG Cross Reference: |
Business
Modeling Specifications |
|
| Specification Name: |
Property
and Casualty Information Models (PC) |
| Description: |
This
specification addresses the data management needs of
the Property and Casualty (P&C) insurance community. It uses OMG’s
Model Driven Architecture principles and related standards (http://www.omg.org/mda/).
Also, this specification uses existing P&C industry standards
(e.g., IBM’s IAA) as a source for the P&C Business Glossary and
associated models. The scope for this initiative includes the U.S.P&C
marketplace data for the core Party, Policy, and Claims Subject Areas.
Additional data models have been included to sub-types and roles and
to further describe the major entity concepts of Accounts and
Agreements, Assessments, Events, and Money. |
| Domain: |
Finance |
| Finalization
Information: |
|
| Specification Name: |
Public
Key Infrastructure (PKI) |
| Description: |
This
specification describes interfaces, constants, and constructs for
interacting with a PKI through CORBA objects. |
| Domain: |
Electronic Commerce |
| Keywords: |
authority, CA, certificate,
CRL, key, registration, RA, repository |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact
Information: |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Specification Name: |
Records
Management Services (RMS) |
| Description:
|
This
specification provides models for software services to support
management activities for electronic records. Following the OMG MDA
framework, models are provided that describe the platform independent
model (PIM) which defines the business domain of Records Management
and the RM services to be provided. Three technology-specific
implementations are specified: 1. PSM-1 - Web Services definition for
Records Management Services in Web Service Description Language (WSDL).
This is actually supplied as ten WSDL files; one for each Records
Management Service. 2. PSM-2 - A Records Management Service XSD. The
XSD is for use in creating XML files for import/export of Managed
Records from compliant environments and to use as a basis for forming
XQuery/XPath statements for the query service. 3. PSM-3 - An Attribute
Profile XSD. The XSD is for capturing and communicating attribute
profiles to permit flexible attribution of certain types of Records
Management Objects. |
| Domain: |
Government |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Specification Name: |
Reference
Metamodel for the EXPRESS Information Modeling Language (EXPRESS) |
| Description: |
The purpose of this specification is to
provide a common basis for communication among tools that create or
compile EXPRESS models, analyze them, and/or map them to various forms
of implementation specifications. It is also intended to serve as a
basis for the definition of formal standard mappings to other modeling
and implementation languages.
|
| Domain: |
Space |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Specification Name: |
Requirements
Interchange Format (ReqIF) |
| Description: |
The
Requirements Interchange Format described in this specification
defines an open, non-proprietary exchange format. Requirement
information is exchanged by transferring XML documents that comply to
the ReqIF format. |
| Latest / past specifications: |
|
Current version: 1.0
.1 |
Past versions: n/a |
|
| Specification Name: |
Resource
Access Decision (RAD) |
| Description: |
The Resource
Access Decision (RAD) Facility is a mechanism for obtaining
authorization decisions and administrating access decision policies.
It enables a common way for an application to request and receive an
authorization decision. The facility is intended to be used by
security-aware applications. |
| Domain: |
Healthcare |
| Keywords: |
access decision,
administrative view, healthcare, policy, RAD, resource |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
COAS,
CORBA/IIOP, PIDS,
Security Service |
| Related Industry Standards: |
HL7;
ASTM E1239; ASTM E1714; ASTM E1385; ASTM E1715 |
| Specification Name: |
Retrieve,
Locate, and Update Service (RLUS) |
| Description: |
This web service specification seeks to define, at a service level,
appropriate interfaces to locate, retrieve, and update resources among
and between healthcare organizations. It is not intended to replace
existing systems or implementations, but to create an interface
standard for a service-oriented layer to expose those healthcare
assets and resources within an organization that are needed to meet
business or medical needs.
|
| Latest / past specifications: |
|
Current version: 1.0.1 |
Past versions: n/a |
|
| Domain: |
Health |
| See also: |
Identity
Cross-Reference Service (IXS) |
| Specification Name: |
Robotic
Localization Service (RLS) |
| Description: |
This
specification defines a localization service that can handle data and
usages specific to use in robotics. It includes a platform-independent
model (PIM) as well as a mapping of this PIM to platform-specific
models (PSM) defined by C++.
|
| Domain: |
Robotics Software Development |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Related Industry Standards: |
[ISO19103] International Organization
for Standardization, Geographic information -- Conceptual schema
language, 2005; [ISO19107] International Organization for
Standardization, Geographic information -- Spatial schema, 2003;
[ISO19111] International Organization for Standardization, Geographic
information -- Spatial referencing by coordinates, 2007; [ISO19115]
International Organization for Standardization, Geographic information
– Metadata, 2003; [PER] International Telecommunication Union
Telecommunication Standardization Sector, Specification of Packed
Encoding Rules (PER), ITU-T Rec. X.691 (2002) / ISO/IEC 8825-2:2002 |
| Specification Name: |
Robotic
Technology Component (RTC) |
| Description: |
This specification defines a
component model and certain important infrastructure services
applicable to the domain of robotics software development. It includes
a Platform-Independent Model (PIM) expressed in UML and
Platform-Specific Models (PSMs) expressed in OMG IDL.
|
| Domain: |
Robotics Software Development |
| Keywords: |
basic types, components,
execution semantics, introspection, literal specifications, modes of
operation, periodic, sampled data, stimulus response |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Lightweight CCM, SDO, UML |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Semantics
of Business Vocabulary and Business Rules (SBVR) |
| Description: |
The
SBVR specification is designed to support interchange of business
vocabularies and rules among organizations.
SBVR is conceptualized optimally for business people and
designed to be used for business purposes independent of information
systems designs. It
is also intended to provide the business vocabulary and business rules
underpinned by First Order Predicate Logic for transformations by IT
staff into information system designs.
Note that, in most cases, such transformations will not be
fully automated; there will be many options for information system
design, with decisions required from system architects and PIM
modelers. |
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
Shared
Operational Picture Exchange Services (SOPES) Information Exchange
Data Model (IEDM) |
| Description: |
The objective of the combined SOPES + IEF
capability will be the specification an architecture-driven,
policy-enforced Information environment that enables shared
situational awareness and empowering decision support through an
interoperable operating environment. The resulting specifications will
enable ECM alerting, response, consultation, collaboration, command,
control and communications capability which are expected to evolve
over time and adapt to community information and knowledge sharing
needs. The specifications will enable individual communities and/or
organizations to tailor solutions to their own legislated mandate,
policies, and practices. |
| Domain: |
c4i |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Specification Name: |
Single
Nucleotide Polymorphisms (SNP) |
| Description: |
This specification addresses the need for a
standardized data exchange format for Single Nucleotide Polymorphisms
(SNPs) entities in the Life Sciences domains. As a result of recent
advances in SNPs research, a large amount of experimental data has
been accumulating. Standardization is required to facilitate
exchanging these data and developing interoperable systems for
managing and analyzing them. Single nucleotide polymorphisms (SNPs)
are common |
| Domain: |
Life Sciences Research |
| Keywords: |
Assay, Bibliographic
References, Frequency, Haplotype, Identifiable, Individual, Map, MDA,
Sequence, Translation. |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
Bibliographic
Query Service,
Genomic Maps, Life Sciences Analysis Engine, Life Sciences Identifiers, XMI |
| Specification Name: |
Space
Operations Language Metamodel (SOLM) |
|
Description:
|
This specification defines a meta-model for representing
spacecraft operations procedures.
These procedures contain sequences of instructions to conduct
spacecraft operations, typically consisting of spacecraft commands and
spacecraft telemetry comparisons.
These procedures may also include the configuration of ground
equipment, configuration of spacecraft test equipment, execution of
ground testing, and execution of on-orbit testing.
Historically, these procedures have been captured in
flowcharts, text manuals, and a number of different scripting
languages used for ground station automation.
A standard meta-model to represent spacecraft operations
procedures will facilitate the transfer of procedures between the
spacecraft vendor and the spacecraft operator, as well as allow for
maintenance and transfer of the procedures across different ground
systems employed over the lifetime of the spacecraft. |
| Domain: |
Space |
| Latest / past specifications: |
|
Current version: 1.0
- Beta 1 |
Past versions: n/a |
|
| Specification Name: |
Surveillance
User Interface (SURV) |
| Description: |
Specifies
standard interfaces for a surveillance component, to be useful in Air
Traffic Control systems, constructed within an architecture that
enables the building of new surveillance processing systems. These
surveillance processing systems will interface with neighboring
surveillance processing systems.
|
| Domain: |
Transportation |
| Keywords: |
ARTAS,
ASTERIX, ATC, Field Extension Indicator, Field Reference Number, Field
Repetition Indicator, Field Specification System, Identification
Coder, ICAO, Radar Systems Specialist Panel, Radar Tracker And
Server, Scaling factor, System Area Code |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Related OMG Specifications: |
CORBA/IIOP |
| Related Industry Standards: |
Eurocontrol,
Radar Surveillance in En-Route Airspace and Major Terminal Areas ,
Edition 1.0 from March 1997, SUR.ET1.ST01.1000-STD-01-01 |
| Specification Name: |
SysML-Modelica
(SyM) |
| Description: |
The objective of this document is to
provide a bi-directional mapping between SysML and Modelica to
leverage the benefits from both languages. By
integrating SysML and Modelica, SysML's strength in descriptive
modeling can be combined with Modelica's DAE
solving capability to support analyses and trade studies. The scope of
this specification supports the objectives of
the bi-directional mapping, and includes the SysML4Modelica profile,
and the SysML-Modelica Transformation. Not all
Modelica constructs will be represented in this profile. The focus is
to include the Modelica language features that
are most common and together cover the majority of the Modelica models
in the standard library. When certain Modelica
constructs are omitted, this will be pointed out explicitly in this
document. In the future, it may be desirable to
introduce additional SysML constructs into the Modelica Language or
additional Modelica constructs in the SysML
language; however, this is outside the scope of the current effort. |
| Finalization
Information: |
|
| Specification Name: |
TACSIT
Controller Interface for CMS Systems |
| Description: |
The
TACSIT component is the software that provides users awareness of
entities in the operational space relative to a certain geo-spatial
context. |
| Finalization
Information: |
|
| Specification Name: |
Task
and Session (TSKSES) |
| Description: |
This
specification defines cooperative components that form a framework
representing the basic model for users of distributed systems. |
| Domain: |
cross-domain |
| Keywords: |
business
object, desktop, iterator, message, person, process, resource,
session, task, user, workspace |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Collection
Service, Life
Cycle Service, Naming
Service, Notification
Service, Property
Service, Transaction
Service |
| Related Industry Standards: |
|
| Specification Name: |
Telecom
Service & Access Subscription (TSAS) |
| Description: |
A
set of interfaces providing the domain facilities through which
network operators can offer third party enterprises secure access to
the capabilities of a network. Capabilities such as call control and
user location can be offered (through their own interfaces) or by
third party value-added services and solutions. |
| Domain: |
Telecommunications |
| Keywords: |
access
control, authentication, call control, cancel, discovery, end
user, SCM, service assess, Service Contract Management, service
provider, session, subscriber, subscription, user location |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG
Specifications: |
CORBA/IIOP |
| Specification Name: |
UML
Profile for Enterprise Application Integration (EAI) |
| Description: |
Provides a metadata
interchange standard for information about accessing application
interfaces. The goal is to simplify application integration by
standardizing application metadata for invoking and translating
application information. |
| OMG Cross Reference: |
UML
Profile Specifications |
| Specification Name: |
UML
Profile for Enterprise Distributed Object Computing (EDOC) |
| Description: |
The vision of the EDOC Profile
is to simplify the development of component based EDOC systems by means of
a modeling framework, based on UML 1.4 and conforming to the OMG Model
Driven Architecture. EDOC is composed of seven specifications:
(1) Enterprise Collaboration Architecture
(ECA); (2) Metamodel and UML Profile for Java and EJB; (3) Flow Composition Model
(FCM); (4) UML Profile for Patterns; (5) UML Profile for ECA; (6) UML Profile for Meta Object Facility;
and (7) UML Profile for Relationships
|
| OMG Cross Reference: |
UML
Profile Specifications |
| Specification Name: |
UML Profile
for Software Radio (also referred to as PIM & PSM for
Software Radio Components) |
| Description: |
This
specification supports the ability to develop waveforms, which
promotes the portability of waveforms across Software Defined Radios (SDR).
The terms Software Radio and Software Defined Radio are used to
describe radios that are implemented with strong emphasis on software.
|
| OMG Cross Reference: |
UML
Profile Specifications |
| Specification Name: |
UML
Profile for Voice |
| Description: |
This specification addresses the
standardization of dialog models used in voice-based applications in a
platform-independent way. More precisely, this RFP solicits proposals for
the following: (1.)
A MOF metamodel to describe platform independent concepts to
model voice dialogs; and (2.) A
UML profile to describe the usage of the UML notation when modeling voice
dialogs. |
| OMG Cross Reference: |
UML
Profile Specifications |
| Specification Name: |
Unified
Profile for the Dept. of Defense Architecture Framework (DoDAF) and
the Ministry of Defence Architecture Framework (MODAF) |
| Acronym |
UPDM |
| Description: |
This
specification defines a set of UML and optional SysML stereotypes and
model elements and associations. This specification documents the
language architecture in terms of the parts of UML 2 that are reused
and the extensions to UML 2 and SysML. The specification includes the
concrete syntax (notation) for the complete language. The reusable
protion of the UML 2 and SysML specification are not included directly
in the specification but are included by reference. The specification
also provides an example of how the language can be used to represent
a UPDM 2.0 architecture. |
| Domain: |
c4i |
| Latest / past specifications: |
|
Current version: 2.0 |
Past
versions 1.1 |
|
| Specification Name: |
Utility
Management Systems Data Access Facility (UMS) |
| Description: |
This
specification provides interfaces for obtaining the analysis data
(both inputs and results) from a UMS on a read-only basis. This
includes information describing a real or simulated state of the
system together with the system’s physical model data. |
| Domain: |
Manufacturing and Industrial
Systems |
| Keywords: |
data
access, data provider, Distribution Management System, DMS,
Energy Management System, EMS, EPRI CIM, power system, PLC, RDF, RTU,
SCADA, UMS, WQEMS |
| Latest / past specifications: |
|
| Contact Information: |
|
| Related OMG Specifications: |
CORBA/IIOP,
Data Acquisition from Industrial Systems, Event
Service, Historical Data Acquisition from
Industrial Systems, Naming
Service |
| Related Industry Standards: |
EPRI
Technical Report TR-106324; Resource Description Framework (RDF):
Model and Syntax Specification, Schema Specification; Uniform Resource
Identifiers (URI): Generic Syntax |
| Specification Name: |
Workflow
Management Facility |
| Description: |
Standard
interfaces for workflow execution control, monitoring, and
interoperability between workflows defined and managed independently
of each other. The interfaces are based on a model of workflow
objects, which includes their relationships and dependencies with
requesters, assignments, and resources. |
| OMG Cross Reference: |
Business
Modeling Specifications |
| Specification Name: |
XML
Telemet<<,,,ric and Command Exchange (XTCE) |
| Description: |
This is a
standard specification to define an information model for spacecraft
telemetry and commanding data. This specification is crucial to the
general standardization of the telemetry and commanding area. |
| Domain: |
Space |
| Keywords: |
Automated
Transfer Vehicle (ATV), Central Telemetry and Command Unit (CTCU),
health and safety, Launch and Early Orbit Phase (LEOP), Mission
Information Base (MIB), Portable Satellite Simulator (PSS), Packet
Utilization Standard (PUS), payload interfaces, Remote Telemetry and
Command Unit (RTCU), satellite, Spacecraft Thermal Vacuum (SCTV),
Spacecraft Control and Operations System (SCOS), Time Division
Multiplexing (TDM), XML Schema, X-Ray Multi Mirror (XMM) |
| Latest / past specifications: |
|
Current version: 1.1 |
Past versions: 1.0 |
|
| Contact Information: |
|
| Related Industry
Standards: |
CCSDS
102.0-B-4, CCSDS 203.0-B-1, ECSS-E-70-41, S2K-MCS-ICD-0001-TOS-GCI,
W3C XML Schema |
| Most recent IPR
and Implementation questionnaire responses: |
|
[ top ] [ Index
Page ]
|
|
