About Logical to Physical Synchronization

Logical to Physical Synchronization Manager

The Logical to Physical Synchronization Manager dialog box is composed of various columns and tools.

Columns Description

Element

In the Elements column, all the elements to be synchronized are listed in form of tree structure. The physical elements to be created are displayed as child of the element in which it will be placed after synchronization.

The equipments to be placed, for which physical aggregating product is not known, is added under a separate node Unknown along with it connectors.

Some elements are listed in the Elements list only if its children need to be displayed and synchronized. Some elements which are not to be synchronized will be displayed to maintain the tree structure. The elements with status New are displayed with temporary name because the name of physical created after synchronization may be different. Example: electrical branch geometry, branches, segments.

Modification

The Modification column provides the details of the modification to be performed on the selected element during synchronization.

New: states that the element is to be created in physical.
Modified: states that selected element exist in physical but modified.
Deleted: states that the physical elements do not have link with any logical element.
Warning: states that the elements cannot be synchronized due to missing or incorrect dependencies / information.
Refused by BR: states that the synchronization of the element is refused by the business rule.
Unknown: states that the modification information of an element could not be computed.

Status

The Status column shows the validation performed by you in form of status.

The different status for elements are:

Accepted: for the elements to be synchronized.
Rejected: for the elements not to be synchronized.
To validate: for the elements which are to be created and aggregating product is unknown.
You cannot synchronize the element unless its status is Accepted or Rejected.

Number of Links

The Number of Links column is only available when the Allow instance links between one logical and multiple physical electrical systems option is selected. It indicates the number of links existing between a logical element and a physical element.

Notes:

If a logical element can be linked to only one physical element, the column displays ---.
If a logical element has several links from different sources, the column displays Multiple.

For more information, see Synchronizing a Logical System with Several Electrical Physical Systems.

Tools

Icons

During the Scan Links stage, icons are provided to indicate the link status of a selected element:


Icons	Link Status	Description
	Linked	Indicates that the logical element is already link to a physical element.
	Linked by business rule	Indicates that elements are linked by business rule.
	Linked by user	Indicates that elements are linked manually.
	Unlinked	Indicates that the physical element is not linked to the selected logical element.

Icons and link status correspondence are available in the Legends section of the dialog box.

User Comments

In User Comments, you can add the comments about the modification of elements during synchronization. The user comment about the element will be added to the Synchronization Report, if generated.

Filters

The Logical to Physical command has filters to sort the data systematically.

The filters are provided as a first row for each column except User Comments list.

In the Elements list, you can enter a string to sort the elements by name.
In the Modification list, you can sort the elements by selecting any one of the option available in the list. The list contains all the modification status.
In the Status list, you can sort the elements according to their acceptance or rejected status.

The combination of all these filters also can be used to filter out elements.

Synchronization in an Intermediate Level

By default, logical objects are analyzed in context of the root level. However, when you instantiate assemblies in your product structure and create reference-reference implement links between sub-entities, contextual implement links are searched and created considering this intermediate level.

After an analysis performed in an intermediate level, the results are the following:

The status of the logical children which are part of an instantiated logical system is the same for all its instances.
If any logical component is connected to a child of an instantiated logical system, its corresponding physical element is also connected to the respective physical children.
If the implement link is not found in the first reference-reference link context, the object is considered as New or Modified based on whether the implement link doesn't exist or exists in an upper context level.

Synchronization of Physical Features with Customized Types

The Mapping between logical type and customized feature resource enables to add customized types on physical features created after the synchronization.

You can use this resource to specify default customized types on physical features corresponding to logical objects. During the analysis of logical objects, the resource is used to retrieve the name of customized types to be added on physical features created after the synchronization. For more information, see Available Resources.

Notes:

If a customized type specified in the resource is not found, a warning message appears in the Logical to Physical Synchronization Manager dialog box. This warning does not prevent the creation of physical features.
Customized types are only added on physical features that are created after the synchronization. They are not added on existing physical features.
If several branches corresponding to one single logical pathway are created, they all inherit the same customized type.

To add customized types on conductors corresponding to logical cables, check the Map logical cable to physical conductor option, and customize the Report Custo Attributes from Logical to Corresponding Physical (L2P_ReportAttributes) opening ID.

Equipment Placement

You can instantiate the physical equipment from the logical by setting the business rule.

The logical equipments to be placed through Logical to Physical synchronization needs to be selected from the logical. The physical equipment will be instantiated in the parent product output from business rule opening L2P_ComputeFatherForPlacingEquipment.

If the business rule is not set, the equipment is displayed in analysis page list as separate element with warning and status To Validate. You may select the product in physical tree where equipment needs to be placed.

Right-click the selected element and select Set father. Then select the product in which the equipment is desired. The Logical to Physical Synchronization Manager dialog box appears with status To Validate.

The equipment placement will not be performed, if aggregating product is not given by you either by business rule or by guide selection.

Synchronization of Logical Routables

After a synchronization, physical conductors corresponding to logical routables are created even if the extremities of the conductors are not defined.

The synchronization behavior of logical routables is the following:

If the physical device corresponding to the logical device placed at the extremity of a logical routable is found, the physical device is used to set the From/To extremity of the physical conductor to be created.

If the physical device corresponding to the logical device placed at the extremity of a logical routable is not found, the space assigned to the logical device is used to set the From/To extremity of the physical conductor to be created.

Important: This behavior is possible if:

The space has an electrical behavior.
The space instance is found in the context of the physical root product which is synchronized.

After a synchronization, the extremities of a physical conductor can be modified. In this case, if the Unset the conductor route when the conductor extremities are modified option is selected, the route of the conductor is cleared. For more information, see Conductor Routing.

The following tables detail the various synchronization cases:

Table 1. Creation of physical conductors after the first synchronization
Logical Device	Physical Device	Electrical Behavior on Space	In the context of the Physical Root	Space Cavity	From/To Setting Behavior
Not linked to a space	Found	—	—	—	The physical device is used to define the From/To extremity of the conductor.
Not linked to a space	Not found	—	—	—	A conductor without From/To extremities is created.
Linked to a space	Found	—	—	—	The physical device is used to define the From/To extremity of the conductor.
	Not found	No	No	—	A conductor without From/To extremities is created.
		Yes	No	—	A conductor without From/To extremities is created.
		No	Yes	—	A conductor without From/To extremities is created.
		Yes	Yes	Cavity with matching name NOT found	The space is used to define the From/To extremity of the conductor.
		Yes	Yes	Cavity with matching name found	The cavity of the space is used to define the From/To extremity of the conductor.

Table 2. Creation of physical conductors after subsequent synchronizations
Logical Device	Physical Device	Electrical Behavior on Space	In the context of the Physical Root	Space Cavity	Status of Existing From/To Extremities	From/To Setting Behavior
Not linked to a space	Found	—	—	—	Unchanged: Same physical device as existing device	Unchanged status: No change during synchronization
	Found	—	—	—	Modified: Different physical device from existing device	Modified status: The physical device found after the synchronization is used to define the From/To extremity of the conductor.
	Not found	—	—	—	Unset	Unchanged status: No change during synchronization
	Not found	—	—	—	Modified, and a physical device or space exists.	Modified status: From/To extremities are reset during synchronization.
Linked to a space	Not found	No	—	—	Unset	Unchanged status: No change during synchronization
		No	—	—	Modified, and a physical device or space exists.	Modified status: From/To extremities are reset during synchronization.
		Yes	Yes	Cavity with matching name NOT found	Unchanged: Same space as existing space	Unchanged status: No change during synchronization
				Cavity with matching name NOT found	Modified: Different space from existing space	Modified status: The new space is used to define the From/To extremity of the conductor.
				Cavity with matching name found	Unchanged: Same space and cavity as existing	Unchanged status: No change during synchronization
					Modified: Same space as existing but different cavity from existing	Modified status: The new space cavity is used to define the From/To extremity of the conductor.
					Modified: Different space from existing space	Modified Status: The new space or cavity is used to define the From/To extremity of the conductor.