Model Manager should be improved so that it also fully supports CED Drafting. As it is today, users of CED Drafting and CED Modeling have both the Drawing Manager and Model Manager running simultaneously with a high risk of conflict. To run two programs instead of only one also means loss of performance that makes no sense.
Model Manager (MM) and Drawing Manager (DM) are using the *same* executable,
however MM and DM initialize differently.
MM talks to Modeling, DM talks to Drafting, resulting in 2 pairs of executables talking to each other
What you request is a single MM (or whatever you call this) talking to Drafting *and* Modeling.
Well, this is exactly how old Design Management (Workmanager Classic Client) was working,
but for Model Manager/Drawing Manager this would mean a major re-design of the architecture and also the U/I.
Try to imagine how a combined MM/DM U/I should look like ......
There is another reason for the "two executable" design of MM/DM which is Licensing!
Concerning licensing, the Situation is:
- Modeling includes Drafting
- Model Manager includes Drawing Manager
This is implemented by so-called LTU=2 licenses - one license allows to run two executables on the same machine.
These LTU=2 (bündle key) licenses allow to run Modeling+Annotation or Modeling + Drafting on the same machine
The same is true for the Model Manager license - which allows to run 1 x MM and 1 x DM on the same machine.
Combining MM+DM in one single process would be a major challenge for the licensing mechanism because
the "bündle key" licenses only work if two different processes (e.g. MM and DM) are running.
The whole design of MM and DM including the licensing of the product is based on having two separate executables,
as this is the case for Modeling+Annotation or Modeling+Drafting.
Another reason for the "two executable" and against a "single executable" design of MM/DM: Memory!
Model Manager/Drawing Manager is a 32-bit application.
There are already enough situations where MM runs out-of-Memory and terminates.
Today, MM and DM are *two* 32-bit applications, each getting approx. 2 GB of total Memory for C-Heap and Java-Heap
If MM and DM would be combined into *one* single 32-bit application, the risk of running out of Memory would increase significantly.
PTC has communicated years ago that there are definitely no plans for a 64-bit Version of Model Manager.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.