Roll working copy revision back.

[CubicleHound]

I need to work on a part currently at revision 1. I would like to check it in before I am finished like a working copy "1+" and when I am finished I want to go back to 1. Is there any way to do this? Working copy does not let you. I have "Allow latest revision overwrite" enabled. I have tried combinations of primary and secondary revisions too.

I realize the purpose of PDM is to disallow you to go back in time, but shouldn't I have the last word on that?

Clem
ME
SW/PDM 06 1.0

 

[PDMAdmin]

What exactly are you trying to do? Are you simply trying to delete the working copy and rollback to revision 1? If that's the case, PDMWorks lets you do that. However, if you're trying to essentially rename the working copy revision to revision 1, you cannot do that, because revision 1 already exists in the vault. If you insist on the final revision being 1, you will need to delete the working copy and revision 1, then check the new file in as revision 1. That seems a little excessive, though; it seems to me that you could accomplish the same thing using primary and secondary revisions.

 

[CubicleHound]

I thought so too, but I cannot seem to arrive at the initial revision.

The reason for doing this is that we have outsourced some conversion and as assemblies come in they are at a specific revision. We have to check those assemblies and sometimes fix them. So we are working on them and they are different (newer) than the inital revision when we complete the check/fix. We then need to check it back in at the initial revision number because the file did not get officially revised. We need a way to notate that the assembly is in the process of being fixed.

If I use two revision levels, I can make it go 1->1a->1b, but then I can't go to 1 without doing what you said and delete revision 1 first.

This all stems from the fact that our detail drawings extract the revision number that is displayed on the printout, from the part/assem. If I could have a drawing exist at revision 1C but only have the number 1 appear in our revision box, then that would work too.

Convoluted enough for you?

Thanks for any ideas you might have.



Clem
ME
SW/PDM 06 1.0

 

[dsgnr1]

We had kinda the same delimma (I think).
We needed an initial rev prior to an A rev because if we used A as the initial revision then the first rev was A (working copy would have been A+ or whatever. We ended up using "A-init" prior to rev A.

regards,
dsgnr1

¿)

At some point you just have to shoot the engineer and build the dang thing.

 

[CubicleHound]

dsgnr1

I see what you mean. This would help for the inital revision of an object. I guess I was concerned also about parts that are alread at a subsequent revision that need to be worked on, but aren't getting an offical revision bump. I think we just need to revisit incremental revisions.

Can you put a formula in a sheet format block? Then I could make 1.3 appear as 1 in a block.

Clem
ME
SW/PDM 06 1.0

 

[dsgnr1]

the problem we were have was that we wanted our designers to vault the files over the weekend...bang they are rev A and have not hit the production floor.

didn't like that idea.

good luck CH

¿)

At some point you just have to shoot the engineer and build the dang thing.

 

[EEnd]

Would this work?
When you get the files from the people who are creating them, place them into your vault as a working copy or lower revision level (secondary, tertiary) of the previous revision. For instance, if you have a part come in that you want to be revision C. You could check it in as B+ or B1 or B1+ depending on what was in the vault for that part prior to your new data. Then once you get it fixed up and checked you could then check it in as revision C.

If you want the part to be at the first revision, you could have a prerelease revision level. I did this by specifying the primary revision as a list: @ X A B C … W Y Z. The X is the prerelease revision level and the @ is … well redundant I guess.

As far as having A1 or 1.3 show up in the title block, I treat that as a feature. Any file that has an intermediary revision level is between released versions. Seeing A1 or 1.3 as the revision is a red flag that the drawing you are looking at is not at a “ready for production state”.

Eric

 

[CubicleHound]

Eric,

Thanks for the suggestions.

In you example I see what you are saying about checking an something in as B, but that would require you had the forsight to know you were going to need to make changes before arriving at C. I am looking at parts already at C without my control and now I need to work on it, make it known to others that I am working on it through revision numbers/symbols/letters, and then finish by keeping it at C. I think it is a lost cause.

I do think I am going to implement the prerelease revision thing though.

Clem



Clem
ME
SW/PDM 06 1.0

 

[EEnd]

Are the files already in the vault at the revision that you want to use? If so then PDMAdmin's suggestion about rolling back the vault to the last revision before the one that you want to use and then checking the most recent copy in is the most direct way to get the vault to have the revision that you want. The vault will delete the files for all of the revisions that get rolled back. At the minimum you will need a local copy of the version that you want to put back in.

If the files are not yet in the vault, but their revision fields are set to the current level, you should be able to put them into the vault at a working level of the previous revision. PDMWorks changes the revision property of the file to match that of the vault.

 

[CubicleHound]

Thanks Eric,

I'm trying to bend PDM to my wants, but in fact I need to use PDM as it was intended. I think I now have the tools to revamp our thinking of the revision scheme as a whole.


Clem
ME
SW/PDM 06 1.0

 

[wgchere]

Not being terribly sophisticated with equations, etc. I solved the problem of intermediate revs by creating a REVBLK Custom Prop and linking the drawing revision text to that. Unfortunately, the REVBLK property has to be manually updated.

Our company has 1.1, 1.2, etc. for pre-initial release work, then when it is released the Configuration Control Manager changes it to -.-. Now, when someone plays with the file and saves it is -.1, -.2, etc. but when it is released at Rev A the CCMngr changes it to A.-.