NB	Standard name Name in CAD systems (Feature tree) Filename in the CAD system pool (max. 256 characters) Note The company name [Company name] / catalog name [Catalog name] is not part of the standard designation [Standard name].
SHORTNB	Short name (max. 16 characters) Used by CAD systems that are not compatible with long NB strings
LINA	Description for BOM Name in PARTbom Default designation in ERP systems Note The company name [Company name] / catalog name [Catalog name] is not part of the parts list designation [BOM name].
Identification type	Attribute Declaration Functional feature [Function attribute] Geometric feature [Geometry attribute] Dimensional characteristic [Dimension attribute] Characteristic [Object attribute]

Standard designation [Standard name] ( NB ) and parts list designation [Description for BOM] (LINA ) are declared in the Identification details [Identification data] dialog box (open via PARTdesigner -> File menu [File] -> Identification data [Identification data] or icon .

The standard designation [Standard name] must be unique for all rows and value range entries, i.e. if variable parameters are changed by changing the table row and / or the value ranges and the model is geometrically changed as a result, the NB must also change ; this is the case for stroke and angle positions, changes to dimensions (length, width, height, ...) and for conditional geometric structures of components. When exporting to the CAD system or saving neutral formats, the NB is converted into a file name with the currently set variable parameters.

Example:

Consequence if the NB is not unique: If you want to export a part / assembly from PARTsolutions in the CAD system, the program first searches the parts pool to see if there is already a file that corresponds to the NB to be exported. Only if such a file does not yet exist is the file regenerated by PARTsolutions. If, for example, a cylinder is selected once with a stroke position of 5mm and once with 10mm and the variable of the stroke position is not contained in the NB, no second file is generated and in this case an incorrect part (again with a stroke of 5mm) is created in the CAD system; consequently, it is not possible to manage parts with different stroke positions in the pool!

For this reason, particular importance must be attached to the unambiguousness of the NL. The TestMeta routine locates value ranges that are not contained in the NL, thereby reducing the error rate in advance.

If possible, the parts list designation [Description for BOM] should reflect the order details according to the manufacturer's system.

In any case, the parts list designation [Description for BOM] must be unique.

	Note
	Under no circumstances should stroke and angle positions be added to the parts list designation [Description for BOM], otherwise an order for a new part may be triggered in the ERP for each stroke position!

Example:

	Note
	The LINA often simply refers to the NB (LINA='$NB.'), but this must be avoided at all costs, as errors can occur in the ERP administration if the value ranges of stroke and angle positions (functional characteristics) are incorrectly included.

	Note
	Recommendation: First create LINA. Then set NB='$LINA.' + value ranges.

In the PARTdataManager you can quickly and easily recognize the NB and LINA by the title lines of the table and the 3D view:

Component designation (standard designation [Standard name] / parts list designation [Description for BOM] )

Short form of the Standard name (NB)

The short designation [Short name] (SHORTNB ) is specified in PARTproject in the General tab of the respective part. It essentially corresponds to the NB and its requirements, but it is particularly important to ensure that all unnecessary characters such as hyphens or spaces etc. are removed so that the actual string does not exceed the maximum of 16 characters. This is the only way to ensure functionality in all CAD systems with short permissible strings!

Example:

Short description [Short name]:

D933$D.$L.

Standard designation [Standard name] (NB) for comparison:

Sechskantschraube DIN 933 $NENN.

Example

If the NB in the catalog is generally kept very short (e.g. only consists of an order number), it is also possible to make a direct reference to the NB (SHORTNB=$NB. ).

When creating a value range variable in the variable manager [Variable Manager] ( PARTdesigner ), the correct type identification [Identification type] must be selected for this.

A correct declaration is important, because only then can an error-free conversion of these or the resulting NB and LINA be ensured in the ERP system. Details on this can be found under Section 7.8.14, “ Identification type ”.