Creating conditions for part condition template - HxGN EAM - Version 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Part Conditions

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1

On the Part Conditions tab, users create all conditions that are valid for the part condition template. There is no setup screen for conditions so that they can simply be associated to a template. Most organizations will maintain a single template; however, many can be created if necessary.

You will use this tab to create/associate the condition to the template in a single save action. Create your conditions by entering the Condition code, Description, and Suffix Code. Once all conditions for the part condition template are associated to the template more information can be entered for each condition. For example, there are numerous fields on the condition record that reference other conditions on the template. These fields can contain one or more conditions from the selected template. A condition value cannot be referenced in one of the lookups until the condition itself has been created for the template.

These fields include the following:

  • Return to Store Condition List - List of valid conditions for which a condition tracked part can be returned to store (with Core Return unchecked) based on the condition in which it was issued. For example, if the part is issued in the 100% life remaining condition, it can be returned to store in the following conditions: having 75% life remaining, 50% life remaining, 25% life remaining, or 0% life remaining. Multiple condition values can be entered here using the multi-select lookup provided or by manually entering the values separated by a comma.

  • Return to Store Condition Default - This is the default condition in which the part will be returned to store based on the condition in which it was issued. This is only the default value and can be changed by the user prior to submitting the transaction. Only a single condition value can be entered here, and it must be listed in the Return to Store Condition List.

  • Core Return Condition List - List of valid conditions for which a condition tracked part can be returned to store (with Core Return checked) based on the condition in which it was issued. For example, if the part is issued in the 100% life remaining condition, it can only be returned to store in the following conditions: having 100% life remaining. Multiple condition values can be entered here using the multi-select lookup provided or by manually entering the values separated by a comma.

  • Core Return Condition Default - This is the default condition in which the part will be returned to store (when Core Return is checked) based on the condition in which it was issued. This is only the default value and can be changed by the user prior to submitting the transaction. Only a single condition value can be entered here, and it must be listed in the Core Return Condition List.

  • Receive Repairs Condition List - List of valid conditions for which a condition tracked part can be received to store based on the condition in which it was placed on an external repair requisition or an internal repair work order. For example, if the part is placed on a requisition or work order in the 100% life remaining condition (but returned for repair), it can be received back into the store in the following conditions: having 75% life remaining, 50% life remaining, 25% life remaining, or 0% life remaining. Multiple condition values can be entered here using the multi-select lookup provided or by manually entering the values separated by a comma.

  • Receive Repairs Condition Default - This is the default condition in which the part will be received to store based on the condition in which it was placed on the requisition or work order. It is only the default value and can be changed by the user prior to submitting the transaction. Only a single condition value can be entered here, and it must be listed in the Receive Repairs Condition List.

In addition, there are two check boxes that define specific behavior for the selected condition:

  • Prevent Reorders - Select this check box to prevent parts in the selected condition from being reordered. For example, when parts are purchased, they are purchased in the ‘new’ condition. The remaining conditions on the template can be flagged to Prevent Reorders so these parts are not available for quotes, requisitions, and POs.

    • Parts flagged to prevent reorders can still be placed on external repair requisitions. They just cannot be purchased direct or for stock.

    • When parts are created in a condition flagged to prevent reorders the value of the condition check box is used as the default Prevent Reorders check box value for the part. However, this value on the part can then be updated if necessary.

  • Prevent Issues - Select this check box to prevent parts in the selected condition from being issued from stock. In most places where parts can be issued in the system parts in these conditions will not be displayed in the Part lookup.

    • It is recommended that conditions identifying the part as in need of repair not be created or used within HxGN EAM. This is because a method of returning a part to store and identifying it as needing repair already exists with the Return for Repair check box (now called Core Return). See Tracking core parts by condition in EAM for details. Checking the Core Return check box remains the method of identifying the part as needing repair which increments the Qty. for Repair (now Core Qty.) of the part, therefore there is no need to used part conditions to identify the need for repair.

    • The ‘*’ condition record (i.e., all conditions) created when the part condition template was created cannot be seen, deleted, or updated on this screen. See the "Add Stores for Condition Tracked Parts" section for more details.

    • All fields on this screen can be updated except for Condition and Suffix Code even after parts have been created using the template. The Prevent Reorders value will not be updated on existing parts for which the part condition template is associated

    • Commas and spaces are not allowed in the Condition field.

    • Do not use a space between values when manually entering condition values into the multi-select fields.

    • The * condition will not be displayed in the multi-select field lookups.

    • A maximum of 10 values can be entered or selected for the multi-select fields.

    • Conditions on the template can be removed except when they are referenced on other condition records for the same template, or the template is associated to a part record.

    • Maximum length of Condition is 20 characters.

    • Suffix Code can only be one character and must be alphabetic (A-Z) or numeric (0-9).

    • Suffix Code for the condition must be unique within the selected template.

    • If a new condition is added to a part condition template after the template has been associated to a part the system will create a child part, corresponding to the newly added condition, for all parts for which the template is associated.

Below is an example of what part conditions might look like and how they can be used. The image shows the conditions and their descriptions. A part will typically start out as New (i.e., 100% of its useful life remaining) but as the part is used it will progress through each of the conditions listed until 0% of its useful life remains. A part can skip conditions through its lifecycle. A part’s condition can change whenever it is returned to stock in good repair, when it is received into stock during a part transfer, or when received following a repair. In addition, a part’s condition can change while it sits in stock on a shelf.

What condition a part is in could be based on the number of times it has been repaired (for core tracked parts), a visual inspection, or any process your organization deems appropriate.