Cancel
Showing results for 
Search instead for 
Did you mean: 

Best practice advice to represent Non CAD data in assemblies

Genius
Genius

I need pointed in direction to look for recommended practices to represent Non CAD data in assembly files. I have tried various searchs here and in Teamcenter forum, but not seeing what I am hoping for.

 

We are in early stages of a Teamcenter implementation with Solid Edge 10 currently, we will be on ST 2019 when Teamcenter begins testing.

 

Paint, solder, grease etc. are the type of items we do not currently show in assembly models.

 

Each of these items is represented by a controlled part number in our Oracle system now. Rough estimate of seperate items is over a thousand.

 

We are in the early stages of just moving from AutoCAD based system to Solid Edge, at this point we have about 1,500 drawings, 600 assemblies. This represents less than 10% of our overall drawings. I would like to make good decisions on adding the Non CAD data.

 

Thanks,

 

Gary Dinges | Mechanical Design Engineer II | Probes & New Product Development
Emerson Commercial & Residential Solutions | Therm-O-Disc, Inc.| 1320 South Main Street | Mansfield | OH | 44907 | USA
T +1 419 525 8554

gary.dinges@emerson.com

5 REPLIES 5

Re: Best practice advice to represent Non CAD data in assemblies

Legend
Legend

Our practice, is that we have .par files that have the properties for non-cad parts. We then will drop those files of no physical property into our assembly, this way it can show up in our BOM on our drawings, and what we import into our ERP system. Many of these non-cad files require setting occurances for how many units as needed for each assembly.

Betreff: Best practice advice to represent Non CAD data in assemblies

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Hi @Gary_Dinges 

 

 

as said by @Trikefreak  I also would use such NonGraphical parts.

 

They are defined once with units and precision and can be used in any amount for every assembly.

 

Search help and/or the forum  here for the defi option parameters in custom properties.

regards
Wolfgang
Highlighted

Betreff: Best practice advice to represent Non CAD data in assemblies

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

@Gary_Dinges Here is the Help page on non-graphical part use.

 

https://docs.plm.automation.siemens.com/tdoc/se/2019/se_help/#uid:ngrphc1a



Ken
Production: SE 2019 MP5, Testing: SE 2020
http://Grundey.blogspot.com

Re: Best practice advice to represent Non CAD data in assemblies

Phenom
Phenom

We bulk imported our equivalent non-cad parts into Teamcenter with TC properties as appropriate via a script our VAR wrote for us.

 

We do things differently from the other people who have replied here as we do not add a Solid Edge dataset to the ItemRevision in Teamcenter, but instead add the non-cad parts to the Structure Manager BOM in TC. 

 

These items will not then appear on you draft BOM table. Not sure what your plan is, but as our manufacturing BOM is driven from StrMan, that works well for us, and we don't have those items cluttering up the feature tree. 

 

Just an alternative suggestion.

Re: Best practice advice to represent Non CAD data in assemblies

Gears Phenom Gears Phenom
Gears Phenom

@Gary_Dinges  - because you are using TC, you can just create the Item in TC without a Solid Edge file. That Item Revision can be used in the Solid Edge assembly. Search and drag & drop (without applying relations by holding the shift key). It is represented by a green triangle in your assembly tree. There are a few custom properties and a couple of Teamcenter preferences that need to be set. If you read the SEEC Admin guide, you'll find more info about it. Also, look at this document from Gtac that gives the details with pictures: https://solutions.industrysoftware.automation.siemens.com/docs/newsletter/seec-working-with-non-grap...

 

Jamie Griffis | Teamcenter Architect | Applied CAx, LLC