For device selection, the part behavior described below is relevant.
Save parts
Parts can be saved in the project in the following places:
- Parts to be provided in the delivery, general installation materials, and so on, can be assigned directly to the project. Up to 1,000 project parts are allowed.
- Up to 50 part numbers can be assigned to the main function of a device.
- You can put up to 50 parts in one place in the schematic using a part definition point (as you can with every main function).
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 part and 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 for synchronizing the parts data are available:
- Synchronizing the current project (Synchronize command)
- Updating the current project (Update command)
- Completing the current project (Complete command)
- Synchronizing stored parts when opening a project
- Parts data synchronization after changing a project
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. To also transfer the device data into the project for these functionalities, you have to activate the setting Update device data after the storing of parts. In this case the newer device data is additionally transferred to the main functions that use these parts.
During the update or completion of the project, the device data is updated for all parts affected. 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.
Only the data of function templates is transferred during these actions.
Note:
During the assignment of template data of the part to the functions in the schematic the settings in the dialog Settings: Device selection are used.
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. This means for a device selection that in addition to the template data the data of other part properties is also transferred (for example the length of a cable entered at a part). The setting Update device data after the storing of parts has no effect on this update of the device data.
Since the device data is possibly not transferred 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. In addition to template data, part properties are also transferred during a device selection.
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. If subdevices are assigned to the device, the device-specific data of the subdevices is transferred into the part.
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.
Note:
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, an assignment of order data to the mechanical symbols with scaling information can be managed (Hierarchy level Mounting data in the Properties tab).
Assemblies
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 to define whether assemblies should be broken up on insertion and to what level this should occur (File > Settings > User > Management > Part selection). There is also a Break up assembly project setting that you can use to define whether assemblies should be broken up in reports and to what level (File > Settings > Projects > "Project name" > Reports > Part). 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
Synchronizing Stored Parts with the Parts Database