This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

APPLICATION - PRODUCT ENGINEERING - Planned setup. Is this possible?

Thobbe - Thursday, June 20, 2013 4:42 AM:

Hi

We are in the beginning process of implementing a PLM system

Our needs are like this:

When project starts we know that we will build 3 prototypes and a release part with a BOM list

First build will be called A1 second A2 third B and the release  C

All will have a BOM list and the importance  here is that if A1 is released with a BOM that have 3 items and a certain revision not will change, when we increase revisions for A2 or B BOM list items.

This for purchase to order the correct BOM item revision to correct prototype.

We made a test on this and we got this result:

Released part 11 Rev A

Created Part 11 Rev B

Changed some Rev on BOM items

Released Part 11 Rev B

Created Part 11 Rev C

Now we have to change Rev A and this get me confused

A new Rev B is created?

A new A1 or new C would have worked but not a new already released version.

Can I do what i want?

I'm not here to get a full solution just if it's possible and some hint's would be very appreciated.

 

Cheers

Thobbe 



Brian - Monday, July 15, 2013 10:35 PM:

Hi Thobbe,

You can't do what you described above in the standard system since when you create the new revision of part 11 from Rev A to Rev B all of the relationships to the Rev A item are locked down and Rev B now takes its place. Rev A becomes superseded.

When you try to edit the old Rev A the system tries to create a new Revision based on the old one and looks for the new Rev number which would be "B" but you already have one of those so it can't do it.

You might be able to do something like that if you change the Versioning from Automatic to Manual but to be honest I haven't tried it so not sure how the system reacts here.

Hope this helps,

Brian.



[email protected] - Tuesday, August 13, 2013 4:47 AM:

Hello Thobbe,

I have a lot of experiences regarding manual versioning. Your tobic can be done by using fixed/float behaviour within relation and lifecycle states. Within automatic versioning there is following behaviour:

If the item is "released" the major revision is updated when locking/unlocking the Item. A lock on a released item will automatically create a new major_rev.

But to be honest to understand your need it would be helpfull to get the scenario on the system a little bit more detailed.

Please feel free to add additional screenshot describing your problem and there will be a possible solution.

// Jens