1. Presentation of the PDM Implementor Forum activities
By Frederic Darre CIMPA, AFNeT technical coordinator of the PDM IF Implementer Group

2. AFNeT Standardization Days 2016 - Paris
Table of content
General Objectives of the PDM-IF
Available web site to access to PDM-IF information
PDM-IF: Project Organization
PDM-IF: Consortium
PDM-IF Kick-Off Meeting September 29, 2015; Paris
PDM-IF User Group 2016: Documentation of Use Cases
AP242 BO Model XML Recommended Practices
PDM-IF (IG) 2016 – Test Round 1: Scope & Test Case
AFNeT Standardization Days Paris
March 23, 2016

3. General Objectives of the PDM-IF
Speed up PDM interoperability within and between companies, based on ISO PDM standards
Between different PDM systems, between PDM and ERP, …
OEMs  1st Tier suppliers, SMEs  SMEs, etc.
Covering the full product life cycle
Develop agreed STEP PDM Rec. Practices to increase the efficiency of interoperability (processes, use cases, information) with increased quality, and cost and time reduction
Common platform for testing PDM interoperability functionalities
according to international PDM recommended practices
Interoperability Tests rounds between COTS PDM STEP interfaces of PDM vendors and integrators
Makes the STEP PDM interoperability standards useable and quicker to implement worldwide
Decrease the complexity and costs of implementation
AFNeT Standardization Days Paris
March 23, 2016

4. Available web site to access to PDM-IF information
Summary of PDM IF White Paper on ASD SSG public web site 
PDM-IF public web site 
AFNeT Standardization Days Paris
March 23, 2016

5. PDM-IF: Project Organization
AFNeT Standardization Days Paris
March 23, 2016

6. PDM-IF: Project Structure
User Group
Defines Use Cases
Derives requirements
For PDM standards
For Implementations based on these
Describe Best Practices
Enables expert discussions in trusted environment
Defines Roadmap
Implementor Group
Reviews Use Cases
Defines Recommended Practices
Enables expert discussions in trusted environment
Conducts Test Rounds to improve PDM data exchange quality
Provides feedback to standardization activities
AFNeT Standardization Days Paris
March 23, 2016

7. AFNeT Standardization Days 2016 - Paris
PDM-IF: Consortium
ProSTEP iViP
AFNeT
Confirmed:
Beta CAE
Daimler
LOTAR
PROSTEP
T-Systems
Candidates:
Autodesk
BMW
Siemens PLM
Volkswagen
Confirmed:
Airbus Group
Boost Conseil
CT CoreTechnologie
Daher
Dassault Aviation
Dassault Systèmes
GIFAS
Jotne EPM
Liebherr
MBDA
MSC Software
PFA
PTC
Zodiac
Candiates:
Elysium
Safran
Thales
Both hosting organizations are in contact with further potential project members
AFNeT Standardization Days Paris
March 23, 2016

8. PDM-IF Kick-Off Meeting September 29, 2015; Paris
30 Attendees from 17 Companies
Joint Sessions of Implementor Group (IG) and User Group (UG) at start and end of meeting
Separate sessions of IG and UG in between, to work on the respective topics and schedules
Successful transition from “planning / setup mode” to “working mode”, with agreed tasks and dates for the next months
Agreed meeting mode:
IG and UG will meet usually independently, as required by the respective work plans, with one joint meeting per year
Meetings will alternate between Paris (hosted by AFNeT) and Darmstadt (hosted by ProSTEP iViP)
AFNeT Standardization Days Paris
March 23, 2016

9. PDM-IF Work Plan & Schedule 2016
Use case A: Explicitly Configured “as designed” PDM product structure exchanges as single AP242 BO Model XML file referencing 3D CAD models
Use case B: Explicitly Configured “as designed” PDM product structure exchanges as single AP242 BO Model XML file referencing documents
Use case C: Explicitly Configured “as designed” PDM product structure exchanges as fully shattered AP242 BO Model XML file referencing 3D CAD models (in STEP or other CAD format) with validation properties in XML.
2015
2016
2017 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Test methodology
Model Use case A
Preliminary Rec. Pract. A
Test round 1
Update Rec. Pract.
Test round 2
Agree Use case Set A
Final Rec. Pract. A
Update Rec. Pract.
Test round 3
Agree Use case B
Model Use case B
Preliminary Rec. Pract. B
Joint Meeting
Sept.
UG Meeting
June.
Joint Meeting
Dec.
ISO USA
meeting
ISO JP
meeting
ISO
meeting
ISO
meeting
AFNeT Standardization Days Paris
March 23, 2016

10. PDM-IF User Group 2016: Documentation of Use Cases
Use cases provided by member will be modeled in a formal manner
Will lead to well-documented traceable requirements
Using the open “Archimate” enterprise modeling language
The Business Layer describes the general process steps and the involved stakeholders
The Application Layer defines how the information needed to support the process is mapped into the PDM Systems and the AP242 Business Object Model
The Infrastructure Layer will define particular testing requirements where needed.
AFNeT Standardization Days Paris
March 23, 2016

11. AP242 BO Model XML Recommended Practices
Business Object Model XML is a new implementation format for STEP, introduced with AP242 and AP209, aimed in particular at data management systems
Though a standard needs to be precise, it also needs to provide some flexibility through generic patterns and alternative representations
Otherwise, each new requirement would lead to a change of the standard
Recommended Practices are bridging this gap: they define how to apply these patterns to support particular capabilities
The core scope in focus is:
Basic PDM Subset (Part, Part Version, Part View, Document)
Assembly Structure with External References
Validation Properties
AFNeT Standardization Days Paris
March 23, 2016

12. AP242 BO Model XML RP - Document History
May 5, 2014: Start of Work
June 18, 2014: First Review Version (v0.8)
August 12, 2014: Second Review Version (v0.12)
November 14, 2014: Final Draft (v0.90)
February 24, 2015: Initial Release (v1.00)
Since summer 2015, work was restarted to incorporate feedback received from vendors, users and testing activities
Release of updated version 1.1 for AP242-IS anticipated around End of March 2016
Release of version 1.2, documenting the changes introduced by the upcoming Technical Corrigendum of AP242, planned for summer 2016
AFNeT Standardization Days Paris
March 23, 2016

13. AP242 BO Model XML RP - Table of Contents
Introduction
Scope
Reference to Recommended Practices
Basic Concepts
Part Identification and Classification
Part Properties
Part Structure and Relationships
Document Identification and Classification
External Files
Document and File Properties
Document and File Association to Product Data
User-Defined Attributes
Validation Properties
Outlook
List of Templates
Annex
AFNeT Standardization Days Paris
March 23, 2016

14. AP242 BO Model XML RP – A look inside
For any given construct, defines:
Entity relations
Attribute definition
Attribute population
Exchange recommendations
In addition, XML File excerpts are given as well:
AFNeT Standardization Days Paris
March 23, 2016

15. PDM-IF (IG) 2016 – Test Round 1: Scope & Test Case
Test Round 1 = PDM-IF “Use Case A”
Assembly Structure + Properties in one AP242 BO Model XML file
Geometry: in a format that can be opened by all participants to verify positioning and completeness, based on well-known “AS1” model
Specified additional PDM information
Management of a document for each referenced file
Chapter 8 in the recommended practices
With Version and Classification
Assignment from a part o a document
Chapter 11.2 in the recommended practices
Creation date / update date
Chapter in the Recommended Practices
Management of person with identified role like ‘creator’ or ‘editor’
Chapter in the Recommended Practices
AFNeT Standardization Days Paris
March 23, 2016

16. PDM-IF (IG) – Test Round 1: Test Methodology
PDM Sys. A
PDM Sys. B
Test Suite
Sample XML
PDM-IF
Test
Env.
Data
creation
Export modified
Export
Validation
Release
Import Data
Report Results
Manage Changes 1 2 3 4 5 6 7
Testing is done in a distributed manner by the PDM-IF IG members
Test environment on the PDM-IF web site serves as central data hub for test files and results
Added value compared to previous AP242 XML tests in CAx-IF and JT-IF:
Management of PDM-specific attributes
Change Management
AFNeT Standardization Days Paris
March 23, 2016

17. PDM-IF (IG) – Test Round 1: Schedule
Start with three rounds per year, aligned with proposed Work Plan
Test Round 1: Beginning of February – May 2016
Test Round Kick-Off: February 3 at ProSTEP iViP, Darmstadt, Germany
Test Round Review: May 11 at AFNeT, Paris, France
Conference Calls every two weeks
High frequency in order to support all participants in the new environment
Further workshops in 2016:
Early September (Round 2 Review)
Late November / Early December (Round 3 Review, joint meeting with UG)
AFNeT Standardization Days Paris
March 23, 2016

18. AFNeT Standardization Days 2016 - Paris
Summary – next actions
Launch of the PDM IF in Sept. 2015, hosted by AFNeT and ProSTEP iViP
Joint PDM IF User Group and Implementer Group on the 29th of Sept. 2016
1st version of STEP AP242 e1 BO Model XML Assembly Structure Recommended Practices
Successful start of the 1st test round of the 2016 schedule
Planned joint meeting of the PDM IF User Group and Implementer Group in December 2016 (Darmstadt)
Start of preparation of the PDM IF work plan for 2017 in Q3 2016
On going actions to gather new participants (industries and vendors)
Definition and prioritization of PDM interoperability use cases for 2017
AFNeT Standardization Days Paris
March 23, 2016

19. AFNeT Standardization Days 2016 - Paris
Contact information
Jean Brangé
AFNeT
Steven Vettermann
ProSTEP iViP
AFNeT Standardization Days Paris
March 23, 2016

20. AFNeT Standardization Days 2016 - Paris
BACKUP
AFNeT Standardization Days Paris
March 23, 2016

21. PDM-IF (UG) – Presented Use Cases
Dassault Aviation: Airframe Data Exchange using Data packages with many Industrial Partners, in charge of Production
Daimler: GET: Collaborative Workspace
Volkswagen: Support "Collaboration OEM-OEM and OEM-Joint Venture"
PSA: Business cases OEM-OEM , OEM-Design Partner , OEM-suppliers
Airbus: Improved Data Exchange between Airbus and Airbus Helicopters
ProSTEP iViP: futuristic insight: Synced Factory Twins
AFNeT Standardization Days Paris
March 23, 2016

22. AFNeT Standardization Days 2016 - Paris
Derived Use Cases based on AP242 PDM exchanges, Agreed between IG and UG
Use Case A:
Explicitly Configured “as designed” PDM product structure exchanges as single AP242 BO Model XML file referencing 3D CAD models
Including validation properties in XML;
Use Case B:
Explicitly Configured “as designed” PDM product structure exchanges as single AP242 BO Model XML file referencing documents;
Use Case C:
Explicitly Configured “as designed” PDM product structure exchanges as fully shattered AP242 BO Model XML file referencing 3D CAD models
AFNeT Standardization Days Paris
March 23, 2016

23. AFNeT Standardization Days 2016 - Paris
Assembly Structure Recommendation - Example Simple vs. Full Positioning Representation
Whenever the subsequent node does NOT contain a geometric model (i.e. it is a sub- assembly)  use Simplified Positioning Rep.
Whenever the subsequent node DOES contain a geometric model (i.e. it is a component part)  use Full Positioning Represent.
Implicit Item-based Transformation; preferred by CAD systems
Explicit Transformation Matrix; preferred by PDM systems
Same Coordinate Space; not recommended to be used. P F S
AP242 BO
Model XML P P S G F P P F F P P G G G
AFNeT Standardization Days Paris
March 23, 2016