Object Management Group
Manufacturing Technology a
Industrial Systems Task Force
MantisLogo

Model Driven Architecture
in Manufacturing & Industrial Systems


Index


Organization

"MDA in Manufacturing" was initiated in Anaheim as an ManTIS Plenary Project

Charter

Model Driven Architecture in Manufacturing Discussion
The ManTIS will be formulating its framework for MDA over the Yokohama and Orlando meetings (April June 2002). We will begin our new RFPs from the Roadmap in Orlando. Among the goals of the ManTIS MDA Framework are:

Work group co-chairs

To date this work is being done in plenary under the ManTIS chairs. When it is time for spin-off tasks, this may become a working group and chairs will be elected.

Contact information

The MDA discussion is being held on the Manufacturing mail list, mailto:mantis@omg.org


New!

21 October 2002


Current work

Current Discussion Paper:  Revision 20020608, mfg/2002-06-01


Model Driven Architecture Discussion

Helsinki, October 2002

In a Monday PPE Working Group Breakout the MfgDTF Model Driven Architecture Framework whitepaper draft (mfg/2002-09-03) was reviewed. Larry Johnson went over the recommendations, summarizing the discussion. An updated whitepaper will be drafted for the Washington DC meeting, where we hope to issue the paper.

Orlando, July 2002

MDA Discussion Breakout

Principal Discussion Participants:

It was proposed that the MDA whitepaper should become [part of] the new charter of the ManTIS describing what we do and how we coordinate with other standards groups such as ISO & IEEE

Liaisons:

A possible task would be to take all of the ISO STEP standards and make an operational interface standard and then bring the interface standard back to STEP. This would lead to a harmonized suite of standards.

Define a reference model that aligns well with STEP information models. In the OMG, create a reference model to map between the two.

From these reference models, we would like to scope out of the reference models the pieces necessary to execute one or more end-to-end use cases. An example of this is the usage of a PDM system by a CAD system in the context of design tasks.

The first RFP should be narrowed.

Versioning: PIMs -> PSMs -> Product vZ. As versions of the PIM progress, there needs to be traceability of what elements were used in the old PIM so that a decision can be made as to whether to ripple that into the project.

We will need to make recommendations to the appropriate group about the version control and usage mapping across PIM/PSM/Application models. And we will need to do at least an absolute minimum of this as necessary to manage the ManTIS models themselves until someone comes up with the more general pattern/solution.

Candidates:

There was considerable discussion of what the OMG Mechanism for a coordinating reference model could be:

MDA, EXPRESS, And EXPRESS-X to the Cross Domain Working Group meeting

David Price of Eurostep Group, AB delivered a presentation on MDA, EXPRESS, And EXPRESS-X to the Cross Domain Working Group meeting on Sunday, 23 June 2002. The presentation can be found at ormsc/2002-06-01

Yokohama, April 2002 (exerpted from minutes)

All future ManTIS RFPs will be done under the OMG's Model Driven Architecture (MDA). A significant amount of time was therefore devoted during the ManTIS plenary sessions to discussions about MDA as it is applied to the manufacturing domain. A white paper titled “ManTIS MDA Framework” will be written in which the results of discussion from Dublin, Anaheim and Yokohama will be consolidated as a starting draft. The following bullets summarize the main points and observations from the discussion held in Yokohama.

PDM Enablers V2.0 RFP to be Recast as MDA RFP’s

The first MDA RFP the ManTIS will issue will be for a Product Information Model Platform Independent Model (PIM2), which will be a superset reference model to be used for PDM Enablers and other platform specific PDM related implementations. The RFP will call for the PIM to make the relationship to STEP AP214 and STEP PDM Schema part of the standard, and to specify an XML PSM.

There is some debate about how to make the relationship to STEP AP214 and STEP PDM part of the standard. Lutz Lämmer suggests UML profile. David Price suggests Part 25 mapping EXPRESS into UML. That is, the mapping would be made by feeding the PDM Module Suite ARM into Part 25, thereby deriving the UML as a PSM. The mapping between that UML PSM to the PDM PIM would be the mapping we were going to do as a follow up to the STEP/OMG Harmonization white paper. It was noted that the STEP ARMs could be viewed as PSMs or PIMs in OMG depending on how one looks at them. Given the STEP flavor, they should probably be regarded as PSMs in the OMG.

The problem statement for the RFP is essentially taken from PDM Enablers V2.0, with the addition of mappings to other STEP family of related standards. The RFP calls for the explicit mapping that is normative. As it stands, there is difficulty in identifying the harmonized common subset of both standards, and resolving the unnecessary burden for implementations that need both capabilities (i.e., data access via interfaces and data exchange via STEP). Beyond STEP, there will be the capability to map to other technologies. This helps answer the questions customers have on preserving their investment across emerging and changing technologies.

To summarize, the RFP is basically recasting the PDM Enablers V2.0 RFP as an MDA RFP, suggesting a “scrubbed” UML model for the PIM. The PSM that is being requested is an XML binding that is Part 28 compliant. The “Part 28” model of the AP214 CC8 is suggested. The controversy is that this results in a different XML DTD from the one based on the AIM.


Past activities

None.


Return to ManTIS home


This page was updated on 21 October 2002. Please send comments and suggestions to mantis@omg.org by email.

Last updated on: 11/09/2007