cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Improve interaction of PDMLink and ProjectLink

Improve interaction of PDMLink and ProjectLink

The interaction of PDMLink (Products and Libraries) and ProjectLink (Project) needs to be improved.  We start all of our engineering projects in ProjectLink and eventually at one phase or another of the project we "Send to PDM" the necessary CAD Documents and WTDocuments into either a Library or a Product.

We also are sharing a large amount of PDMLink CAD Objects into projects, and some are checked out to the Project as well.  We do this for development of the new project.  None of our projects are started from scratch, we are always building on what has been done before.

Because of the poor interaction of ProjectLink and PDMLink, these tasks prove to be much more difficult than they should be, impacting our efficiency in engineering and our ability to complete seemingly simple tasks in an efficient manner.

Just as there are only minor differences between a Product and a Library, the differences between a Project, a Product, and a Library must be minimized as well.   In fact I would like to see a workflow where I start a project as a ProjectLink project, and when completed have the option to turn it into a Product or Library.

Improvements that must be made:

  1. ProjectLink routing capabilities added to PDMLink.  I want to be able to notify a team of something, not have to "Promote" the document.
  2. Send to PDM vastly improved or the need for the command done away with.  See C12200545 for an example of the issues we have run into.
  3. Sharing to a Project improved or the need to do so eliminated.  Why do I have to share at all?  The need for this should be eliminated.
  4. Add the ability to change a Project into a Product or a Library. Or vice versa  Might eliminate the other improvements if done correctly.
  5. Probably more, but you get the idea.

Bottom line is that users see Windchill as a singular entity.  PDMLink and ProjectLink must look and act as such to avoid Non-Value Added efforts.

-marc

CAD / PLM Systems Manager

TriMark Corporation

4 Comments
Tanzanite

Marc,

I agree with your idea, above all on point #1.

Participant

I agree, also.  I would add that sharing PDMLink documents to ProjectLink needs similar improvements.  Specifically, if I share revision "A" of a PDMLink document to a project, and if the PDMLink document revises to "B", then there should be some simple way for ProjectLink to auto-update to the new revision on Release, if that is a preference that the Windchill system has set for the State and Auto-Update. If that is not possible, then auto-sharing future revisions should be possible, so that if you share "A" then on Release "B" can also be shared.  Right now, sharing engineering drawings with our customers is complicated by this PDMLink to ProjectLink document sharing functionality.

Moonstone

Here is a link to a related idea that you might want to consider voting on:

Allow routing type workflows for all contexts

Community Manager
Status changed to: Acknowledged