Creating condition tracked parts - HxGN EAM - Version 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Part Conditions

Search by Category
Feature Briefs
HxGN EAM Version

Just because you are tracking some parts by condition doesn’t mean you need any less functionality than with non-condition tracked parts. You need to be able to track available quantity and price, as well as, issue, return, purchase, receive, and repair these parts as well.

It is for this reason that the various conditions of parts within HxGN EAM are created and tracked using part numbers just as non-conditioned parts are tracked.

You can create a condition tracked part in much the same way as other parts except the new field Track by Condition check box must be checked. This will make the new field Part Condition Template required. The following check boxes on the parent part are cleared and protected when Track by Condition is checked:

  • Fugitive Gas - Greenhouse Gas tab is protected for parent and child parts.

  • Track as Kit - Kit Template tab is protected for parent and child parts (condition tracked parts cannot be a kit template; however, child condition parts can be referenced on the Kit Template tab for a non-condition tracked part that has the Track as Kit check box selected.

  • Average Price

  • Last Price

  • Standard Price

  • Core Value

Next, associate the part condition template to be used to create the new part, populate additional fields as appropriate, and save.

Existing HxGN EAM parts cannot be converted to condition tracked parts. A new part record must be created and identified as a Track by Condition part. However, it is possible to change a condition tracked part back to a non-condition tracked part by unchecking the Track by Condition check box on the parent part in update mode. The system will attempt to delete all associated child parts in addition to clearing and protecting the Part Condition Template field value on the parent part.

The newly created part will be the parent part (Parent Part & Condition are NULL). See the new Condition Details section on the Part record view in the image below for more details. In this example, the part record has been created to represent a motor that will be condition tracked.

When the new part record is saved the system will then perform the following steps:

  1. Create a child part record for each condition on the part condition template associated to the part. In other words, if the part condition template contains four conditions the system will create four child part records in addition to the parent part record created by the user. Part attributes on these child parts will match the parent, except part code and the Prevent Reorders check box.

  2. Child part code will be created using the format <parent part code> + <part condition template suffix separator> + <condition suffix>. See child parts 44A165-A, 44A165-B, 44A165-C, 44A165-D, and 44A165-E in the image below. Notice each child code consists of the parent part 44A165 concatenated with the suffix separator (-) concatenated with the condition suffix from the part condition template. In this way, it is easy to query and identify any child part number if the parent is known or can be found.

  3. Each child part will have its Condition field populated with the corresponding condition code from the associated part condition template. The child part is created to represent and track that part condition. In addition, Parent Part is populated with the parent part code.

  4. The Prevent Reorders check box for each child part will be populated per the Prevent Reorders check box value for the condition on the part condition template used to create the part.

Condition tracked parent parts are simply a record used to manage all the part condition child records. Therefore, parent parts cannot be associated to anything in the system including requisitions lines, PO lines, material lists, etc. In addition, the following cannot be associated to parent part records: stock, bin stock, transactions, etc. All planning, purchasing, and transactions will be against specific part conditions only (i.e., child parts). Parent part numbers will only be used to quickly locate the child parts for which to perform these actions.

Most users will be familiar with the parent part number and, as a result, it will be used to quickly find the part condition (i.e., child part) they are looking for in the system. Note that anytime you select a part condition in the system you are selecting a child part.

In update mode the following occurs:

  • Changes to the following fields on the parent part are cascaded to the child parts while updating these fields directly on the child will be prohibited: Track by Asset, Track by Lot, and Track Cores (formerly Repairable Spare).

  • If the Track by Condition check box is checked on the parent (it is protected on child parts and on the parent part if it is not checked) the system will clear Part Condition Template and delete all associated child parts unless these child parts are associated with other records in the system. This might occur if you made a mistake in creating a condition tracked part and you want to undo this mistake

    It will not be possible to convert a non-condition tracked part into a condition tracked part.

  • If the Part Condition Template field is updated on the parent (it is protected on child parts) the system will delete existing child records, then create new child records per the new part condition template. This might occur if you mistakenly associated the wrong template to the part,

  • If a parent part field is not mentioned as cascading to child parts above, then updates to these fields will not cascade.

  • If a child part field is not mentioned as being protected above, then these fields can be updated independently of the parent.