 | ManTIS
Manufacturing Technology &
Industrial Systems Task Force |  |
Adopted Technology
[Note: These pages are in transition as we update for new technology and integrate the technology listings of both the legacy Manufacturing and Utilities Task Forces, Larry L. Johnson, ManTIS Web Page Editor, 22-Oct-2003]
Index of Adopted Specifications
Introduction to OMG ManTIS Standards
Available Specifications are those that have emerged from a Finalization Task Force (FTF), or a Revision Task Force (RTF).
Recently Adopted Specifications are those that are in the process of being fine-tuned by a Finalization Task Force after having been approved successively by the Task Force, the Architecture Board, the Domain Technology Committee (DTC), and finally, the Board of Directors.
Overview of ManTIS Specifications
- OMG Documents:
- 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.
- Specification: formal/2003-03-63
- IDL: dtc/03-02-03
- OMG Documents:
- Description: Standard interfaces to Product Data Management systems, or other systems providing similar services, from other manufacturing software systems.
- Specification: formal/2000-11-11
- IDL: formal/2000-10-65
- UML: dtc/2000-10-02 (Rose Models)
The PDM Enablers Specification V1.3 is based on the revised, approved submission, mfg/1998-01-01, as modified by the Errata mfg/1998-02-01, the PDM Enablers V1.1 RTF Report, dtc/1999-02-01, the PDM Enablers V1.2 RTF Report, dtc/1999-10-02, and the PDM Enablers V1.3 RTF Report, dtc/2000-06-02.
(The original Request for Proposal can be found in mfg/1996-08-01)
The specification is organized as twelve IDL modules:
- PdmResponsibility
- PdmFoundation
- PdmFramework
- PdmBaseline
- PdmViews
- PdmDocumentManagement
- PdmProductStructureDefinition
- PdmEffectivity
- PdmChangeManagement
- PdmManufacturingImplementation
- PdmConfigurationManagement
- PdmSTEP
The PDM Enablers Specification is designed to meet the following requirements:
- Provide robust interfaces that enable the interoperability between PDM systems and a wide variety of other software systems.
- Provide a framework for PDM system interfaces that can be readily customized and extended by PDM technology providers, value added software suppliers, and end customers.
- Provide interfaces that are simple and general enough to be easily used in a broad range of applications, but are complex and specific enough to be meaningful and complete.
- Allow compliant interfaces to be built both on PDM systems with an OMA infrastructure and on existing non-OMA legacy PDM systems.
(Note V2.0 is Recently Adopted Technology and supercedes this technology)
- OMG Documents:
- Specification: formal/2000-12-01
- IDL: formal/2001-05-01
[Note: This IDL document replaces formal/2000-04-02 which was three files concatenated into one. This reference is to a zip file of the three files properly separated for compilation]
- UML: None Separately Available
This specification is the result of a DoD-wide effort, led by DMSO, to establish a common technical framework to facilitate the interoperability of all types of models and simulations among themselves and with command and control systems, as well as to facilitate the reuse of modeling and simulation components. This common technical framework includes the High Level Architecture (HLA). The HLA includes a software component, the Runtime Infrastructure (RTI), whose interface is the subject of this specification.
The RTI is a facility by which individual computer simulations or models may be federated to form a larger model or simulation system. The RTI interface is represented by two IDL interfaces, RTIambassador and FederateAmbassador. The first offers the services that a federate (individual constituent simulation) can invoke on the RTI. The second offers the services that the RTI invokes on a federate. A federate is a computer program or system that maintains a point of attachment to a Runtime Infrastructure.
The interface between each federate and the RTI may be described as a set of services. These services may be categorized by similarity of purpose or concern into six groups, as follows:
- federation management
- declaration management
- object management
- ownership management
- time management
- data distribution management
These groups have been defined to separate categories of function to the maximum extent possible. Thus, if a federation does not require the functions of data distribution management, the federates in that federation may use services in the other groups without reference to the data distribution management services. The mode of employment of services from one group is independent of the use of services from another group. However, the use of services from one group usually will affect the behavior of services from another. For instance, use of time management services to coordinate the advance of logical time across a federation will affect the behavior of object management services in the same federation. The semantics of these services will, in general, render impossible any attempt to implement groups of services separately. Thus the groups of services have not been allocated to separate interfaces.
Background: The ManTIS sponsored a Request for Comment (RFC) on behalf of the Simulation SIG (SimSIG) that proposed a standard for an architecture for federating simulation platforms. Called the High Level Architecture, or HLA, (see mfg/1998-02-05 for a brief overview or go here for a complete description), the RFC was based on work done by DoD's Defense Modeling and Simulation Office (DMSO). A vote to issue this RFC by the Domain Technical Committee occurred at its June, 1998 meeting. The RFC was adopted by the OMG thvough vote of its Board of Directors on 10 November 1998
Data Acquisition from Industrial Systems (DAIS) mfg/2000-11-03 (revised submission), mfg/2001-02-02 (errata)
- OMG Documents:
- 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.
- Specification: mfg/2001-09-03
- IDL: mfg/2001-01-04 [Note... this IDL is not listed in the OMG pages... Mfg editors are checking on this]
- UML: mfg/2001-01-04 [Note... this UML is a convenience document... Mfg editors are checking on its currency.
- OMG Documents:
- Specification: mfg/2001-10-01
- IDL: mfg/2001-10-02
- UML: [Note... no independent UML is listed... Mfg editors are checking its availability].
Revision History
Computer-Aided Design Services (CAD Services)
- Version 1.1
- Version 1.0
- OMG Documents:
- 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.
- Specificationformal/2002-10-02
- IDL: mfg/2001-01-04 [Note... this IDL is not listed in the OMG pages... Mfg editors are checking on this]
Product Data Management Enablers
- Version 1.3 -- The PDM Enablers V1.3 Revision Task Force submitted its Final Report at the Oslo meeting in June 2000. The Report was written as editing instructions agains the PDM V1.0 Convenience Document (below). The report was approved by the Board of Directors 12 September 2000 at their meeting in Burlingame CA USA.
- A Chapter for the CORBA Manufacturing Book for the PDM Enablers will be available soon. A draft of the formal document can be found in OMG Document mfg/2000-07-02
- PDM Enablers V1.3 Revision Task Force Final Report: dtc/2000-06-02
- PDM Enabler V1.3 IDL: dtc/2000-06-03
- PDM Enabler V1.3 UML (Rose Files) – These files are non-normative and are provided for convenience only: dtc/2000-10-02
- Version 1.2 -- The PDM Enablers V1.2 Revision Task Force submitted its Final Report at the Philadelphia meeting in Philadelphia in March 1999. The Report was written as editing instructions agains the PDM V1.0 Convenience Document (below). The report was approved by the Board of Directors 1 February 2000 by Email Vote.
- PDM Enablers V1.2 Revision Task Force Final Report: dtc/1999-10-02
- (There is no OMG Formal Document or Convenience Document)
- Version 1.1 -- The PDM Revision Task Force submitted its Final Report at the Philadelphia meeting in Philadelphia in March 1999. The Report was written as editing instructions agains the PDM V1.0 Convenience Document (below). The report was approved at the San Jose meeting, August 1999 and is now Adopted Technology.
- PDM Enablers V1.1 Revision Task Force Final Report: dtc/1999-02-01
- (There is no OMG Formal Document or Convenience Document)
- Version 1.0 -- The Joint Revised Submission together with the Errata were approved by the Architecture Board in Salt Lake City in Feb 1998. It subsequently passed DTC technology vote and was approved by the Board of Directors in Helsinki in August 1998.
This page was updated on 19 January 2004. Please send comments and suggestions to [email protected] by email. Last updated on: 11/09/2007