My project involves splitting a workflow between two departments and merging the resultant design in the final stage before submitting to the shop. As fas as I can tell, PLM 360 does not handle concurrent workflows? I am trying to avoid creating a release for each department as there is a fair amount of concurrent design required and each department has their own BOM.
What is the best way to handle concurrent development using PLM 360 when each department needs to remain in separate user groups and have very different workflows and approval cycles?
Currently I'm setting it up with the main Project splitting into smaller Releases, (one for Division 1, one for Division 2) each with their own workflows.
The difficulty arises when, for example, stage two of eight in Division 1's workflow requires a compatability check with one of the states in Division 2's workflow.
Also, since Division 1 and 2 BOMs are separate there is no longer a master Bill of Materials, which is something I was hoping to maintain. Currently the only thing I can think of is scripting a sync between the Release's BOMs and the main Project BOM (which is synced with our inventory management software at certain states in the Project workflow).
If it would be helpful, I can mock up our workflow in Visio.
Thanks,
Steve