Thank you for the info. At 36:30 you mentioned instance attributes. Do you have a video that elaborate this? I have some issue where assert mass at sub assembly is not rolling up consistently. Thanks!
As I mentioned in the video, assertions at the individual component level are going to roll up easiest. Fundamentally, assembly-level component assertions are local to that specific subassembly, and will not roll up to higher levels. As a rule of thumb, if you want to create a clean assertion that will roll up to higher levels, always make the part or assembly for which you are asserting a value the "Displayed Part" (not just the Work Part... Use "Open in Window" to make sure it is the top-level part in the Assembly Navigator when you make the assertion.) Assertions created in this way will roll up beautifully, just as you expect. Does that help?
Thanks for sharing that presentation. Question about update part attributes. Does the tool have collaboration functionality between 2 people at the part level. Example one person is in charge of the geometry and the other person can update the mass property attributes but does not have access to modify the geometry.
Great question! Certainly when a group is working together on an assembly, an individual component may be owned (and open for editing) by one designer, while also being viewed (in read-only mode) by others at the same time. And yes, if the mass and inertial properties have not yet been stored with the saved part, the read-only "others" can certainly generate mass properties data if needed in the context of their work. Their changes will not be saved when they close the read-only parts, but they can certainly calculate mass rollups, for instance, without the need for full read/write access to all components at the same time. Hope that answers your question!
Heh heh... That's an interesting conclusion to draw from what I said... We certainly have thousands of large-scale customers collaborating around weight and balance today worldwide. :-) Thanks for stopping by!
Sorry I used the word collaboration but maybe that's not the exact word I need to use to explain my thoughts. Here's what I was thinking when I used the words "collaboration work". I was thinking more of a continuous improvement and live sharing system like those used in software development (Example: Visual Studio and the Github platform). This type of functionality implemented in CAD software could allow mass property updates by a manager or line manager through an automatic notification and automatic update process after approval by the 3D model owner.
@@lebeluet NX certainly does a lot of real-time change notification in the context of assemblies these days. Here's a good video to start you down that road: th-cam.com/video/sDopPt6RQ5w/w-d-xo.html
@jozehrovat3719 -- The optional Advanced Assemblies license, most easily accessible with Value-based Licensing (Design Tokens), lights up the Mass Properties Panel in the Assembly Navigator and Part Navigator, with tons of functionality including multiple assertion options, scaled inertial values when masses are asserted (so inertial properties are closer to reality), Center of Mass visualization options, immediate update without save for mass and inertial properties, mass reference set overrides, maturity-driven assembly rollup options, and much more. And with VBL, you can easily share the license as needed. Hope that helps!
![NX Assembly Mass Properties: Associative Point and CSYS at an Asserted Center of Mass [NX 2206]](http://i.ytimg.com/vi/zHMGabGhzkA/mqdefault.jpg)
![NX Assembly Mass Properties: Associative Point and CSYS at an Asserted Center of Mass [NX 2206]](/img/tr.png)
![NX Feature Templates: Using a Label to show a Warning Message [NX 2206]](/img/n.gif)
Thank you for the info. At 36:30 you mentioned instance attributes. Do you have a video that elaborate this? I have some issue where assert mass at sub assembly is not rolling up consistently. Thanks!
As I mentioned in the video, assertions at the individual component level are going to roll up easiest. Fundamentally, assembly-level component assertions are local to that specific subassembly, and will not roll up to higher levels. As a rule of thumb, if you want to create a clean assertion that will roll up to higher levels, always make the part or assembly for which you are asserting a value the "Displayed Part" (not just the Work Part... Use "Open in Window" to make sure it is the top-level part in the Assembly Navigator when you make the assertion.) Assertions created in this way will roll up beautifully, just as you expect. Does that help?
Thanks for sharing that presentation. Question about update part attributes. Does the tool have collaboration functionality between 2 people at the part level.
Example one person is in charge of the geometry and the other person can update the mass property attributes but does not have access to modify the geometry.
Great question! Certainly when a group is working together on an assembly, an individual component may be owned (and open for editing) by one designer, while also being viewed (in read-only mode) by others at the same time. And yes, if the mass and inertial properties have not yet been stored with the saved part, the read-only "others" can certainly generate mass properties data if needed in the context of their work. Their changes will not be saved when they close the read-only parts, but they can certainly calculate mass rollups, for instance, without the need for full read/write access to all components at the same time. Hope that answers your question!
Thanks. Your answer confirm that collaboration work is not there yet.
Heh heh... That's an interesting conclusion to draw from what I said... We certainly have thousands of large-scale customers collaborating around weight and balance today worldwide. :-)
Thanks for stopping by!
Sorry I used the word collaboration but maybe that's not the exact word I need to use to explain my thoughts.
Here's what I was thinking when I used the words "collaboration work".
I was thinking more of a continuous improvement and live sharing system like those used in software development (Example: Visual Studio and the Github platform).
This type of functionality implemented in CAD software could allow mass property updates by a manager or line manager through an automatic notification and automatic update process after approval by the 3D model owner.
@@lebeluet NX certainly does a lot of real-time change notification in the context of assemblies these days.
Here's a good video to start you down that road: th-cam.com/video/sDopPt6RQ5w/w-d-xo.html
This is great new capability. It is definitely easier and more functional than the old version.
Thanks, Rick!
Hello
Do you maybe know what licence do I need for this mass properties to work?
@jozehrovat3719 --
The optional Advanced Assemblies license, most easily accessible with Value-based Licensing (Design Tokens), lights up the Mass Properties Panel in the Assembly Navigator and Part Navigator, with tons of functionality including multiple assertion options, scaled inertial values when masses are asserted (so inertial properties are closer to reality), Center of Mass visualization options, immediate update without save for mass and inertial properties, mass reference set overrides, maturity-driven assembly rollup options, and much more. And with VBL, you can easily share the license as needed.
Hope that helps!