How HxGN EAM Inventory Management Eliminates Parts-Driven Maintenance Delays

In asset-intensive operations, the most common cause of a planned work order failing to execute on schedule is not a missing technician or a scheduling conflict. It is a missing part. When a mechanic arrives at a job, confirms the failure mode, opens the work order, and then discovers the required component is not in the storeroom – or appears available in the system but cannot be physically located – the job stops. The labour is wasted. The equipment stays down. The maintenance window closes. A delay that was entirely preventable becomes recorded as lost production time.

This pattern repeats across facilities where storeroom management is treated as a logistics afterthought rather than an operational control layer. The underlying problem is rarely that critical parts are inherently hard to source. It is that inventory data is inaccurate, replenishment logic is not configured to account for actual lead times and consumption rates, and work orders are issued without any confirmed verification of parts readiness. HxGN EAM provides a structured inventory management architecture that, when configured correctly, addresses each layer of this failure mode. The system integrates parts master data, storeroom configuration, reorder automation, work order reservation logic, physical count tools, and KPI reporting into a single coherent model. Every layer is interdependent, and maximum value from the inventory module requires understanding how these layers operate and interact.

How HxGN EAM Structures Storeroom and Inventory Data at the System Level

The Parts Form as the Foundation of the Materials Data Model

Every physical stock item in HxGN EAM is defined through the Parts form, which functions as the item master record for the entire materials management module. This record governs the part description, part class, unit of measure, pricing method, and commodity classification. The unit of measure configuration operates at two distinct levels: the inventory unit of measure, which controls how the system tracks and issues stock, and the purchasing unit of measure, which controls how orders are placed with suppliers. As the HxGN EAM documentation on defining units of measure explains, all store transactions are based on inventory units of measure, meaning that when a technician issues a part against a work order, the system deducts in the inventory unit regardless of how the item was received from the supplier. Cable tracked in feet, fasteners tracked individually but ordered by box, lubricants stocked by litre but procured by drum – each scenario requires that both the inventory and purchasing units are correctly defined, with a conversion factor configured between them. Where this configuration is incomplete, the system cannot maintain accurate on-hand balances across receipt and issue transactions.

Stores, Stock Records, and the Role of Bin Assignment

Parts are associated with one or more stores – the HxGN EAM term for a physical storeroom or inventory location – through the Stores tab on the Parts form. Each store association carries its own stock record that includes the bin assignment, quantity on hand, lot number where lot tracking is active, and pricing configuration. As described in the HxGN EAM online help for entering stock information for parts, the system supports lot-level tracking governed by the SHOWLOT installation parameter, and tracks core parts held for internal repair separately from standard stocked quantities. The PRICELEV installation parameter determines whether part prices are recorded at the part level or at the individual stock level within each store, with the default setting of P recording prices at the part level.

The Preferred Store and Preferred Supplier fields on the Stores tab carry direct operational significance. As documented in the HxGN EAM help for viewing and modifying stores associated with parts, Preferred Store designates that automatic requisitions for low-stock items should be fulfilled via store-to-store transfer, while Preferred Supplier routes replenishment to an external procurement workflow. These fields feed the automated requisition generation process and are a prerequisite for the system to generate purchase or transfer requests without manual intervention. Teams that leave these fields blank will find that replenishment does not trigger automatically regardless of how the reorder thresholds are set, which is a common configuration gap in partially deployed HxGN EAM environments.

Reorder Point Configuration and Automated Replenishment in HxGN EAM

Replenishment Methods and Threshold Configuration

The stock replenishment method assigned to each part-store relationship is the primary control that determines whether the system manages restocking proactively or waits for manual action. HxGN EAM supports three replenishment methods on the stock record: Min/Max, Reorder Level, and On-Demand. As the HxGN EAM documentation on managing stock information describes, Min/Max triggers replenishment when the on-hand quantity falls below the minimum level and targets restocking to the maximum level, while Reorder Level uses a single trigger threshold. On-Demand generates a requisition when the part is requested for a work order and no on-hand balance exists.

Setting minimum and maximum levels correctly requires accounting for vendor lead times. The documentation notes that some items may be sourced on 60-day cycles while others replenish within 30 days, and that minimum levels must be set high enough to cover typical consumption during the full lead time period. A common configuration failure is setting minimum levels against average daily consumption without factoring in the maximum probable lead time, which produces a gap between the replenishment trigger and actual delivery. For parts where the purchasing unit of measure differs from the inventory unit, the documentation specifically highlights that if the maximum level is 20 and the minimum is 10 but the item is reordered by the case of 24, the effective stocking levels need adjustment to account for the reorder increment.

EOQ Calculations and Stockout Recording

HxGN EAM includes a native economic order quantity calculation that balances the administrative cost of placing a purchase order against the carrying cost of holding inventory to produce a recommended order quantity per part. As documented through the Generating ABC analysis function in HxGN EAM 11.4, ABC class assignments are used as selection criteria for EOQ calculations, enabling the EOQ process to be run selectively against parts that justify the calculation effort based on their inventory value tier. High-value Class A parts warrant frequent EOQ review; low-value Class C items may use fixed order quantities without meaningful cost impact.

The stock record also supports formal stockout recording, which updates the part’s consumption history when a request cannot be filled from available stock. This is documented in the HxGN EAM 11.3.2 User Guide alongside the EOQ calculation procedure. Organisations that suppress or bypass stockout recording forfeit the historical data that would otherwise allow planners to identify systematic supply failures for specific part categories, and lose one of the primary inputs for validating whether minimum levels are adequate.

The Relationship Between Work Orders and Parts Reservation in HxGN EAM

Parts Planning and Reservation Logic

The connection between work order planning and storeroom execution is managed through the parts reservation and pick ticket functions. As documented in the HxGN EAM help for managing parts for work orders, the Parts tab on the work order record is the interface for adding planned parts, reserving parts, importing a pre-planned parts list from a job plan, creating a purchasing requisition where parts are not in stock, and generating a pick ticket. This tab is the operational handoff between the planning function and the storeroom, and its systematic use is what distinguishes a well-executed planned maintenance programme from one that operates reactively.

When a planner adds a part to a work order and reserves it, the system allocates that quantity against the store’s available balance. The HxGN EAM documentation on issuing parts to work orders confirms that the available quantity displayed at issue time represents the sum of the part’s quantity across all bins in the selected store, minus any quantity currently allocated to other work orders. Where a work order has reserved parts and not all have been issued, a Reserved Items hyperlink is enabled within the issue transaction to retrieve the relevant part lines. This allocation logic prevents two planners from unknowingly scheduling the same unit of a critical spare to two concurrent work orders – a failure mode that routinely produces day-of-maintenance delays in environments where part reservation is not embedded in the planning workflow.

Pick Tickets as the Pre-Staging Control

The pick ticket function formalises the request from the maintenance team to the storeroom to pull and stage parts before the scheduled execution date. As documented in the HxGN EAM help for creating pick tickets, a pick ticket is created from the Parts tab of the work order record. The operator specifies the store, the date by which the parts are needed, and the employee to whom delivery should be made. The system assigns a status of Unfinished by default and populates the total value of the pick ticket as lines are added. Pick ticket management as a standalone function is accessible through Materials > Pick Tickets, as described in the HxGN EAM documentation on defining pick ticket headers, where the class field follows the PICK entity and the pick ticket number is assigned upon saving.

The pre-staging function that pick tickets enable is particularly critical in shutdown and turnaround environments, where multiple work orders execute simultaneously and the storeroom processes dozens of concurrent parts requests. With pick tickets in place, storeroom staff can pull and stage materials during the preceding shift rather than responding to on-the-spot requests from technicians who have already started the job clock. Organisations evaluating where to focus their HxGN EAM configuration investment as part of HxGN EAM implementation and optimisation services consistently find that pick ticket adoption produces rapid, measurable reductions in work order execution delays.

Bin Management, Physical Storeroom Configuration, and Inventory Accuracy Tools

Bin Structure Configuration

Bin-level data is the foundation of accurate available quantity calculations throughout the system. As documented in the HxGN EAM help for creating bins within stores, bin records are created via Materials > Setup > Stores > Bins tab and identify specific physical locations within a store where parts can be stocked. Each bin can be designated for standard stock items or for held items, the latter serving as a quarantine location for parts awaiting inspection or disposition. Bins can be flagged as Out of Service when no stock remains, but only if the recorded on-hand quantity for the location is zero.

The discipline of issuing parts to the correct bin and receiving into the designated location is what keeps on-hand balances accurate at the level of granularity the system requires. In environments where parts are received and put away without updating bin assignments, the system may show stock as available while technicians are unable to physically locate the part. This phantom stock condition directly causes maintenance delays and cannot be resolved by adjusting replenishment parameters. The fix is at the transaction recording level.

Physical Inventory, Discrepancy Reconciliation, and ABC-Driven Count Scheduling

HxGN EAM supports physical inventory counts at the store level, with formal discrepancy reporting available through the Physical Inventory Discrepancy report, which groups count results by store, part, and part organisation and includes a filter for status and null quantities. Where physical counts do not match system balances, the discrepancy reconciliation process corrects the on-hand record, which in turn corrects available quantity calculations for any reservations made against that part.

To prioritise counting effort intelligently, HxGN EAM includes a native ABC analysis function. As documented in the Generating ABC analysis help page for HxGN EAM, the analysis divides stock items into three classes – A, B, and C – based on administrator-specified percentage thresholds for total inventory value. Class A parts represent the largest share of inventory value and are counted most frequently. Class B and C items are counted at lower frequencies proportionate to their value contribution. The ABC class assignments feed directly into EOQ calculations, stock replenishment runs, and physical inventory count scheduling. Running ABC analysis periodically and refreshing count frequencies as consumption patterns shift with production volumes is a foundational inventory hygiene practice that directly protects the accuracy of available quantity data that the reservation and pick ticket functions depend on.

Metrics and KPIs for Measuring Inventory Performance Against Maintenance Outcomes

Native KPI and Reporting Capabilities

HxGN EAM’s Start Center provides a configurable KPI dashboard that system administrators can set to display on login. The HxGN EAM documentation on Start Center KPIs describes the dashboard as user-configurable based on system privileges, with graphical KPI displays driven by user-specified parameters. Storeroom supervisors and maintenance managers can configure views that surface stockout frequency, parts availability at work order release, and requisition-to-receipt cycle times alongside work management indicators such as work order completion rates and planned versus reactive maintenance ratios.

The system’s stock transaction history provides the raw data needed to calculate fill rate – the proportion of parts requests that were satisfied from on-hand stock at the time of request. Tracking fill rate by work order type separates storeroom performance from procurement performance. A low fill rate on planned preventive maintenance work orders points to a replenishment configuration problem: minimum levels are too low, lead times are not accounted for, or replenishment is not automated. A low fill rate on corrective work orders may instead indicate absent strategic spares for asset classes with high failure consequence. These are different problems with different solutions, and the transaction-level data in HxGN EAM makes the distinction traceable.

The Viewing stock levels by part function provides a cross-store view of on-hand quantities, open requisitions, purchase order status, and usage history for any part in the item master. This view is the starting point for periodic replenishment parameter reviews: planners and storeroom supervisors can compare actual consumption rates against the minimum levels currently configured and identify parts where the safety buffer has eroded relative to current lead times.

Connecting Storeroom Transactions to Work Order Performance Data

The HxGN EAM data model links every storeroom transaction – issue, receipt, stockout record, pick ticket, reservation – directly to the work order and asset record it originated from. This linkage enables analysis across the relationship between parts availability failures and work order durations, identifying which asset classes or work order types are most frequently delayed by inventory gaps. Teams that invest in custom SQL reporting against the HxGN EAM database, an approach covered in HxGN EAM SQL query optimisation for asset downtime reporting and KPI calculations, can construct targeted views that correlate stockout events with work order delay hours, producing the evidence base needed to justify safety stock increases, replenishment parameter revisions, or storeroom staffing adjustments for specific part categories.

Inventory performance in HxGN EAM is a continuous calibration process. Minimum levels need periodic review as consumption patterns shift with production volumes and maintenance strategy changes. ABC classifications need updating as new high-value components are added to the asset register. EOQ parameters need refreshing when supplier pricing or lead times change. The system provides every tool required to run this calibration loop effectively, but the loop operates only when configuration is deliberate, transaction recording is disciplined, and the personnel responsible for storeroom management understand both the system mechanics and the operational objectives they are serving.