Dear ENOVIA users,
Thank you for joining us for the "ENOVIA to the MAX - Product Release Engineer and 3D Product Architect" webinar, and a big thanks to our two ENOVIA Portfolio Marketing experts and speakers: @ND and @RH.
Please find hereunder the LIVE webinar replay, Q&A (coming soon), and the link to access all the "ENOVIA to the MAX" on-demand webinar series.
🔁 Replay
💬 Q&A
1. If we do not have many CAD activities, then which Role is recommended?
Answer: We suggest to use the Product Release Engineer role (XEN) as it is not as closely tied to 3D geometry of the systems that generate it as is 3D Product Architect (PAU). XEN retains more of its value and capability in the process than PAU would with limited / no CAD.
2. Do we have EIN on MBOM side?
A. Yes, the MBOM EIN is the same attribute, but it could only be set manually for the moment. Further integration with the EIN that is set in the Engineering Item, in Product Release Engineer (XEN), is planned to be available in the near future.
3. When a document specification is added to a Physical Product, can I see it when I extract the BOM with XEN?
A: Not for the moment. The generation of a bundle containing the files associated the product structure will be available in the near future.
4. What application and role do you need to import/define core/cover material?
A: Core and Covering Materials can be created from various apps, for example SIMULIA Material Definition App (included in Mechanical Designer role (MDG), Raw Material can be created from BIOVIA Specification Manager (XSR), using the app “Specification Management”.
5. How to apply variants and options in product structure?
A: Model and Model Versions can be associated to the product structure, and effectivities can be applied on instances of this product structure either from Engineering Release app (XEN role) or from Product Structure Editor app (PAU role) if the Configuration Engineer (CFG) role is activated. Then the product structure could be filtered by Product Configuration in both Apps.
6. Is there a capability to assign EIN for the Physical Product's subtype created through TXO?
A: Yes.
7. Is there a capability to have different revision schemes for a different Physical Product's subtypes created through the TXO?
A: Not directly. You must use a custom attribute from which a value is different by subtype to do that.
8. In the duplicate functionality, will there be a revision as an action coming up for a non-configured structure?
A: Currently the options are limited to Duplicate, Reuse, Exclude and Duplicate with Drawings.
9. To create a new revision of the existing component in the duplicated structure?
A: This is outside of the Duplicate functionality. Subsequently, “Reuse” would be used on the particular component and a revise would then be made as a separate operation.
10. How to assign plants to make components?
A: You can move these components to the relevant collaborative space and organization, which presents their “Manufacturing responsibility."
11. Will there be corresponding MBOMs created per plant as it was in old ENOVIA ways of working?
A: Not as in the old way. The MBOMs corresponding to each plant are moved to the collaborative space/organization that represents this plant.
🔎 Can't Get Enough?
Access all the LIVE "ENOVIA to the MAX" webinars, now available on-demand, by clicking here.
