1 / 13

Automatic BOM Transformation for Unifying Engineering and Manufacturing Definitions

Streamline the process of transforming and maintaining BOMs with an automated solution, enabling efficient management of associative EBOM and MBOM definitions for manufacturing planning and execution. Maximize reuse and optimize global manufacturing strategies.

josier
Télécharger la présentation

Automatic BOM Transformation for Unifying Engineering and Manufacturing Definitions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BOM transformation working group:AUTOMATIC BOM TRANSFORMATION Jean-Claude Niyonkuru March 2019

  2. Unify ENG and MFG: Associative EBOM and MBOM Management Engineering Definition MFG Planning Definition Plant Specific Definition Plant Execution PLANT 1 PLANT 2 Global Manufacturing Strategy No Replication  Maximize Reuse  Optimization CAB is assembled by Plant 1 for Both Plant 1 and Plant 2 Manage only Plant Specific Definition Alt 002 Alt 001 ERP ERP MES MES Publish Manufacturing BOM Engineering BOM St 2 St 3 St 4 St 5 St 6 St 1 St 8 St 9 St 7 St 11 St 12 St 10 Equivalent Stock Publish St 2 St 3 St 4 St 5 St 6 St 1 Full Traceability

  3. GAP closure Automatic mBOM creation & maintenance mBOM manual maintenance Plant Attribute maintenance Performance ???

  4. Mass mBOM creation and extension • Plant Specific BOM using VSED (No new view iteration needed) • Reconciliation through huge structure.

  5. AUTOMATIC mBOM creation

  6. Automatic mbom creation & maintenance • Discuss feature intent • Discuss customer use cases • Prioritization • Discuss current PTC road map

  7. Feature intent • BUSINESS CHALENGE: The eBOMmBOM transformation and maintenance can become quickly cumbersome using a heavy tool like MAPSB. • In fact, 60% of the activities that the user needs to do are predictable • SOLUTION: Allow in MPMLink to define rules to help the user to create and maintain mBOM’s • BENEFITS: • User Efficiency • High quality data

  8. GENERATE DOWNSTREAM STRUCTURE • Automatic generation of downstream structure • Define rules to allow transfer and transform of items from an upstream to downstream structures based on rules. • OOTB rules are based on attributes/types of the parts or based on template from related Process Plan • Highly customizable transfer rules • Feature to be used for a node that don’t have any downstream structure AUTOMATIC

  9. step 1: Generate Downstream structure - Dataset PPlan1 eBOMroot (Design) mBOMroot (Mfg) OP11(Design) Part2 (Design) L120H_SB (Design) OP12(Design) CAssy1 (Design) Part3 (Design) Option1 (Design) On the OperationToPartLinkIBA “ParentName” = “Kit1” FG1 (Design) Part1 (Design) Sub-Ass2 (Design) PPlan2 Part2 (Design) OP21(Design) Part3 (Design) Raw1 (Design) FG2 (Design) On the OperationToOperatedOnPartLink “allocation type” = “blank” OP22(Design) Part3 (Design) Raw2 (Design) CAssy2 (Design) Option3 (Design)

  10. Step 1: Generate Downstream structure – expected result EQLink mBOMroot (Mfg) eBOMroot (Design) GDS=010 L120H_SB (Mfg) L120H_SB (Design) GDS=010 Option1 (Mfg) CAssy1 (Design) REM=yes FG1 Option1 (Design) Part1 (Design) FG1 (Design) REM=yes FG1 SubAssy2 (Mfg) Part1 (Design) AUA=Yes Part2 (Mfg) SubAssy2 (Design) AUA=Yes Raw1 (Design) Part2 (Design) OP12(Design) Raw2 (Design) Part3 (Design) “ParentName”=“Kit1” Kit1 (Mfg) FG2 (Design) REM=yes Part3 (Design) Part3 (Design) AUA=Yes FG2 Part3 (Design) CAssy2 (Design) REM=yes Option3 (Design) Option3 (Design)

  11. Step 2: Propagate upstream changes - DATASET L120H_SB (Design) GDS=010 2 CAssy1 (Design) REM=yes Change quantity Change assigned expression (usage) Add usage Remove usage 3 1 4 1 Option1 (Design) FG1 (Design) REM=yes Part1 (Design) AUA=Yes 2 SubAssy2 (Design) AUA=Yes 3 Part2 (Design) Part3 (Design) FG2 (Design) REM=yes Part3 (Design) AUA=Yes 4 FG3 (Design) REM=yes Part4 (Design) AUA=Yes 4 M120H_SB (Design) GDS=020 CAssy2 (Design) REM=yes CAssy3 (Design) REM=yes Option2 (Design) Option3 (Design)

  12. Step 2: Propagate upstream changes – expected result EQLink mBOMroot(Mfg) eBOMroot (Design) GDS=020 M120H_SB (Mfg) Option2 (Design) L120H_SB (Design) GDS=010 GDS=010 CAssy1 (Design) REM=yes L120H_SB (Mfg) Option1 (Design), RED FG1 (Design) REM=yes Option1 (Mfg), RED Part1 (Design) AUA=Yes FG1 Part1 (Design) SubAssy2 (Design) AUA=Yes, QTY=2 FG1 Part3 (Design) SubAssy2 (Mfg), QTY=2 FG2 (Design) REM=yes Kit1 (Mfg) Part3 (Design) AUA=Yes Part3 (Design) FG3 FG3 (Design) REM=yes Part4 (Design) Part4 (Design) AUA=Yes FG2 Part3 (Design) CAssy2 (Design) REM=yes Option3 (Design) Option3 (Design)

  13. Customer use cases for mbom automation • The rules should be extended to Process Plan. Rules maybe based on phantom Kit (in Solar this is an engineering Kit used as is and then children consumed in Process Plan)

More Related