Master model concept without Teamcenter

[jettson]

We are using NX6 w/o Teamcenter. We now create a solid model file. To create a our drawing we create and assembly and attach the solid model (just created) and then go to drafting to dimension the part. This creates a model file and a drawing file with the same number but a different extension. ex. 200300_01m and 200300_01D

This was implemented quite a few years ago and was said to decrease loading time when you bring up an assembly and save on file size.

We are wanting to start putting the model and the drawing in the same file.

The problem is that we keep hearing the MASTER MODEL CONCEPT) when we bring up this change.

We do not send our files to other departments and engineering is the only dept that works with our files.

Need advice on how on which way to proceed.

Thanks

 

[JohnRBaker]

You've already gotten the best advice that you're going to get: CONTINUE TO USE THE MASTER MODEL APPOACH.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

To an Engineer, the glass is twice as big as it needs to be.

 

[jettson]

Thanks John, but why is this concept better than 1 file containing the model and drawing?

 

[looslib]

Why do you think you want to go back 18 years in time and do the drawing and model in a single file?
What advantage do you think you will gain?

Master Model has many advantages even if you don't have a PLM system running (ruining, some say) your daily life!

As long as you have a control system for changing file ownership and permissions so your released drawings and models cannot be changed, you can use NX without a PLM system. I worked for a large company that managed UGII data for 20+ years with no PLM. We had folders that we moved released files into the users could not write to. All done with scripts and GRIP. Even in 2009/2010 I worked for a VERY large NX customer who did not have PLM in this division in Texas. I was the admin and had to manually move files to the release folders every day. Wrote some GRIP code for them to at least put things in an In-Check folder automatically so I only had to go there to find the files t be released.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[cowski]

Here are some advantages in no particular order:
[ul][li]revisions for model and drawing can be tracked independently[/li]
[li]model file size is reduced, resulting in better performance in modeling and assemblies[/li]
[li]work on the model and drawing can take place in parallel[/li]
[li]the use of reference sets simplifies management of objects in the drawing[/li]
[li]model can be positioned in the drawing independent of the model or assembly position[/li][/ul]

In short, master model is considered 'best practice' because of the flexibility it offers. Of course, no one is forcing you to use master model method; test for yourself to see the pros/cons for your particular application.

http://www.nxjournaling.com

 

[jettson]

Thank you for the advice. We probably stay with the master model concept. The reasons this question was submitted is:

We have no data manager
We change the name of our drawings and models per rev (123569_01 to 123569_02)and archive the old drawing.
We have 0 IT help on files managment and are still running 6
No files are locked and anyone can modify or delete any drawing or model. (Not sure if IT even backs them up)
We have no standards for modeling or drawings
We have some users that do not use sketcher and do not contsrain assemblies
We have to attach patterns for our title blocks
We have to use search for our load options and have files scattered everywhere. (this takes forever)

Thank you again for your advice