Manufacturing Hub Integration

General Issues

Saving a Project

Manufacturing Hub Automatic Save (Warmstart) Behavior

Automatic Save (Warmstart) will not occur when a Structure Exposed document is loaded within a DELMIA session, and will be deactivated (if it is turned ON) until the Structure Exposed documents have been unloaded.  When the first automatic save is cancelled, a Warning box is displayed advising that Warmstart has been deactivated and also listing the documents that are stored as Structure Exposed.  Further cancellations of automatic saves won't display any warnings. Once all Structure Exposed documents have been unloaded, a Warning box is displayed advising that Warmstart has been reactivated and documents stored as Structure Exposed have been unloaded.

 In Case of Manufacturing Hub ‘Activity Library’ file (.act) is ‘Structure Exposed’ and hence ‘Automatic Save’ is disabled.

Open Issues

None

 

Documentation

Loading a PPR from a Project

Plantype naming restrictions

When loading data from Manufacturing Hub, an activity type library is created in DPM that corresponds to the Manufacturing Hub plantypeset. All process types in DPM are derived from a base type named "Activity" and you cannot create a new type named "Activity". Due to this DPM restriction, you cannot create a process plantype named "Activity" in the Manufacturing Hub. If a plantype named "Activity" is created in Manufacturing Hub, no objects of this plantype will be loaded in DPM.

Saving with Detailing Data

Reparenting and its Effect on Detailing

When a Manufacturing Hub process with detailing data is moved under a new parent with the Reparent Activity command in DPM, existing simulation data under the process is retained in the new location. For this reason, it is recommended that Reparent Activity is used when a process must be moved.

When a Manufacturing Hub Process with detailing data is moved under a new parent in DPM via other methods, such as drag-and-drop, cut-and-paste or copy-and-paste, the following occurs:

  • The original process and all of its children are deleted
  • A new copy of the process and all of its children are created under the new parent

As the Process and all of its children are newly created, any simulation data under the children of the original process is not retained in the copied processes.

What is Saved Back into the Manufacturing Hub

Process Reparenting in DPM

When a process in a Manufacturing Hub project is reparented in DPM and subsequently saved back to the Manufacturing Hub, the following events occur in Process Engineer:
  • A copy of the original process is created under the new parent
  • The original process is no longer linked to its original parent

Although the original process is no longer linked to the original parent, is not deleted; it is still present in the Project Library with its original name. Objects that were associated to the original process still retain the links to the original process. This results in those objects being linked to two distinct processes of the same name in Process Engineer.

As illustrated in the example below, if Subassembly1 is linked to OP1 and OP1 is then moved to a new parent in DPM, Subassembly1 will be linked to both the original and new copies of OP1 after the project is saved in the Manufacturing Hub:

 

Save of States & Position back to Manufacturing Hub

New 'Manufacturing Positions' and '3D States' created in V5 using the Create Positions  and Create State command respectively, for the products and resources loaded from the Manufacturing Hub will be saved back to Manufacturing Hub. However the association between the 'Manufacturing Positions' and '3D States' created in V5 and their owning products and resources is saved back to the Manufacturing Hub only if products and resources are of an non-organizational plantype.

 New 'Conditions' created using the Define Condition command created for activities which are loaded from the Manufacturing Hub will be saved back to Manufacturing Hub. This is applicable only for activities which are of an non-organizational plantype in the Manufacturing Hub.

Viewing and Editing Current Manufacturing Hub Session Data

Use Implicit Filtering indicates whether the Apply Implicit Filtering option was enabled at the time that the current project was loaded from the Manufacturing Hub. This control is used only to display the implicit filtering status for the loaded project and can not be changed from the Edit Manufacturing Hub Document Info dialog box.

Use Implicit Filtering
is checked if Apply Implicit Filtering was enabled when the project was loaded in V5. If Apply Implicit Filtering was not applied, Use Implicit Filtering is not checked.

Search for a Process, Product, Resource or Work Station Component
The following combobox option has been documented for the PPR Search dialog box:
 
  • NOT LIKE
    Return all components that do not contain the current value in the value field as a substring for the current parameter.

Loading the Manufacturing Context > Volume filter limitations

If the position of the reference product is modified in V5 and subsequently saved back to ENOVIA, the product data must be imported from ENOVIA (incremental import) into the Manufacturing Hub again to update its position information. If the product data is not re-imported, the volumetric filter defined with respect to this reference product will not have its bounding box updated accordingly and the filtering results will not be accurate.

CAA API to access attributes on Parent-Child Link
Since V5R19 SP1 following functionality is available.
The following script-snippet shows how to use the functionality.

Sample Script :

Sub CATMain()

Dim doc as ProcessDocument

set doc = CATIA.ActiveDocument

dim pprdoc as PPRDocument

set pprdoc = doc.PPRDocument

Dim Act1 as Activity

set Act1 = pprdoc.Processes.Item(1)

Set pPRActivity2=Act1.GetItem("Process Plan")

Set pPRActivity3=pPRActivity2.GetItem("Workplan")

set myObj = pPRActivity3.GetItem ("DNBE5PCLINKPROVIDER")

Dim AA as String

myObj.SetStringAttribute "extendedeffectivity", "EE1"

AA = myObj.GetStringAttribute ("extendedeffectivity ")

msgbox AA

End Sub

 

The above script sets the extendedeffectivty attribute value to “EE1” on the Parent-child link between WorkPlan and its parent in the Process tree.

The user can use any of the set/get methods exposed in the IDL ‘DELMIAIPDPDProperty’ to set/get different attributes on the parent-child links.

DNBIPDMutipleClient--Registration.reg
Requirement & Usage

Since R11 GA the following functionality is available

Registry file called DNBIPDMultipleClientRegistration.reg is delivered in <Installation Directory>/intel_a/code/command> folder. This file needs to be run once after the fresh installation of DELMIA V5

This is required to support remote DPE server-DELMIA V5 client connection. In case of DELMIA V5 client, the COM environment is not initialized explicitly. So CoInitializeSecurity method is not called explicitly by the User, but implicitly during the COM initialization process. So to overwrite the default security we need to overwrite the ACL (access control list) in the client’s registry. This is achieved through the above file.

This file registers the security settings for three applications:- DELMIA.exe, CNEXT.exe and DirectLaunch.exe