Development Status Tracking

[sdrzewiczewski]

How are you currently tracking the development status of a Product, could even be a subassembly of that product?

Currently we have an excel spreadsheet that has a manual copy of the BOM and then there are some columns that are populated that are tallied on a summary sheet of the spreadsheet. This spreadsheet does alot of duplicate work that is already done in Windchill or our ERP (Oracle) system. We are looking to make this too (the spreadsheet), go away, but this one piece of functionality is not really represented well in either of the two tools.

If this is something that you are currently doing today either in Windchill, your ERP system or another external tool, I'd like to hear how you are addressing these issues.

Thanks,
Steve D.

[kpritchard]

We've applied our development lifecycle to WTParts. PTC (Business Admin) Documentation illustrates a 2 Stage development Lifecycle, ours is essentially an extension... multiphase development Lifecycle. You'll probably want to have an editable and locked state for each phase. We've also restricted avdancement of WTPart State(other than X-Editable to X-Released, i.e. X-Released to Y-Released) to the PromoteWorkflow and any editableto/from releasedstate to Change Management Workflow vialifecycle transitions. Also advise keeping the State "names" as short as possible as multiphase eats up a lot of display area.

Hope this helps...

PS - Have an active Enhancement Request to anable Version Control in Project-Link to be able to manage early stage development work with lighter weight routings.