Manikin Licenses

[JohnMattson]

We recently purchased two of the new Pro/Manikin licenses. When setting up the license file and talking with license management, it turns out that these Manikin licenses have to be tied to a particular machine! I assumed they would be tied to a Pro/E license like most add-ons or extensions are. I don't know of any other add-on modules to Pro/E that are licensed like this. Has anyone else bought a Manikin license and run into this?

Thanks, John

This electronic message including any attachments ("Message") may contain information that is privileged, confidential and/or exempt from disclosure under trade secret and other applicable law. If you are not the intended recipient, notify the sender immediately, permanently delete all copies of this Message, and be aware that examination, use, dissemination, duplication or disclosure of this Message is strictly prohibited.

[ptc-158344]

John,

Other PTC licenses are managed like this. The JT Interface is one and I believe is another is DRM. PTC says this is because they are 3rd-party packages and they have to pay royalties on them.

I fail to understand why this matters; all licenses from PTC should be floating. The cost of these licenses is too high to dedicate to one workstation. To optimize or offset the cost, you have to share the software with other users.

Regards,

Will Swank
CNH America LLC

Principal CAD/PDM Engineer
500 Diller Ave. M/S 640
New Holland, PA, USA 17557-0903

[ptc-1932745]

The basic rule used to be: If the module ended in 'O' it was floatable,
such as 'TDO', Tool Design Option

The others were extensions, these are tied to a particular 'seat' of
pro-e.

Such as 'ISDX', Interactive Surface Design Extension or 'BMX',
Behavioral Modeler Extension



I wouldn't put it past PTC to come up with a third option that ties the
module to the CPU ID, or Network ID, etc... but I think you should check
first.



Manikin is shown in the docs as an extension, so you should be able to
bind each one to a particular 'seat' of Pro-E.



We do this ourselves for Behavioral Modeling Extension (BMX). We have
a particular pro-e launch icon for this configuration.



I believe that most of the 'X' extensions also have floatable 'O' option
versions, but you pay an addition amount for the 'privilege'. I seem to
recall that to have Mathcad as an option vs. extension was something
like an additional $1500 or so. The 'O' options can be enabled and
released as needed from the Tools | Floating Modules Menu picks.



(As an aside to anyone listening from PTC, at this price point we
decided not to purchase Mathcad, because it was of limited use to use as
an extension.)



There is documentation on how to setup pro-engineer to have two or more
'launch' icons that automatically bind these extensions, the down side
is that to release the extension you have to exit pro-e and restart.







Christopher Gosnell

TRIGON INC.
FPD Company
124 Hidden Valley Road
McMurray, PA 15317
PH: 724.941.5540
FX: 724.941.8322
www.fpdinc.com

[PhillipBuckhann]

I'm interested to hear more about this.

We are exploring getting a license or two to be shared among a group of
engineers geographically dispersed. Certainly didn't think this would be an
issue so I am glad the concern has been raised.

Is anyone else running manikin and if so do you know what package you have?
I know there is a Manikin Extension and a Manikin Analysis Extension and I
am beginning to sort through the published differences now in order to
understand them better. If there is a difference between how the two can be
used among a group of engineers that is definitely something I need to
consider. If binding them as described below is an option then it may not
be such a big deal. If it's linked to a specific CPU ID though and can only
run on a single machine it could be a show stopper.

Thanks

Phillip Buckhannon
JLG Industries, Inc.





CGosnell@fpdcompa
ny.com
To
10/09/2009 08:41 -
AM cc

Subject
Please respond to [proecad] - RE: Manikin Licenses
CGosnell@fpdcompa
ny.com








The basic rule used to be: If the module ended in ‘O’ it was floatable,
such as ‘TDO’, Tool Design Option
The others were extensions, these are tied to a particular ‘seat’ of pro-e.
Such as ‘ISDX’, Interactive Surface Design Extension or ‘BMX’, Behavioral
Modeler Extension

I wouldn’t put it past PTC to come up with a third option that ties the
module to the CPU ID, or Network ID, etc… but I think you should check
first.

Manikin is shown in the docs as an extension, so you should be able to bind
each one to a particular ‘seat’ of Pro-E.

We do this ourselves for Behavioral Modeling Extension (BMX). We have a
particular pro-e launch icon for this configuration.

I believe that most of the ‘X’ extensions also have floatable ‘O’ option
versions, but you pay an addition amount for the ‘privilege’. I seem to
recall that to have Mathcad as an option vs. extension was something like
an additional $1500 or so. The ‘O’ options can be enabled and released as
needed from the Tools | Floating Modules Menu picks.

(As an aside to anyone listening from PTC, at this price point we decided
not to purchase Mathcad, because it was of limited use to use as an
extension.)

There is documentation on how to setup pro-engineer to have two or more
‘launch’ icons that automatically bind these extensions, the down side is
that to release the extension you have to exit pro-e and restart.



Christopher Gosnell

TRIGON INC.
FPD Company
124 Hidden Valley Road
McMurray, PA 15317
PH: 724.941.5540
FX: 724.941.8322
www.fpdinc.com

[ptc-1932745]

One other thing that we found when using the 'free' version of Manikin is that after applying the Manikin in ass'y mode, it 'poisons' your pro-e session and you cannot save anything in session, whether it uses Manikin features or not. (WF4 M060).




Christopher Gosnell

TRIGON INC.
FPD Company
124 Hidden Valley Road
McMurray, PA 15317
PH: 724.941.5540
FX: 724.941.8322
www.fpdinc.com

[Chris3]

Mike Campbell said that in a previous thread that it would most likely
be fixed in M110. See here for reference:

[lhughes]

The issue is resolved in M100.

At times you are able to save the assembly changes with Manikin in it,
others, you will need to remove or suppress the Manikin first.

[ecoutu]

In answer to the issue of not being able to save the session when the free manikin has been loaded

PTC is using/proposing a product called: DRM ( Data Right Management). This allows PTC users to protect their geometry. The Manikin product is using this protection. This tool is really efficient to protect your product. it would block all saving activities even if you remove the protected object from your session. After the first implementaiton we realized that it was too restrictive for the manikin and mainly for the manikin light. Therefore we removed to some extent the DRM session saving restriction.

Starting in WF4 M0100 the user will be able to laod the manikin light and manipulate it. The manikin can still no be saved without the license but after removing the manikin from the session. the user will be able to save his session.

Eric