Allow "Move" and "Copy" of CAD Objects between Workspaces

[sprosser]

...formaly known as "Export to Workspace" in Intralink 3.x...

Users tend to collect CAD objects in their Workspaces.They start to grow (Number of objects) and become slow. Wouldn't it be great to e.g. select one assembly in the Workspace and start a new workspace with this assembly and the dependend objects (move them so they are removed from the source Worksopace)?

Another Usecase:

A CAD Designer is currently working on improving a part - while he is doing this his boss is showing up and asking him for another solution to improve the part. What agreat functionality if the CAD Designer could easily make a copy of his part into a new workspace and start the othe aproach in the new workspace.

This function  improve the flexibility and performance for test and variant designs.

On the other hand the user know this function from ProINTRALINK and the absence in PDMLink  doesn't improve the user satisfaction....

[ChrisPLM]

I think his boss should be concerned on the number of data the user has in his workspace which are not checked in (check in does not include release). If the user is off sick, what does this boss do. What control over IP has the company if the user keep plenty trial and concept in his workspace. PDMLink is an entreprise system to support processes not a vault or an engineering tool.

That is a key difference I think many CAD users do not understand. Working in a PDM where processes (be NPI, NPD, including use of PJL or not) are managed, pushing the data along side.

This is a different approach to simply managing CAD.

Having this functionality will only create more mess in user workspaces.

I obviously votes against and wonder if those who voted for are only CAD designers ?

Best regards

[mschulze]

This used to be possible in Windchill 9.1. Using the add to workspace function within the workspace. So  this probably a "removed functionality" bug.

But even in Windchill 9.1 this was not an intuitive functionality.

This function makes sense and should be easy to use.

[rpalmisano]

Totally disagree with your point of view, in our case, we used the Export to Workspace in ILink 3.x because we are working on several solutions for the same problem.

Expl. Designing a Jig for some manufacturing purposes, obviously you can have more than one solution, 1 more effective than another, but far more expensive. Sometimes having all these variation designs in the same Workspace makes it confusing and hard to manage. Sometimes most of these solutions have many common parts, so you don't necessarily want to check these in who can eventually never be used, but you definetly don't want to redesign the same part or assembly again.

The Export to Workspace was definitely a useful command.

[ChrisPLM]

Hello Remy,

obviously every company decides on their best practices. I personally would not implement such was of working.

In the example you described, I would make use of ProjectLink as, I imagine the design decision will be made of many contributing factors outside of creating CAD files such as availability, cost from suppliers, testing, results of simulation etc....

Clearly (to me,( there are more than one person who needs to know about the various ideas the designer want to investigate and therefore it is a collaborative work. Collaboration = check in, sharing.

as explained above, if you export you duplicate and that is bad practice, especially when it is to share with people from inside the organisation.

So sorry, I still believe such functionality would encourage bad NPD, PLM, R&D practices.

PS; In PDMLink, you can still export from Workspace, then Import AS NEW into a new workspace.