The Change Management Control options are enabled only when the Manufacturing Hub
project is Change Management (CMC) controlled. Otherwise, these options are shown in a disabled state.
||A separate license controls the availability of the Change Management Control functionality. You must have
this license installed to open a project that is Change Management (CMC) controlled.
If a CMC-enabled project is selected to be loaded and the Open in Read Only Mode
option is not checked, the system checks for the availability of an MCM (Manufacturing Change Management)
product license. If a license is not available, an error message is displayed to indicate that a CMC-enabled
project can not be loaded without an MCM license:
If the license is available, one MCM product license will be checked-out per machine, irrespective of the
number of V5 sessions running on the machine and the number of CMC-enabled projects opened in those sessions.
||For CMC-based projects, all existing action proxies and modification statements will be
accessible. By selecting an action proxy and modification statement, you are able to plan and save only those
activities that are affected objects of the action.
Click the button
next to each option to select an Action Proxy and a Modification Statement.
The Select Action and Modification Statement dialog box is displayed. Click the the drop-down
menus to select an action proxy and a modification statement:
In a CMC enabled project, the action proxy and modification statement can be ignored when loading a project.
However, modifications to the project made from DPM will not be saved back to the Manufacturing Hub.
Note that in a CMC-enabled project, whether an object is versionable or not is determined by the Versionable
attribute in the object's plantype.
When creating new objects in CMC-enabled project
- Non-versionable objects can be created whether the project is opened in CMC mode or not.
- Versionable objects can be created only if a valid action proxy/mod statement is selected at the time the
project is opened.
- Versionable objects cannot be created if an action proxy/mod statement is not selected at the time the
project is opened.
- If a project has been opened by selecting an action proxy/mod statement, any new object created will
automatically have the action proxy/mod statement that was selected when the project was opened.
- In case the parent under which an entity (e.g. process) is created is not in a planning state that allows its
modification (for e.g. if the planning state is not "in-work"), a warning message is displayed at the when the
project is saved. However, the save of the newly created entity does go through fine.
When modifying objects in a CMC-enabled project
- Non-versionable objects can be modified regardless of whether the project is opened with an action proxy/mod
statement or not.
- Versionable objects can be modified only when an action proxy/mod statement has been selected.
- A component can be modified only if the project has been opened with the modification statement with which
the component was created or checked out.
Deleting objects in a CMC-enabled project
- When an object is deleted, the effectivity of the deleted object will be cut (subtracted) by the effectivity
of the modification statement that was selected when the project was opened.
Saving objects in a CMC-enabled project
- If an action proxy/mod statement is not specified when a project is opened, detailing cannot be saved.
- If an action proxy/mod statement is not specified when a project is opened, all non-versionable objects
modified or created will still be saved to the Manufacturing Hub, however all versionable objects modified or
created will not be saved.
- When new versionable objects are created in DPM and saved in the Manufacturing Hub, the following rules are
- The effectivity of the mod statement is copied into the effectivity of the newly created objects
automatically by the Manufacturing Hub server.
- If the versionable object is customized (customization can be done in the plantype of the versionable
object) to be max configured, then the effectivity of the mod statement will not be copied into the newly
- The effectivity of the versionable objects can be overwritten, but the user is then responsible for the