is this a good practice to create drawing file for assembly?

[godpaul]

here is what i plan to do:

complete model 1.prt
complete model 2.prt

complete assembly for model 1 and 2, get assembly.prt

then finally, create a STANDALONE DRAWING
insert blank sheet 1, sheet 2, sheet 3
on sheet 1, insert base view, when prompted for prt file, pick model 1.prt
on sheet 2, insert base view, when prompted for prt file, pick model 2.prt
on sheet 3, insert base view, when prompted for prt file, pick assembly.prt

is this practice good? OR.......
a drawing file should be exclusively for one model
and a drawing file should be exclusively for assembly prt file


i ask this question is because later on i want to use code to update EVERYTHING, model1, model 2, assembly and drawing,
that's why i try to reduce the number of drawing files but just increase the number of sheets in one drawing.

thank you very much !

 

[NutAce]

In my opinion, I wouldn't do this.

This would mean that all the individual components and the assembly would get the same drawing nr.
How would you differentiate them when you would want to order the individual components?

I would just create one drawing for each component, and one for the assembly. Placing separate views on that Assembly drawing for each individual component can be done of course, but I would keep the assembly as the main drawing. (Sheet 1)

Starting with a Stand alone drawing you can do of course, but why not directly create that from the Assembly? Then there is no need to connect it afterwards.

Ronald van den Broek
Mechanical Engineer
Cad Environment Coordinator
Wärtsilä, Propulsion Services
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5
HP EliteBook 8570W Intel(R) Core(TM) I7-3740QM CPU @ 2.70GHz, 16Gb Win7 64B

 

[godpaul]

thank you, one thing i dont understand is the last sentences you said: " Then there is no need to connect it afterwards"

well, sorry for not stating the reason very well, the reason i pick Standalone drawing is because that's the only option to create a new drawing without referencing any part file.
but after listening to you suggestion, i will give up what i plan to do and do the following:
create model 1 and 2,
create drawing for model 1 and 2

create assembly for model 1 and 2
create drawing for assembly

so i have two drawings. :0


i haven't done too much study, what i eventually want to do is:
if i modify external parameter expressions for model 1 and 2, then in the VB code, after i click update, model 1 and 2 will be updated. After that, drawing of model 1 and 2 should also be update. Finally, update assembly and its assembly drawing
OF COURSE, EVERYTING WILL BE OPENED JUST IN CASE NX NEEDS TO FIND FILE TO UPDATE
what i worry about is the order that NX is going to update part file, assembly file, and drawing file

 

[Xwheelguy]

Why write a code for any of this? NX does this for you after you revise your models as long as the dwgs are using the master model concept.

Create a simple assembly, like of a square nut and a bolt. Create 3 dwgs, one of the nut, one of the bolt and one of the asm. Dimension the hole in the nut and the shaft, and the overall distance from bolt head to nut face. Change both the nut hole diameter and thickness and then the bolt shaft diameter and head thickness. Go over to the drawings and update the views. All your dimensions should update. No code needed unless you're wanting to do this for the sake of learning.

Tim Flater
NX Designer
NX 8.0.3.4
Win7 Pro x64 SP1
Intel Xeon 2.53 GHz 6GB RAM
NVIDIA Quadro 4000 2GB

 

[cowski]

I wouldn't worry about the update order, NX is very good at performing updates correctly. Whether you use one collective drawing or three individual drawings, NX doesn't care.

The question goes beyond what is good practice in NX to what is good practice at your place of work. Remember that the engineering documentation is used outside of engineering. How will your strategy impact manufacturing, purchasing, and documentation control? If drawing "A" has details for parts "B", "C", and "D", how do you order just part "B"? If part "C" needs a revision, do the other parts get bumped up a rev level even though nothing changed on them? How do you explain that to purchasing?

www.nxjournaling.com

 

[Xwheelguy]

Also consider file naming conventions - if your drawing files have the revision levels in there, how will all component dwg revisions be distinguished from any sub-asm and asm dwgs?

I feel your idea of a single dwg file containing all dwgs is great, however, I've not seen anyone put it into a workable practice as of yet. The main reason being most companies for which I've worked preferred to have the dwg revision in the filename (to avoid having to actually open the dwg and physically look at the revision level).

Tim Flater
NX Designer
NX 8.0.3.4
Win7 Pro x64 SP1
Intel Xeon 2.53 GHz 6GB RAM
NVIDIA Quadro 4000 2GB

 

[godpaul]

come to this forum will always have great suggestions
this is the drawback when working alone on this project...

we have a bunch of tools design from outside, they share the common features, what i do is to commononize those features and make a master model like you said. after that, i also create a master drawing for that master models.

that master model can take care of 5, 10 or even 20 different tools.
so, when a new tool is coming, i take a look and see if it fits to the master model, if it is, input dimensions in the Excel sheet

in the end, what i do is use code to ask NX to grab data from Excel sheet and update the model.
up to now, like, Xwheelguy said, i can simply go to drawing and click update manually, BUT since i am already on this track, i just want to save a little more time.
so, my big goal is one mouse click and go.

as cowski you said, honestly, i haven't considered how to maintain the revision number and all other potential issues.( maybe after the update, ask code to "save as" in order not to destroy the master model and drawing?)

lots of things to be considered honestly, I just dont know
i am new, only have 1 month NX touch...so sometimes i may not realize what i do is not good practices...