BOMs with multiple controlled states?

[sdrzewiczewski]

Our lifecycle has 3 states that are what I call controlled. We have Prototype, PreProduction and Production. We then have several working states, In Work, Prototype In Work, PreProduction In Work, Production Change, then there are others for obsolence, reviewing etc...

One of the struggles I'm having is to show a BOM and only show the three controlled states. If there are any of the other states those iterations/versions should not be shown. I know that you can view a BOM based on state, such as Production, but if there is no Production it would show you a working state.

I've been able to configure a role, that only has read to the three controlled states and this accomplishes what I'm looking for, but is not really how I want to ultimately deliver the functionality. I would rather a report for a user to run that has the logic built into it, versus having to give the user an additional account assigned to that role, so they could look up a BOM.

Do other companies have similar issues? If so have you been able to address them?

Thanks,

Steve D.

[MikeLockwood]

We have exactly this situation - it follows directly from using the OTB two-phase lifecycle and statebased versioning.

There should be multiple states, but with logic to select one if available, then look for the next, etc.

[mkraegeloh]

hi,

we've done this with a small customization which involved creating
states in the resource bundle like "PROTOTYPE|PRODUCTION".
the user could choose such a state when selecting the config spec, in
which case either state would qualify for display in the BOM.

martin

Lockwood,Mike,IRVINE,R&D wrote:
> We have exactly this situation - it follows directly from using the
> OTB two-phase lifecycle and statebased versioning.
>
> There should be multiple states, but with logic to select one if
> available, then look for the next, etc.
>

[sdrzewiczewski]

After you added the new state, dod you need to change anything else?

Thanks,
Steve D.

[ptc-1965197]

Hi

we have exactly the same need, with a LifeCycle Initial|Development|Proto|Prod|Released.

Can you explain your customization ? Have you only add entries in the StateRB ? Or have you also customized the OOTB BOM ConfigSpec Visitor ?

because It does not work on my PDMLink 9.1 ...

Does it work in all Windchill ConfigSpec bades UI, like HTML BOM, PSE or MPSE ?

Thanks in advance

Best Regards

Gregory