Planned use of PDM and Configuration Management data ... · Planned use of PDM and Configuration...

Planned use of PDM and Configuration Management data exchange based on STEP AP242


Frédéric Darre (Cimpa obo Airbus)& Jean-François Cugy (Dassault Aviation


Table of content

June 5 & 6, 2019 (Paris) – [email protected] - http://standardizationday.afnet.fr/ - ‹13›

• Summary of main business requirements and challenges• Remind of AP242 capabilities for PDM - CM interoperability• Summary of STEP AP242 PDM Recommended Practices • Illustration of the AP242 data model for the “As designed”, “As Planned”

and “As Built” product structures • Harmonization of AP242 ed2 and AP239 ed3 for PDM & R,V&V• Overview of AP242 COTS interfaces capabilities for PDM exchange• Preparation of 2019 benchmark of AP242 PDM COTS interfaces• Planned use of PDM data exchange based on STEP AP242

by Airbus and Dassault Aviation• Summary - next actions


Summary of main business requirements and challenges

nCommunication of PDM data for development and manufacturingn Communication of PDM data with the supply chains in case of

heterogeneous PDM systems (Equipement manufacturers …)nCommunication between PDM systems and ERPnMigration of legacy PDM system to new COTS PDM systemnLong Term Archiving of Configured PDM product structure and

metadata.



Benefits to use STEP AP242 standard for PDM – CM data exchange


OEM-1PDM system Aparametrized

Supplier 1PDM system B

Use of specific / proprietary formats

Supplier 2PDM system C

Supplier nPDM system D...

Specificconverterformat A

In case of heterogeneous PDM systems between OEMs and Suppliers, benefits for the OEMs – Suppliers ecosystem to agree on common PDM data exchange standard



Cost of development of PDM data exchange interfaces with OEM 1 multiplied by the number of its suppliers

Use of international standardized formatsOEM-1

PDM system Aparametrized

Supplier 1PDM system B

Supplier 2PDM system C

Supplier nPDM system D...

PDM system Eparametrized

OEM-2

ISO Standard format(with possible parametrizations)

Cost of development of AP242 PDM data exchangeinterfaces optimized for the OEMs and their Suppliers

PDM system Eparametrized

OEM-2

Specificconverterformat E




Remind of AP242 capabilities for PDM - CM interoperability


nOverview of PDM product structure with Configuration Management


Remind of AP242 capabilities for PDM - CM interoperability


nProduct Specification and Configuration nEffectivity mechanism

Generic data model describes:- Product line- Options- Combination of options- Configuration- Different types of effectivities

(date, serial numbers …)


Summary of STEP AP242 PDM Recommended Practices

nRecommended Practices for STEP AP242 XML Product & Assembly Structure§ Joint Publication with CAx-IF and JT-IF§ Version 1.2 (June 30, 2017) for AP242 IS (2014)§ Version 2.0 (October 30, 2018) for AP242 TC (2016)

• Internal draft for all Implementor Forums• Special chapter outlining implementation changes from AP242 IS to AP242 TC• Special chapter for transfer of customized PDM data• Publicly available on PDM-IF and CAx-IF Homepages

nRecommended Practices for STEP AP242 XML Configuration Management§ PDM-IF specific document§ Version 0.7 (October 10, 2018) ongoing development

• Configuration Management (product specification)• Effectivities specification (serial number, date, conditions)

§ Plan to publish as version 1.0 in 2019



Summary of STEP AP242 PDM Recommended Practices


Table of contents1 Introduction2 Scope3 Reference to Recommended Practices4 Basic Concepts5 Part Identification and Classification6 Part Properties7 Part Structure and Relationships8 Document Identification and Classification9 External Files10 Document and File Properties11 Document and File Association to Product Data12 PDM Properties and CAD User-Defined Attributes13 Validation Properties14 Exchange of Customized PDM Information15 CAx-PDM Compatibility Guide16 Outlook17 List of TemplatesAnnex A XML Schema derivation from BO Model EXPRESS SchemaAnnex B Known IssuesAnnex C Reference DocumentsAnnex D Conversion from implicitly to explicitly defined transformationAnnex E Recommendation for the Definition of UnitsAnnex F AP214 AIM to AP242 BOM Mapping


Illustration of the AP242 data model for the “As designed”, “As Planned” and “As Built” product structures


As designed As planned As built

PO PO

As planned intermediate node

Include deviations

DeviationsAs built intermediate node

Associations (Realization)Associations(Planned)

inputsoutput

Process OperationPO As built node including deviations

Assembly node or leaf part

Business need to keep the traceability between the different views including potential deviations.


Illustration of the AP242 data model for the “As designed”, “As Planned” and “As Built” product structures


Individual part structurePart structure

Part

PartVersion

PartView

Individual part structure

IndividualPartOr Part

IndividualPart

Version

IndividualPartView

Product Structure« As planned »

PlannedIndividual

Part

IndividualPart

IndividualPart

Version

IndividualPartView

RealizedIndividual

Part

Product Planned

To Realized

PartViewTo

IndividualPartViewAssociation

PartViewTo

IndividualPartViewAssociation

Product Structure« As designed »

Product Structure« As built »

ViewContext”As designed”

ViewContext”As built”

ViewContext”As planned”

The STEP AP242 data model allow the representation of the VIRTUAL product and the LINKS to the representation of the PHYSICAL product. (Process operation sequence are not represented)

To be identified via Use Cases with Recommended

Practices

PartVersionTo

IndividualPartVersionAssociation

PartTo

IndividualPartAssociation


Remind of AP242 capabilities for Process Operation


Process Plan

Manufacturing or control operation

Manufacturing planning

ProcessOperation

OccurrenceProcess

Plan

ProcessOperationResource

Assignment

ProcessOperation

InputOrOutput

ProcessOperationDefinition

ProcessPlan

Relationship

Part structure

Part

PartVersion

PartView

Produced Outputs

[]

Example: 'stamping', 'milling', 'drilling', 'welding', 'casting', and 'painting'

ProcessOperationDefinition

Relationship

Example: 'decomposition‘'exclusiveness‘'sequence‘'simultaneity'

ProcessOperation

OccurrenceRelationship

Example: 'alternative' 'substitution' 'version association' 'version sequence'

Example: 'alternative' 'version association' 'version sequence'

Operation

ShapeElement

ConcernedShapes

[]

The list of objects affected by the operation occurrence

Input or ouptut ElementAssemblyOccurrenceRelationship,AssemblyViewRelationship,Occurrence,PartVersion

AssignedTo Ressource / ToolBreakdownElement,IndividualPartView,Occurrence,PartVersion,RequirementView


Harmonization of AP242 ed2 and AP239 ed3


Requirement Management, V&V

Work Management

Product Specification and Configuration

Product Data Management

Process Plan

Mating

Material

Kinematics

Individual Part

Document Management

Composite Structural Shape and Structure

Common resources Incl.: Classification, Date & Time

Effectivity, Property, Condition, State,

Identification, name & description

Breakdown

Activity

Shape Association and Structure

Electrical Harness

3D geometry

Area of harmonizationbetween AP239 ed3 and AP242 ed2

AP242 ed2 specific capabilities

Message

Management resourcesIncl.: Person, organization and

Address, Approval/Certification, Information rights, Contract and

project

Planned and evaluated characteristics

Representation and external element reference

Probability

Risk

Slot

Interface

Planning, scheduling

Task description

Observation

Resources

Analysis

Delta change

AP239 ed3 specific capabilities

Target: harmonization of AP242 ed2 – AP239 ed3 for PDM – CM finalized in Q3 2019


Harmonization of AP242 ed2 and AP239 ed3 for PDM & Requirements, Validation & Verification


Verification & Validation

Requirement Management

Properties

Requirement satisfaction

Requirement identification

Requirement source

Requirement

Requirement Version

RequirementView

RequirementVersion

Relationship

RequirementView

Relationship

Requirement Tracing

Relationship

Requirement Collection

Relationship

Requirement Decomposition

Relationship

Requirement Satisfaction

Assertion

Requirement assignment

Date and Person who assert

DateAndPersonOrganizationProperty

Value

Property based requirement

Text based requirement

ValueWithUnit

StringValue

ValueList

ValueSet

[]

[]

Requirement Assignment

RequirementRelationship

Requirement Source

Example:ActivityMethod,Breakdown,Document,IndividualPart,Part,ProductConfiguration,Project,Requirement,WorkRequest

Example:Activity,ActivityMethod,,Breakdown,Document, IndividualPart, Organization,Part, PersonInOrganization,Project,Requirement

Evidence

Verification

Verified byVerifies

Verification Relationship

Validation

Validated byActivityMethod,OrganizationOrPersonInOrganizationAssignment,PartVersion,StateDefinition

[]

Validates

[]

Analysis Model

State Observed

State Observed

Evaluation Result

Evaluation Status

[]Evidence Select

…

Evaluated Requirement

Analysed charac.

Evaluated charac.


Preparation of 2019 AFNeT – prostep ivip benchmark of AP242 PDM COTS interfaces

n Scope of the Benchmark N°3§ PDM

• NEST: PDM Assembly with 3D Geometry represented with nested files• TC “multi-id /multi-language”

§ CAD• 3D PMI Semantic Part Level and/or 3D PMI Semantic & Graphic Part Level• 3D PMI Graphic Assembly Level (if implementation level allows)

n Schema: AP242 Ed1 BOM XSD TC1n Reference Recommended Practices Documents:

§ Assembly Structure TC v2.0 (October 2018)§ Configuration Management TC v0.7+§ Semantic and Graphic PMI

n Participants§ CoreTechnologie, Dassault Systèmes, Datakit, Elysium, PROSTEP AG, PTC, T-Systems (other to be confirmed).

n Planning§ PDM and CAD test cases will be defined before 2019 summer break§ Test phase planned to start after 2019 summer break



Overview of AP242 COTS interfaces capabilities for PDM exchange


Major PDM systems have several COTS AP242 interfaces for PDM “As designed” data exchange, either developed by their editors or by third party integrators


Planned use of PDM data exchange based on STEP AP242 by Airbus and Dassault Aviation

nPrinciple: 3D Experience technical compatibility with STEP AP242nLong Term ArchivingnHeterogeneous exchange for general usagenSpecific Aircraft program deployment in case by case usage



Summary / next actions

nOn going actions with the PDM-IF to develop new use cases and get support by PDM editors

nOn going actions with PLM Action Group related to standardsnInputs for internal 3D Experience deployment for Airbus and Dassault Aviation



Thank you!


Planned use of PDM and Configuration Management data ... · Planned use of PDM and Configuration...

Documents

Transcript of Planned use of PDM and Configuration Management data ... · Planned use of PDM and Configuration...