Skip to main content
M
MikeLockwood22-Sapphire I
22-Sapphire I
March 19, 2015
Question

outsourcing CAD work - data managed in Windchill

  • March 19, 2015
  • 8 replies
  • 1939 views

Now involved in discussions about way(s) to manage CAD data for which the desire is to outsource some work, ongoing. In general, relates to relatively routine changes to mature products (using Windchill change Requests / Notices). Family Tables, top down design, envelope parts, full product structure, etc. involved, so collection is relative a big issue.



Constraint: For now at least, external user does not have access to internal Windchill system.



Brainstormed various ways to approach, all of which seem to have major downsides except possibly these:



1) Use "portable / offline" Workspaces


- Internal user collects from Change Task Affected Objects (or possibly Revise first and collect Resulting Objects).


- Internal user adds to Workspace **** as a shared user account / password ****


- Internal user zips Workspace and sendsto external user.(can this be done??)


- External user accesses Workspaceas a shared user account / password ****makes edits via Check out / in


- External usersendsWorkspaceback to source


- Internal useraccesses Workspaceas a shared user account / password ***, checks work, checks intosource Windchill system



2) Use Windchill Packages


- Internal user collects from Change Task Affected Objects (or possibly Revise first and collect from Resulting Objects).


- Internal user exports Importable Package (requires Windchill license not currently in place)


- Internal user Sends Windchill Package to external user


- External user imports Package to 2nd Windchill system, makes edits via check out / in in external Windchill system


- External user exports Importable Package, sends back to source.


- Internal user imports Package to source Windchill system.





Thinking that surely this must be something that others have addressed, possibly many times over, and there may already be best approach. If the best answer is: Allow external user to access work checked out to a Project in the Source Windchill system, that's ok, but we're currently prevented from doing that.




thanks in advance for thoughts on this.





Mike Lockwood

8 replies

R
RandyJones20-Turquoise
20-Turquoise
March 19, 2015
On 03/19/15 02:19 PM, Mike Lockwood wrote:
>
> Now involved in discussions about way(s) to manage CAD data for which the desire is to outsource
> some work, ongoing.  In general, relates to relatively routine changes to mature products (using
> Windchill change Requests / Notices).  Family Tables, top down design, envelope parts, full
> product structure, etc. involved, so collection is relative a big issue.
>
> Constraint: For now at least, external user does not have access to internal Windchill system.
>
> Brainstormed various ways to approach, all of which seem to have major downsides except possibly
> these:
>
> 1) Use "portable / offline" Workspaces
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and collect
> Resulting Objects).
>
> - Internal user adds to Workspace **** as a shared user account / password ****
>
> - Internal user zips Workspace and sends to external user.(can this be done??)
>

Yep. This is ootb. From the Creo Parametric Server Management dialog simply select the workspace,
rmb, and select "Export Workspace". This will prompt you for a password and then package up the
workspace in a compressed format. Simply send that to the external user.

The external user can then import this by also using the Creo Parametric Server Managment dialog.
And the rest of your steps in this section can happen.
>
> - External user accesses Workspace as a shared user account / password **** makes edits via Check
> out / in
>
> - External user sends Workspace back to source
>
> - Internal user accesses Workspace as a shared user account / password ***, checks work, checks
> into source Windchill system
>
> 2) Use Windchill Packages
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and collect
> from Resulting Objects).
>
> - Internal user exports Importable Package (requires Windchill license not currently in place)
>
> - Internal user Sends Windchill Package to external user
>
> - External user imports Package to 2nd Windchill system, makes edits via check out / in in
> external Windchill system
>
> - External user exports Importable Package, sends back to source.
>
> - Internal user imports Package to source Windchill system.
>
>
> Thinking that surely this must be something that others have addressed, possibly many times over,
> and there may already be best approach.  If the best answer is: Allow external user to access work
> checked out to a Project in the Source Windchill system, that's ok, but we're currently prevented
> from doing that.
>
>
> thanks in advance for thoughts on this.
>
>
>
> Mike Lockwood
>
>
> ----------


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
   Fax: 785-667-2695
------------------------------------------------------------------------

T
TomU23-Emerald IV
23-Emerald IV
March 19, 2015
In order for the external user to import the workspace wouldn’t they also need Windchill? What if they don’t?

R
rnkennedy31-Visitor
1-Visitor
March 19, 2015
ProjectLink works well for off-site contractors, however this would mean that Windchill would need to be accessed from outside, VPN connections would work if feasible.





--

Regards,


Robert N. Kennedy III
R
RandyJones20-Turquoise
20-Turquoise
March 19, 2015
On 03/19/15 02:41 PM, Uminn, Tom wrote:
>
> In order for the external user to import the workspace wouldn't they also need Windchill?
>

Nope. Access to the originating Windchill system is not required.

> What if they don't?
>
> *From:*Randy Jones [
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and
> collect Resulting Objects).
>
> - Internal user adds to Workspace **** as a shared user account / password ****
>
> - Internal user zips Workspace and sends to external user.(can this be done??)
>
>
> Yep. This is ootb. From the Creo Parametric Server Management dialog simply select the workspace,
> rmb, and select "Export Workspace". This will prompt you for a password and then package up the
> workspace in a compressed format. Simply send that to the external user.
>
> The external user can then import this by also using the Creo Parametric Server Managment dialog.
> And the rest of your steps in this section can happen.
>
> - External user accesses Workspace as a shared user account / password **** makes edits via Check
> out / in
>
> - External user sends Workspace back to source
>
> - Internal user accesses Workspace as a shared user account / password ***, checks work, checks
> into source Windchill system
>
> 2) Use Windchill Packages
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and collect
> from Resulting Objects).
>
> - Internal user exports Importable Package (requires Windchill license not currently in place)
>
> - Internal user Sends Windchill Package to external user
>
> - External user imports Package to 2nd Windchill system, makes edits via check out / in in
> external Windchill system
>
> - External user exports Importable Package, sends back to source.
>
> - Internal user imports Package to source Windchill system.
>
> Thinking that surely this must be something that others have addressed, possibly many times over,
> and there may already be best approach. If the best answer is: Allow external user to access work
> checked out to a Project in the Source Windchill system, that's ok, but we're currently prevented
> from doing that.
>
> thanks in advance for thoughts on this.
>
> Mike Lockwood
>
> -----End Original Message-----
>
>
>
>
> --
> ------------------------------------------------------------------------
> Randy Jones
> Systems Administrator
> Great Plains Mfg., Inc.
> 1525 E North St
> PO Box 5060
> Salina, KS USA 67401
> email:- <">mailto:->
> Phone: 785-823-3276
> Fax: 785-667-2695
> ------------------------------------------------------------------------
>
> -----End Original Message-----
> ********** CONFIDENTIALITY NOTICE ********** The information in this email may be confidential
> and/or privileged. This email is intended to be reviewed and used only by the individual or
> organization named above for the explicit purpose of conducting business with Trans-matic Mfg. Co.
> If you are not the intended recipient or an authorized representative of the intended recipient,
> you are hereby notified the any review, dissemination or copying of this email and its
> attachments, if any, or the information contained herein is strictly prohibited, and no privilege
> or protection has been waived. If you have received this email in error, please notify the sender
> immediately by return email and delete this email from your system.
> -----End Original Message-----


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

R
RandyJones20-Turquoise
20-Turquoise
March 19, 2015
On 03/19/15 03:12 PM, Randy Jones wrote:
> On 03/19/15 02:41 PM, Uminn, Tom wrote:
>>
>> In order for the external user to import the workspace wouldn't they also need Windchill?
>>
>
> Nope. Access to the originating Windchill system is not required.

Actually access to any Windchill system is not required.

>
>> What if they don't?
>>
>> *From:*Randy Jones [
>>
>> - Internal user collects from Change Task Affected Objects (or possibly Revise first and
>> collect Resulting Objects).
>>
>> - Internal user adds to Workspace **** as a shared user account / password ****
>>
>> - Internal user zips Workspace and sends to external user.(can this be done??)
>>
>>
>> Yep. This is ootb. From the Creo Parametric Server Management dialog simply select the workspace,
>> rmb, and select "Export Workspace". This will prompt you for a password and then package up the
>> workspace in a compressed format. Simply send that to the external user.
>>
>> The external user can then import this by also using the Creo Parametric Server Managment dialog.
>> And the rest of your steps in this section can happen.
>>
>> - External user accesses Workspace as a shared user account / password **** makes edits via Check
>> out / in
>>
>> - External user sends Workspace back to source
>>
>> - Internal user accesses Workspace as a shared user account / password ***, checks work, checks
>> into source Windchill system
>>
>> 2) Use Windchill Packages
>>
>> - Internal user collects from Change Task Affected Objects (or possibly Revise first and collect
>> from Resulting Objects).
>>
>> - Internal user exports Importable Package (requires Windchill license not currently in place)
>>
>> - Internal user Sends Windchill Package to external user
>>
>> - External user imports Package to 2nd Windchill system, makes edits via check out / in in
>> external Windchill system
>>
>> - External user exports Importable Package, sends back to source.
>>
>> - Internal user imports Package to source Windchill system.
>>
>> Thinking that surely this must be something that others have addressed, possibly many times over,
>> and there may already be best approach. If the best answer is: Allow external user to access
>> work checked out to a Project in the Source Windchill system, that's ok, but we're currently
>> prevented from doing that.
>>
>> thanks in advance for thoughts on this.
>>
>> Mike Lockwood
>>
>> -----End Original Message-----
>>
>>
>>
>>
>> --
>> ------------------------------------------------------------------------
>> Randy Jones
>> Systems Administrator
>> Great Plains Mfg., Inc.
>> 1525 E North St
>> PO Box 5060
>> Salina, KS USA 67401
>> email:- <">mailto:->
>> Phone: 785-823-3276
>> Fax: 785-667-2695
>> ------------------------------------------------------------------------
>>
>> -----End Original Message-----
>> ********** CONFIDENTIALITY NOTICE ********** The information in this email may be confidential
>> and/or privileged. This email is intended to be reviewed and used only by the individual or
>> organization named above for the explicit purpose of conducting business with Trans-matic Mfg.
>> Co. If you are not the intended recipient or an authorized representative of the intended
>> recipient, you are hereby notified the any review, dissemination or copying of this email and its
>> attachments, if any, or the information contained herein is strictly prohibited, and no privilege
>> or protection has been waived. If you have received this email in error, please notify the sender
>> immediately by return email and delete this email from your system.
>> -----End Original Message-----
>
>
> --
> ------------------------------------------------------------------------
> Randy Jones
> Systems Administrator
> Great Plains Mfg., Inc.
> 1525 E North St
> PO Box 5060
> Salina, KS USA 67401
> email:-
> Phone: 785-823-3276
> Fax: 785-667-2695
> ------------------------------------------------------------------------
>
> -----End Original Message-----


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

T
TomU23-Emerald IV
23-Emerald IV
March 19, 2015
“Access to the originating Windchill system is not required.”

I don’t mean the Windchill system. I mean ANY Windchill system. What if they don’t have Windchill at all.

Tom U.
R
RandyJones20-Turquoise
20-Turquoise
March 19, 2015
On 03/19/15 03:16 PM, Uminn, Tom wrote:
>
> "Access to the originating Windchill system is not required."
>
> I don't mean the Windchill system. I mean ANY Windchill system. What if they don't have
> Windchill at all.
>

I realized my earlier reply didn't actually state that so I replied to my own post clarifying this
point. But the answer is the user does NOT need Windchill of any kind for portable workspaces:

> *Subject:* [solutions] - RE: outsourcing CAD work - data managed in Windchill
>
> On 03/19/15 02:19 PM, Mike Lockwood wrote:
>
> Now involved in discussions about way(s) to manage CAD data for which the desire is to
> outsource some work, ongoing. In general, relates to relatively routine changes to mature
> products (using Windchill change Requests / Notices). Family Tables, top down design,
> envelope parts, full product structure, etc. involved, so collection is relative a big issue.
>
> Constraint: For now at least, external user does not have access to internal Windchill system.
>
> Brainstormed various ways to approach, all of which seem to have major downsides except
> possibly these:
>
> 1) Use "portable / offline" Workspaces
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and
> collect Resulting Objects).
>
> - Internal user adds to Workspace **** as a shared user account / password ****
>
> - Internal user zips Workspace and sends to external user.(can this be done??)
>
>
> Yep. This is ootb. From the Creo Parametric Server Management dialog simply select the workspace,
> rmb, and select "Export Workspace". This will prompt you for a password and then package up the
> workspace in a compressed format. Simply send that to the external user.
>
> The external user can then import this by also using the Creo Parametric Server Managment dialog.
> And the rest of your steps in this section can happen.
>
> - External user accesses Workspace as a shared user account / password **** makes edits via Check
> out / in
>
> - External user sends Workspace back to source
>
> - Internal user accesses Workspace as a shared user account / password ***, checks work, checks
> into source Windchill system
>
> 2) Use Windchill Packages
>
> - Internal user collects from Change Task Affected Objects (or possibly Revise first and collect
> from Resulting Objects).
>
> - Internal user exports Importable Package (requires Windchill license not currently in place)
>
> - Internal user Sends Windchill Package to external user
>
> - External user imports Package to 2nd Windchill system, makes edits via check out / in in
> external Windchill system
>
> - External user exports Importable Package, sends back to source.
>
> - Internal user imports Package to source Windchill system.
>
> Thinking that surely this must be something that others have addressed, possibly many times over,
> and there may already be best approach. If the best answer is: Allow external user to access work
> checked out to a Project in the Source Windchill system, that's ok, but we're currently prevented
> from doing that.
>
> thanks in advance for thoughts on this.
>
> Mike Lockwood
>
> -----End Original Message-----
>
>
>
> --
> ------------------------------------------------------------------------
> Randy Jones
> Systems Administrator
> Great Plains Mfg., Inc.
> 1525 E North St
> PO Box 5060
> Salina, KS USA 67401
> email:- <">mailto:->
> Phone: 785-823-3276
> Fax: 785-667-2695
> ------------------------------------------------------------------------
>
> -----End Original Message-----
>
> ********** CONFIDENTIALITY NOTICE ********** The information in this email may be confidential
> and/or privileged. This email is intended to be reviewed and used only by the individual or
> organization named above for the explicit purpose of conducting business with Trans-matic Mfg. Co.
> If you are not the intended recipient or an authorized representative of the intended recipient,
> you are hereby notified the any review, dissemination or copying of this email and its
> attachments, if any, or the information contained herein is strictly prohibited, and no privilege
> or protection has been waived. If you have received this email in error, please notify the sender
> immediately by return email and delete this email from your system.
>
> -----End Original Message-----
>
>
>
>
> --
> ------------------------------------------------------------------------
> Randy Jones
> Systems Administrator
> Great Plains Mfg., Inc.
> 1525 E North St
> PO Box 5060
> Salina, KS USA 67401
> email:- <">mailto:->
> Phone: 785-823-3276
> Fax: 785-667-2695
> ------------------------------------------------------------------------
>
> -----End Original Message-----


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

M
MikeLockwood22-Sapphire IAuthor
22-Sapphire I
March 27, 2015

Have been playing with things. Portable Workspaces seems to be robust, fairly error-proof, flexible, etc. Looks like we'll go ahead with portable workspaces.





Mike Lockwood

Terms & ConditionsAccessibility statement