This functionality is only available for certain module packages. Info / Copyright

Parts Behavior when Selecting Devices

For device selection, the part behavior described below is relevant.

Save parts

Parts can be saved in the project in the following places:

Parts stored in the project

Some part properties (e.g. the purchase price) are needed for calculations in output lists, but shouldn't be provided to the end customer. You can use a configuration dialog to determine which properties should be stored in the project. These properties will then be included when the project is transmitted. Parts properties that are not stored are only available through access to the parts database.

In the Delete stored parts properties dialog you can quickly identify which parts properties are stored in the project. You also have the option of deleting individual properties from the parts stored in the project.

In the Synchronization of parts - <Project name> dialog box you can synchronize the parts stored in the project with the system parts.

Updating device data

Parts and other master data are continuously updated and are, for example, made available via the EPLAN Data Portal. As a result, it is possible that the data of the parts stored in the project change in the parts management. To transfer such changed data into the project, different functionalities are available to synchronize the part and device data:

If the parts in the project are older than in the parts database, the newer data is stored in the project during a parts database synchronization. In addition the newer device data is transfered to the main functions that are using these parts.

During the update or completion of the project, the device data is updated for all parts used. During the parts synchronization only the device data of the selected part. In the process the respective part numbers and part reference data remain unchanged.

Part and device selection of updated parts

Also during the part and device selection of a part that has an older state in the project than in the parts database, an update of the device data takes place at the affected main function. Since the device data is possibly not transfered to all usages of the part in the project (for example, for changed template data), a query is displayed in such cases. You can then decide whether you want to select this updated part or rather another part.

The popup menu item Update device data is available to you in the bill of materials navigator to allow for updating the device data at the functions in the project in such a case nevertheless.

Parts generated from schematic data

The Generate part command allows you to create a part from the schematic data. This part is saved as a part stored in the project. This creates a device in the parts management, i.e. the part and the device data are stored in the database.

You can only do this for the component of a main function. It is only available if exactly one part reference (with a quantity of 1) is entered in the DT.

The part generated in this way contains function templates for all functions of the device.

If the command for a main function is carried out again, you can decide by means of a two-step security prompt whether you want to overwrite only the existing part in the project or also want to update the part master data.

Bill of materials

You can use the stored parts to create a bill of materials containing additional data such as "Description", "Supplier", etc. This bill of materials can be passed on to clients, for example (and contains the additional information) without having to send the entire parts database.

The parts list can be output in different sorted / grouped output lists. Hierarchically structured parts groups can optionally be broken down or output down to a predetermined depth.


Parts with the Quantity = "0" are always output! To avoid this, use a filter.

Panel layout

The parts stored in the devices in the schematic determine the mechanical space requirements on the mounting panel. In parts management (the Mounting data tab), an assignment of order data to the mechanical symbols with scaling information can be managed.


When assigning parts to devices, hierarchical assemblies can be broken down. The information is retained regarding the assembly to which each individual part belongs.

You use the Break up assembly user setting (Options > Settings > User > Management > Part selection) to define if assemblies should be broken up on insertion and to what level this should occur. There is also a Break up assembly project setting (Options > Settings > Projects > "Project name" > Reports > Parts) that you can use to define whether assemblies should be broken up in reports and to what level. If assemblies were broken down during insertion, they can't then be treated as assemblies during reporting.

Parts variants

To support multifunction relays, so-called parts variants can be created in parts management.

If a new part is added to a device and if a function template is contained in that part, then that function template is attached to the device. If a part is removed from a device, then all of the function templates belonging to the part are also removed.

See also