Transition files into PDMWE 1

[SuperMPG]

We have discrete files for revision history, but when we slide into the PDMWE domain, we'll need to convert that scheme to the internal revision history in the database.

NOW--

part_A.sldprt
part_B.sldprt
part_C.sldprt
part_D.sldprt

IN PDMWE--

part.sldprt with rev history stored internally


I can place rev D in the vault and walk it through the rev history manually so that the internal database recognizes it as rev D, but there will be no actual history, since revs A through C are not in the vault.

Is there a (relatively painless) way to put all 4 files in the vault and have understood as part of the rev history, not as four separate files?

I hope that makes sense...

B-

 

[NL8]

SuperMPG,

I understand what you are trying to do, but I don't think it's possible to integrate everything so that an actual revision history is generated. PDM not only sees what's changed, but also stores the changed geometry so that you can roll back to it at need. I'm thinking your best bet, if REv history is that important to you, is to check in part_a, change it so that it matches b, check it in as B, change it to match C, check it in as C, etc.

In essence you may have to go through the whole revisioning process again if you want to actually show the changes in every step.

Joe Hasik, CSWP/SMTL
SW 09 x64, SP 4.1
Dell T3400
Intel Core2 Quad
Q6700 2.66 GHz
3.93 GB RAM
NVIDIA Quadro FX 4600

 

[RawheadRex]

SuperMPG,

I don't have a good answer to your question other than to suggest that you may want to speak to someone about data migration as part of your implementation. They may be able to pull this off.

Best regards,


Chris Gervais
Application Engineer
CSWP, CSWST

 

[SuperMPG]

Ouch! That would be totally out of the question.. we have thousands of parts and assemblies, some of which have 8 or 9 revisions. If what you say is true, I'll definitely need to come up with a plan B.

However, I can see (by doing a little file system snooping) that PDM stores each revision and version as a separate, complete SW file, which suggests that in doing a rollback it may not just update the geometry according to a set of edits but rather it would just pull up an earlier file, complete with the geometry state at that point in time. If that is true, then technically I should be able to insert each revision file into the history stream at its proper location. That, too, would be a major headache, but is possibly automatable.

Hmmm... much to think about.

B-

 

[kellnerp]

If you happen to be thinking of going to dbWorks you might find that a script can be written to do what you need. This comment is predicated on the assumption that you have been absolutely consistent in your naming.

TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."

 

[SuperMPG]

How does dbWorks compare with PDMWorks?

 

[kellnerp]

I think better than Workgroup or Enterprise.
[ol i]
[li]Deals with configurations extremely well, including the revisioning of the same.[/li]
[li]Good note management tools to allow custom notes fed from the PDM side allowing many notes to be filled in from the PDM prior to even making a drawing and also makes the notes searchable in PDM.[/li]
[li]Fantastic support[/li]
[li]Highly customizable[/li]
[li]A lot of the scripts are open to user.[/li]
[li]Has a good web based tool that can be distributed to people who feed of engineering's drawing like mfg people[/li]
[li]Can tie into ERP[/li]
[li]Autonumbering and some other tools included[/li]
[li]Maintain existing file structure if desired. [/li]
[/ol]
That's just a few.

TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."

 

[900SS]

Hello SuperMG, Have you contacted your SWKS VAR about this? What you are facing is what EPDM handles for you automatically once implemented. The manual method you described in the beginning is typical for non PDM users and can be migrated into EPDM. It may require a a script for automating the load or not. However the DBWorks way will also be faced with the same challenge.

Are you a customer of EPDM now or considering it?

 

[fcsuper]

In my experience, it's not worth the trouble. Your old system will still exist, so if someone needs to go back into history at some point, they can go to the old files. After about a year or so, older revisions will not likely needed any more than one or twice a year. There's no ROI when trying to transfer history over.

Matt Lorono
CAD Engineer/ECN Analyst
Silicon Valley, CA
Lorono's SolidWorks Resources
Co-moderator of Solidworks Yahoo! Group
and Mechnical.Engineering Yahoo! Group