SLIDES PDE2004 Ungerer plm services

Product Lifecycle Management Services within OMG's Model Driven Architecture: 

Product Lifecycle Management Services within OMG's Model Driven Architecture Max Ungerer, Lutz Lämmer, PROSTEP AG

Contents: 

Contents The XPDI-group RFP requirements Technical content of the submission Next steps

The ProSTEP Organization: 

The ProSTEP Organization - Standardization ProSTEP - Organization und Implementation - Worldwide Cooperation Management (VDA, PDES,...) Responsible for: iViP e.V. - Market-Penetration - Product-Development - Service Solutions Responsible for:

The ProSTEP iViP Association: 

The ProSTEP iViP Association Implementor Forums Training Courses & Benchmarks

The XPDI working groupExtended Product Data Integration: 

The XPDI working group Extended Product Data Integration Established: Nov. 2001 Objectives: Harmonization of PDM standards/ Standardization of PDTnet approach Initial Members : Michael Feltes DaimlerChrysler AG Dr. Lutz Lämmer PROSTEP AG Uwe Kaufmann Fraunhofer IPK Dr. Sachers PROSTEP AG Dr. Max Ungerer PROSTEP AG Gerd Schumann Volkswagen AG Ronald Sander Volkswagen AG Matthias Zagel Eigner AG Erik Rieger PTC

XPDI Partners : 

XPDI Partners Sponsoring Partners Technology Partners 88solutions

Project organization: 

Project organization Industrial representative : Michael Feltes, DC Technical Review instance : XPDI-Working Group Project Review instance : iViP/ProSTEP-TSC Project contribution : PDM-IF 2004

Current Roadmap: 

Current Roadmap OMG deadlines PLM RFP issued 26.11.2002 DC LOI Deadline 02.04.2003 Initial submission Deadline 12.05.2003 Revised submission Deadline 27.10.2003 2nd Revised submission Deadline 12.01.2004 Project Milestones: Official project start 01.01.2003 OMG presentation 03.02.2004 AB review 26.04.2004

Reference documents: 

Reference documents RFP mantis/2002-10-01 Initial submissions DaimlerChrysler mantis/2003-06-03 88solutions mantis/2003-05-04 Revised submission mantis/2004-01-01, mantis/2004-04-01

Objective: 

Objective Extend and revise the PDM Enablers as a MDA specification Define a Platform Independent Reference Model for Product Lifecycle Services Linking that PIM with the STEP Information Model Supporting compatible implementations on multiple platforms Reducing complexity of client code in comparison with PDM Enablers V1 Allowing server implementations to attain improved performance over PDM Enablers V1

Problem Statement: 

Problem Statement PDM Enablers specification V1.3 was adopted Nov 2000, and requires a CORBA implementation Relationship to other information models, like STEP family of related standards, is informal and not explicitly defined Compatibility across multiple platforms (e.g. CORBA, SOAP-WebService, J2EE and others) is not in scope Convenient service interfaces to complex PLM functions are necessary Concepts missing in PDM Enablers V1 Bill of Material, Delta/Net Changes, Effectivity Propagation, Event/Notification/Query

Mandatory Requirements: 

Mandatory Requirements Modeling requirements Informational PIM based on STEP Computational PIM and at least one PSM Functional requirements Capability similar to PDM StepEnablers Flexible traversal and filter mechanism Generic query mechanism Handling of Bill of Material Non-Functional requirements Increased performance and reduced client complexity compared to PDM Enablers V1

Optional requirements: 

Optional requirements XML Schema PSM Effectivity management Convenience service for check-in / check-out Processing variable notes Service for search in design space Notification Relationship management and traversal

PLM Services as OMG MDA standard: 

STEP Part 14 (EXPRESS-X) data model/instance transformation executable mapping PLM Services as OMG MDA standard STEP Part 25 (EXPRESS2XMI) relates EXPRESS to UML PIM2PIM model refinement/enhancement XML Schema oriented PIM2PSM model projection using stereotypes … Use Cases, Queries PDM Enablers 1.3 …

Relationship to STEP AP214: 

Relationship to STEP AP214 STEP Part 14 (EXPRESS-X) data model/instance transformation executable mapping PDTnet Queries PDM Enablers 1.3 … PIM2PSM model projection using stereotypes … Model check shall result in equivalent representations STEP Part 28 (EXPRESS2XSD) relates AP214 ARM EXPRESS to XML Schemaby using the P28 configuration for AP214 ARM

PLM services usage scenario: 

OEM Supplier Online access (synchronous) Mass data exchange (STEP asynchronous) CMS LCA WT VPM IMAN PDM system System synchronisation PLM services PLM services CPI PDM system PLM services usage scenario

Considered Use Cases: 

Considered Use Cases Export and import of assembly data Authentication/start-up of session Authorization Start node identification Browsing of product structure data Download and upload of structure data Generic object query Search in design space Change notification Browsing configuration information Viewing of change management information

Subset definition of the STEP reference (1): 

Subset definition of the STEP reference (1) For the submission an extended subset of the AP214 ARM CC6 and CC8 was defined. This scope is a superset of STEP PDM Schema. The selection was driven by the following considerations: reducing the modeling elements, and grouping of these elements to reflect the units of functionality.

Subset definition of the STEP reference (2): 

Subset definition of the STEP reference (2) Product structure and Bill of Material primary objects used for product data management parts and the bill of material relationships between items for discrete manufacturing hierarchical product structures representing assemblies constituents of those assemblies corresponding to the traditional engineering and manufacturing bill of material indentured parts list

Subset definition of the STEP reference (3): 

Subset definition of the STEP reference (3) Document structure and properties handling of electronic documents comprising one or more files track documents that are not actively managed by the PLM system Shape Definition and Transformation handling of item shape definitions by representations given by documents and their absolute or relative positioning

Subset definition of the STEP reference (4): 

Subset definition of the STEP reference (4) Classification and Properties Defines Classification (hierarchies) and descriptions of PLM entities Authorization Defines approval and related person and organization information for PLM entities Configuration Management meet the requirements of enterprises that offer many possible configurations of their products for sale

Subset definition of the STEP reference (5): 

Subset definition of the STEP reference (5) Alias Identification mechanisms to identify PLM relevant item in other contexts, e.g. organizations Change and Work Management activity, project, and contract related information activities may be initiated by work requests and may be authorized by work orders

Subset definition of the STEP reference (6): 

Subset definition of the STEP reference (6) Process Planning process plans, versions of process plans with version tracking, process operations and properties of processes Multi-language support capability to represent descriptive information about objects in different languages

Normative UML PIM: 

Normative UML PIM Applying the ISO10303-25 part and the proposed extensions results in a normative UML PIM with the following modeling constructs: Classes and interfaces for EXPRESS entities and types Associations and compositions, both bi-directional and unidirectional for EXPRESS attributes whose domain is an EXPRESS named type Mapping of simple EXPRESS types like string, integer to the corresponding UML types

Part Identification: 

Part Identification

Part Structure BOM: 

Part Structure BOM

Document and File Management: 

Document and File Management

Shape Definition and Transformation: 

Shape Definition and Transformation

Approval: 

Approval

Configuration Management: 

Configuration Management

Computational PIM (1): 

Computational PIM (1) The computational viewpoint captures the functional aspects of the model described in the informational viewpoint It enriches the information model by functional elements, which support an effective and easy to use interface for handling the data-model

Computational PIM (2)PLM connector and PLM object: 

Computational PIM (2) PLM connector and PLM object Functional element PLM connector with PLM connection factory PLM resource adapter PLM object factory PLM container interface PLM query- and traversal mechanism

Computational PIM (3): 

Computational PIM (3) Queries and Traversal of Information Element Definition of queries according to the four main usage categories finding a specific data item up- and downward-browsing in product structures retrieving a sub data model adding information to the data model Conformance Points Optional: general query interfaces using XPath for navigation Mandatory: set of specialized queries, e.g. AssemblyStructureQuery returns a sub data model with several items and all assembly structure information elements StartNodeQuery is used to get a starting point for further queries and returns a list of items found by evaluation of XPath expressions

Computational PIM (4): 

Computational PIM (4) Services as defined in the OMG PDM Enablers V1.3. Services for flexible traversal and filter mechanisms. Services for query capability for PLM systems. Services for handling Bill of Material (BOM). Services supporting increased performance and reduced client complexity with respect to OMG PDM Enablers V1.3. Services for simple relationship navigation and management of PLM data elements[6.6.1.6].

Example PSM for XML (1): 

Example PSM for XML (1) Definition of a projection of the normative UML PIM into the platform specific model (PSM) with an execution infrastructure given by XML To enrich the normative UML PIM an UML profile for XML schema is used An UML profile consists of three key items namely stereotypes, tagged value called properties, and constraints. In Query interfaces LocationPath maps to XPath expressions Connection interface maps to a set of SOAP messages forming the WebService interface

Example PSM for XML (2): 

Example PSM for XML (2) Insufficiencies No type-safety of reference IDREF(S) are elements and not attributes (not W3C-conform) No multiple inheritance is supported Elements have to be in a certain order Problems by exchanging partial models (e.g. using SOAP) References are not valid /NULL is not allowed as IDREF(S) a kind of place marker or null-reference would be useful

Example PSM for XML (3) Comparison of 10303-25/10303-28: 

Example PSM for XML (3) Comparison of 10303-25/10303-28

Next Steps: 

Next Steps Using the ProSTEP iViP working structure to leverage reference implementations web service demonstrator Setup of a test environment and infrastructure information events for IT partners

OpenPDM Migration: 

OpenPDM Migration

Open tasks: 

Open tasks Consideration of optional functional requirements mentioned in the RFP Mapping to other PSM like J2EE, CORBA