21X Impact Analysis and Where Used Query and Export

Scott Casale

21X Impact Analysis and Where Used Query and Export

The Impact Analysis app offers impacts onto an item and the objects that are impacted by that item.

In 21x, Impact Analysis is considered a "deprecated app" although it still functions as a visual representation to present impacts (affected items, where used, etc.). In 21x, a warning, when opening the app, states to "use the Relations command instead." The Impact Analysis app functions as 19x does - only with the warning on opening.

  • The Impact Analysis app shows impacts for 3D Parts, Physical Products, Engineering Doc's, and etc. This functions similar to other PDM/PLM software Where Used functionality - only in a visual interface only.
    • Impact Analysis offers the ability to see an Items impacts but has no way to export to a spreadsheet or see as list.
  • The Relations app "command" offers a visual aid for parent children and various relations, similar to Impact Analysis app, but has no way to export to a spreadsheet or see as list.
    • The Relations App does not work for Engineering Documents such as tables which have items that use them for parameters. 
  1. What is the best way to query Where Used 3D Parts, Physical Products, Engineering Doc's, and etc, and export them to a spreadsheet or list? Is there a specific App Web or Native?
  2. If Impact Analysis is eventually going to go away as an app offering in future releases, how does one find the impacts (Where Used) of Engineering Documents?

 

Any assistance is appreciated in advance - I'm somewhat new to 3Dexperience and Catia but versed in many other CAD, PLM, and PDM software as admin and user.

Ryan Benyshek

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Scott Casale)

Relational explorer might be good enough to show how the impact of the item relates within the context of the data model. If you want to show the relations impact of the Relational explorer you might need to modify the search index config xml to show them and have the SXI index those relations and show them with a custom ontology. As for export of objects within the data model, you might need to look into the RGD (Report administrator) app to do the advanced queries. Worst case an MQL query of the database can definitely do the job.

Edited By:
Ryan Benyshek[Dassault Systemes.] @ May 15, 2022 - 02:40 PM (America/Central)

Scott Casale

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Ryan Benyshek)

Thank you, Ryan Benyshek.

I will look into the RGD app.

Michael George Craffey, IV

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Scott Casale)

Scott,

As Ryan mentioned, using Relational Explorer is a good option. I think your concern about deprecation of functionality is actually going to be an expansion of the "Relations" feature that appears in multiple interfaces. I included several screen grabs of different places/interfaces a user can see relations.

Thank you,

Michael Craffey
Razorleaf Corporation

Attachments

  • Relations_From_Object_View.jpg (199.8k)
  • Relations_From_Product_Finder_Native_Client.jpg (157.4k)
  • Relations_From_Search.jpg (195.4k)
  • Relations_From_Tools_Menu.jpg (185.8k)

Scott Casale

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Michael George Craffey, IV)

Hey Mike!

Good to hear from you.

Looking at this with 21x and a carry over from 19x, Engineering Documents do not present relational links in Relations or Relational Explorer.

 

Image attached.

Attachments

  • capture.png (47.2k)

Ryan Benyshek

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Scott Casale)

The Relations Explorer app has the ability to show Eng. Doc relations to physical products, as with the Specification Doc connection.  As for showing a relation in context of Design Table, that may be a bit trickier to get directly, you go through the 3DPart attached to the Physical Product. Maybe the best practice is to have the spec-doc connection built in context of the document since it is directly controlling the design definition of the part, nothing is directly enforcing this behavior though, and would need to be checked as a business rule.

Attachments

  • Relationship as Specification.png (4.6k)
  • REL-Eng Doc as Specification.png (40.2k)
  • REL-Explorer with Design Table.png (31.3k)
Edited By:
Ryan Benyshek[Dassault Systemes.] @ May 19, 2022 - 09:30 AM (America/Central)

Scott Casale

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Ryan Benyshek)

Understood.

The images you shared are of 22x, not 21x. At present Engineering Doc's do not display relations in 21x or in relation explorer 19x.

Ryan Benyshek

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Scott Casale)

I haven't checked in a 19x environment, I do see that the functionality for Knowledgeware search patterns ( specifically delivery of a function to show Design Table) was validated to be released in 2018xFD04 Not sure which 21xHF you're on, but this is working in a 21xHF10 server. Maybe you need to enable the "All Relations" dropdown after selecting the Customize relations icon in the relations explorer app, this should show any indexed relations if it doesn't, see if the "Knowledgeware" relations shows up for you while there.


 

Attachments

  • All Relations Dropdown.png (18.6k)
  • 21xHF10 Relations Explorer.png (151.2k)
  • Knowledgeware Relations.png (6.4k)
  • Customize Relations.png (4.6k)

Michael George Craffey, IV

RE: 21X Impact Analysis and Where Used Query and Export
(in response to Scott Casale)

Scott,

I'm pretty sure I was using 21x when I took those screen grabs. I will look at the 21x environment to see what you're seeing. Can you send me a document title to look for in Zoom?

Thanks,

Mike

 

Michael Craffey
Razorleaf Corporation