Occasionally, I'll come across parts that are called out as assemblies. I see it happen with some beginners or done as a shortcut to avoid having to create an assembly.

For example, in my line of work, rivet are commonly not shown, so I may see a bracket that is called BRACKET ASSY, but it's a part. If another bracket or some hardware needs to be added to this “assembly” it takes a bit longer to update and becomes a pain if it's been used in a lot of assemblies.

Does that make more sense?

Occasionally, I’ll come across parts that are called out as assemblies. I see it happen with some beginners or done as a shortcut to avoid having to create an assembly.

For example, in my line of work, rivet are commonly not shown, so I may see a bracket that is called BRACKET ASSY, but it’s a part. If another bracket or some hardware needs to be added to this “assembly” it takes a bit longer to update and becomes a pain if it’s been used in a lot of assemblies.

Does that make more sense?

As far as same views, that's a good one. Also, try to model the components in the same orientations and reference points. That way if you have to replace the component with a different one, you will decrease or eliminate the amount of mates that you will have to fix. I try to model each component the way it is going to be oriented in the final product.

Also, for drawings, don't forget to leverage the power of Configurations and Display States to eliminate the number of Drawings/Assemblies you need to manage.

As far as same views, that’s a good one. Also, try to model the components in the same orientations and reference points. That way if you have to replace the component with a different one, you will decrease or eliminate the amount of mates that you will have to fix. I try to model each component the way it is going to be oriented in the final product.

Also, for drawings, don’t forget to leverage the power of Configurations and Display States to eliminate the number of Drawings/Assemblies you need to manage.