I have NEVER understood View Representations and I guess after 15 years I still need help.

I have NEVER understood View Representations and I guess after 15 years I still need help.

jeanchile
Advisor Advisor
828 Views
7 Replies
Message 1 of 8

I have NEVER understood View Representations and I guess after 15 years I still need help.

jeanchile
Advisor
Advisor

Hello all,

 

Thank you for your time. I have a question about a situation that shows up on every project we do and it constantly creates confusion. We create models and drawings for complex systems that involve everything from point clouds to part drawings and literally everything in between. Our common workflow is like this:

 

  1. We create sub-assemblies that represent all of the different disciplines and all of the "pre-fabricated" items in our overall design. Nothing we do can be shipped to the site in one piece, and it is often assembled on site by a different company (often that company isn't even ours, nor employed by ours, it is often employed by a general contractor or the owner themselves).
    1. a. Sometimes, entirely for ease of modeling and constraints, we create "unnecessary" sub-assemblies that are just for the ease of modeling. Think of a bolt, a washer, a lock-washer, and a nut, used in 58 connections in one piece of duct sub-assembly. We often put those in a "phantom" sub-assembly for ease of modeling patterns and constraints but not necessarily on every project.
  2. We create a "top-level" assembly drawing showing the entire project/assembly that is usually a MASSIVE file with all the elements present but almost nothing is shown clearly, it just shows everything in its final location with overall dimensions and references to project "control points" (like gridlines from an architectural/structural world or pre-established work-points for the entire project).
  3. We then attempt to show the field assembly crew the "steps" or "stages" for putting the entire project together. Like first showing them where to drill and place concrete anchor rods in the existing concrete, second, how to layout and place structural steel members (columns, beams, bracing, etc.), third, how to install the vertical circulation items (stairs, ladders, etc.), fourth, how/where to install mechanical items (pumps, ductwork, pre-fabricated mechanical piping spools, etc.), fifth, how to install and fasten the grating/floor-plate/walking surface, then sixth, how to place the work-safety items (guardrails, safety gates, etc.). The “order” for these items is often jumbled like, for example, when a large piece of equipment or ducting needs to be installed part-way through the structural steel being erected.

How do we structure our drawings so that we can represent the "field assembly steps" of the overall assembly? Because the model sometimes isn't structured according to the "steps" (think back to the phantom bolt sub-assemblies), and/or because things from one step (either later or previous to the current step) need to be shown (at least in reference) in the current or other steps, we seem to be left with only using View Representations to do this. Level of Details and suppression is the wrong tool because we're not trying to save memory/RAM in our computers, we're trying to document "steps". Positional Representations are something we often use to show kinematic layouts of the mechanical equipment, and sometimes the structure, but don't isolate steps. View Representations seem to be our only option. I am constantly running into two different error messages while trying to set these up (the "The component status is associatively set by the Design View Representation Default in subassembly: blah, blah, blah..." or the "Locking a design view representation removes all associative links...") and I often get frustrated and quit (then go back to controlling drawing visibility by "disassociating" view representations in the drawing views and then turning off the individual components in each drawing view, which is incredibly cumbersome).

 

I know this is getting long but those who have made it this far, please hang on, I'm almost there...  If I want to show a drawing view of just the ductwork, and a couple of framing members and gridlines showing their supports and overall location, how do I do this with View Representations when the existing site items created by the point cloud shown as reference geometry are done by one person, in one sub-assembly, the ductwork, done by two people in another sub-assembly, and the structure, done by two OTHER people in a different sub-assembly, both contain hundreds of other sub-assemblies, and thousands of different parts? Because, in all honesty, creating a "top-level" view rep in the overall, top-level, assembly, and then having to go through every single sub-assembly on the WHOLE project (again think about all the "discipline" sub-assemblies that usually start with the point-cloud/existing items, then a lot of those have Frame Generator sub-assemblies, some of those have Tube and Pipe sub-assemblies, then both of those often have demoted sub-assemblies inside of those, and then those often have pre-fabrication sub-assemblies representing what's delivered to the site, and then some of those have those **** phantom sub-assemblies containing all the fastener parts), just setting up a view of the ductwork could take me three days. And, then when I create those view-reps in FG sub-assemblies and such, I often get the errors because I've misunderstood something or misnamed/miscreated a view rep in one of the HUNDREDS of sub-assemblies. I cannot just click "Remove Associativity" in every error/dialog box because it causes everyone else's sub-assembly view-reps to fall apart.

 

What is the tool we are supposed to be using to do this? Are we supposed to be using something else other than View Representations? Because in the “old days” using AutoCAD it was a bunch of blocks, external references, and a TON of mistakes. Using Inventor for all of this is probably a mistake, but overall has cut our “error-rate” to a seriously TINY FRACTION of what it used to be and ENTIRELY removed the process of back-charges and the need for E&O insurance. For an example of a really small project like I'm talking about, see the picture below. This tiny project has a field-scan/point-cloud with existing silos/bucket-elevator/conveyors/structure and such, new structural elements, new mechanical elements, new ductwork, new vertical circulation, and new bar-grating/fall-safety elements. Our projects are often MUCH larger than something like this. For the two of you on this forum who made it all the way to here... thank you for going this far. I understand if you don't have a solution to offer. Perhaps just venting/typing this will allow me to get some sleep tonight.

Screenshot 2023-08-02 213202.png

Inventor Professional
0 Likes
829 Views
7 Replies
Replies (7)
Message 2 of 8

mojtaba77f
Advocate
Advocate

Using View Representations to document field assembly steps can be a challenge, as it can lead to associativity errors and other problems. Simplified Representations are a better option for documenting field assembly steps, as they are not associated with the original assembly. This means that you can make changes to the simplified representation without affecting the original assembly. In addition, you can use folders to organize components in the simplified representation. This can make it easier to find the components you need and to control their visibility. You can also create custom parameters for visibility control. This can be useful for hiding components that are not relevant to a particular field assembly step. Finally, you can explore Autodesk iLogic. iLogic is a powerful tool that can be used to automate tasks in Inventor. You can use iLogic to create custom macros that will help you document field assembly steps more efficiently.

0 Likes
Message 3 of 8

jeanchile
Advisor
Advisor

Oh man, thank you Mojtaba. This is the kind of response I was hoping for. We've used Simplified Representations for sharing content with other companies/trades, but I have actually never considered using them for documenting this stuff. It definitely sounds like the kind of situation where we are "using a tool for something it wasn't designed for", but I'm hoping this will provide us a much easier solution. I'm off to research that and will report back with my findings. If anyone else has any more ideas, I'm certainly grateful for the input.

 

Thanks again! I hope this didn't take you too much of your life to get through.

Inventor Professional
0 Likes
Message 4 of 8

Frederick_Law
Mentor
Mentor

As the name imply, View Rep control visibility of parts in View.  And lots of users used LoD for that.

By default there is only "Primary" View, which is locked.

To start you need to create new View.

I've Default and Design in my templates.

 

Also by default Views are associated.

It means if you change View in assembly, every child will use same name View.

Hence I have "Default" view.  The one for drawing with planes, sketches turned off.

"Design" is what I use when designing.  I can turn things on a off without affecting the drawing.

Association will break in this view.

 

Now if I need to show steps, I'll add views to hide parts/assembly for each step.

If I really want to, I'll add ipn.

 

ModelState could help in some case.

ie Raw material -> machine -> weld prep -> weld -> machine -> weld prep -> machine -> plating

It was difficult using iPart, derive, weldment.

0 Likes
Message 5 of 8

matthew.hansche
Enthusiast
Enthusiast

One question I have is what version of Inventor are you using? If I understand you correctly, what you want to do can be tricky using views of any type (I have been there).

 

Not to sound like a salesman, but since we upgraded to 2022 we have been able to utilize model states and have been able to easily accomplish much more than we were using a combination of Levels of Detail and views. Something to consider if you are using an older version.

0 Likes
Message 6 of 8

swalton
Mentor
Mentor

Sometimes it is helpful to nest Design View and other times it is better to create them in at one level, just for the drawing.

 

In our case, we typically create two Design View reps for each component: Design and Painted.

Design is the one that is handy for engineering design, and Painted shows the final color.  

 

Once we decide which model will be used to produce the fabrication documentation, we start adding View Reps to that assembly.

 

So in your case, we might make a "Foundations" view rep that shows all the piers and concrete work.  Then one that shows the various modules of the frames and so on.  We don't worry about breaking associativity with the sub-component view reps because we want to control the appearances of those components by trade, fabrication step, or some other way to communicate to the field workers.  Think Lego instructions where the components in the current step are normal colors and components from previous steps are in a neutral color.

 

It works well to document the process for a new machine, but can be tedious when revisions change how the machine will be built.

 

I suspect that some thought and iLogic programming time would automate some of the View Rep creation process.  Adding some iProps to the sub-component models to store the proper assembly step/trade might be helpful.

Steve Walton
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Inventor 2025
Vault Professional 2025
0 Likes
Message 7 of 8

jeanchile
Advisor
Advisor

Thank you Mathew, we are using 2024.0.1 but will be upgrading to the 2024.1 version soon.

 

I'll dig around on the "model states" you mention (and it didn't make you sound like a salesperson, FYI) and see if they'll work for our situation. I don't know what "model states" is, but it sounds similar to what Mojtaba was talking about.

Inventor Professional
0 Likes
Message 8 of 8

jeanchile
Advisor
Advisor

Thank you Steve. What you are talking about in your post is exactly what we are trying to accomplish. Your post had one statement that I'm curious about though:

 


@swalton wrote:

 

... and so on.  We don't worry about breaking associativity with the sub-component view reps because we want to control the appearances of those components by trade, fabrication step, or some other way to communicate to the field workers.  Think Lego instructions...


In making view reps before, I have tried the whole "break associativity" scenario, but if I remember correctly, when I selected that option, some of the nested items were completely "messed up" afterward (e.g. some of them had various work-planes and such visible, the "safety yellow" appearance on some of the items disappeared, some of that assembly's view reps were different, etc.).

 

Do you (or anyone else) know what exactly is supposed to happen to the nested sub-assemblies when you select the option to "remove associativity" when that dialog box jumps up onto the screen (as in, why would the painted appearance on sub-assemblies be changed just by selecting "remove associativity")?

Inventor Professional
0 Likes