ENOVIA SmarTeam .NET Problems

Multiple ENOVIA SmarTeam versions are currently experiencing problems as a result of a series of Microsoft Windows Updates published earlier this year.  Specifically, the problems are related to several SmarTeam executables, including SmarTeam Editor, the SmarTeam Workflow Service, and other SmarTeam executables.  The core problem is that Microsoft appears to have changed their implementation of some garbage collection code in all versions of the .NET Framework, and this code is fundamental to a number of applications like SmarTeam.   Continue Reading

Gotcha with Oracle 11g for SmarTeam

For those of you planning to move to Oracle 11g with SmarTeam V5R20, watch out for this one.  With 11g, Oracle has introduced a feature called Deferred Segment Creation.  Generally speaking, this is a nice feature because it saves space in exports and eliminates unneeded storage allocation in many databases.  It can create problems with ENOVIA SmarTeam, however.  Continue Reading

CATIA V5 UUID Uniqueness

Given that UUID stands for Universal Unique Identifier, it may seem strange to talk about uniqueness in this context.  But it comes up more often than users might like inside of CATIA V5.  It isn’t simple to determine the UUID of a CATIA V5 file, nor is it easy to manipulate the value.  With a little bit of information though, it isn’t too hard to avoid some basic CATIA V5 UUID problems.  Continue Reading

EPDM Document BOMs vs. EPDM Item BOMs

A lot of people in the SolidWorks Enterprise PDM community were excited when EPDM Item BOMs were introduced, but the EPDM Item Explorer and its related features still cause some confusion about how to use both EPDM Document BOMs and EPDM Item BOMs.  Unfortunately, it’s impossible to definitively settle the question of whether to use EPDM Document BOMs, EPDM Item BOMs, or both, in a short article.    However, there are some general rules of thumb worth considering in determining whether EPDM Document BOMs or EPDM Item BOMs best fit a company’s business strategy:  Continue Reading

Swapping Models in SolidWorks

Design Automation is very powerful when creating unique “same as, but” models for new jobs. But in many cases, people are doing configure-to-order (CTO) just as much as they are doing engineer-to-order (ETO). Configure-to-order means utilizing standard components and using the automation to determine the logic for which component, or which size of a component, to put in an assembly. Configuring an automated design sounds simpler, and in many ways it is, but there are a few things to note and some design automation best practices to follow when planning to swap models in SolidWorks.  Continue Reading

EPDM Document BOMs

SolidWorks Enterprise PDM offers a number of ways to work with BOMs (Bills of Materials).  In EPDM 2008, SolidWorks introduced the Item Explorer, along with Items and Item BOMs.  Although many in the community welcomed this addition to EPDM’s BOM capabilities, EPDM users should not overlook the possibilities inherent in the EPDM Document BOM.  Here are some of the key capabilities of, and possibilities for, using EPDM Document BOMs: 

Continue Reading

SolidWorks Assembly Mates for Design Automation

When creating your SolidWorks assembly master models and preparing them for automation, a lot of decisions need to be made in developing the best mating schemes. One important consideration in this development is the creation of the relations between components. The design intent in your models can be established by parameters that are driven by your automation tool, or by relations within SolidWorks.  Let’s dig into this a bit deeper to uncover some an important design automation best practice related to SolidWorks mating.  Continue Reading