IBM Maximo Inventory Module: In-Depth Explanation

The Inventory module in IBM Maximo Manage is designed to help organizations:

Goal Business Impact, Maximize item availability, Reduce delays in maintenance work due to missing parts Minimize excess inventory, Lower carrying costs and reduce waste Balance stock levels, Keep high-turnover items available while avoiding overstocking seldom-used items

Core Spare-Parts Management Tasks:

• Track stock levels and locations
• Monitor reorder points and automate replenishment alerts
• Create purchase requisitions/orders for restocking
• Manage receipts, issues, returns, and transfers
• Define stocked vs. non-stocked vs. special order items
• Manage tools and condition codes
• Maintain storeroom location data

Item Master Application: The Foundation

The Item Master is the central repository for all items used across Maximo. It enables you to:

Key Capabilities:

✅ Define item attributes (commodity codes, units, lot/rotating/condition-enabled flags)
✅ Specify alternate/substitute items
✅ Assign condition codes and safety hazards (organization-specific)
✅ Create item kits and assembly structures
✅ Manage consignment and tax-exempt items
✅ Attach vendor information and specifications
✅ Link external documents

Item Attributes to Configure:

Attribute Purpose Example

Commodity Code Categorize for reporting/contracts “Pumps > Centrifugal > 5HP”

Order/Issue Units Define purchasing vs. issuing measures Order: CASE, Issue: EACH

Lot Type Track batches/expirations LOT (pharmaceuticals), NOLOT (hardware)

Rotating Flag Serialize assets with common item number PUMP-5HP with 10 serialized instances

Condition-Enabled Track value based on item condition Used/Refurbished/New parts

Consignment Flag Vendor-owned inventory paid on consumption Vendor-managed spare parts

Rotating Items: Serialized Asset Tracking

What Is a Rotating Item?

A rotating item is a serialized asset that shares properties of both inventory items and fixed assets.

Key Characteristics:

• Has a generic item number (e.g., PUMP-5HP) but multiple serialized instances
• Maintains inventory value AND asset tracking
• Cannot be "consumed" — it is maintained, repaired, and relocated
• Tracked by BOTH item number (Inventory) AND asset number (Assets application)
• Cannot also be flagged as a spare part

Practical Example:

Item: FermionT23 (Laptop)
- 10 physical laptops share this item number
- Each laptop is serialized: LAP-001, LAP-002...LAP-010
- When issued to a technician, the specific asset (LAP-005) is tracked
- Inventory balance shows "10 available"; Assets application shows location/status of each

Implementation Workflow:

1. Create item in Item Master → Flag as Rotating
2. Add to storeroom with issue unit/cost
3. Either:

• Create asset records manually in Assets application, OR
• Create PO → Serialize items upon receipt

4. Associate assets with rotating item to enable balance tracking

Item Kits: Bundled Issue Units

Definition:

An item kit is a predefined collection of items issued as a single unit (e.g., “Preventive Maintenance Kit for Pump”).

Key Rules & Constraints:

✅ Kits can contain standard stocked items only
❌ Kits CANNOT contain: rotating items, condition-enabled items, or lotted items
✅ Kits are assembled/disassembled within a SINGLE storeroom only
✅ Kit balance ≠ sum of component balances (components are "consumed" into kit)

How Kits Work:

┌─────────────────────────────────┐
│ Kit: "Pump-PM-Kit"              │
│ Components:                     │
│ • Gasket (Qty: 2)               │
│ • Seal (Qty: 1)                 │
│ • Lubricant 500ml (Qty: 1)      │
└─────────────────────────────────┘

When kit is ASSEMBLED:
→ Kit balance: +1
→ Component balances: -2, -1, -1 respectively

When kit is ISSUED to work order:
→ All components are considered used
→ Technician can return unused components via Disassemble Kit action

Business Value:

• Simplifies work order planning (issue 1 kit vs. 5 separate items)
• Ensures consistent BOM for repetitive tasks
• Streamlines technician workflows

Item Assembly Structures: Hierarchical BOMs

Purpose:

Define the parts/subassemblies required to build an item or define location requirements.

Key Use Cases:

🔧 Rotating Items: Define components of a pump/motor assembly
📦 Item Kits: Specify kit composition (alternative to Kit tab)
🏭 Locations: Define standard equipment required at a location

Critical Rules:

Parent Item Type Allowed Child Items Rotating Item Rotating OR non-rotating items Non-Rotating Item Non-rotating items ONLY Item Kit Standard items ONLY (no rotating/condition-enabled/lotted)

Template Efficiency:

Scenario: 10 identical pump assets need the same subassembly structure

Without Assembly Structure:
→ Manually add 15 components to each of 10 asset records = 150 entries

With Assembly Structure:
→ Create structure ONCE on item PUMP-5HP
→ Copy to all 10 asset records = 15 entries + 10 copy operations

Navigation Tip:

Use the Move To action in the Item Assembly Structure tab to traverse parent/child hierarchies and view nested structures.

Item Master Statuses: Lifecycle Control

Maximo uses status inheritance to control item availability across organizational levels:

Item Level → Organization Level → Inventory (Storeroom) Level

Status Types & Impact:

Status GL Transaction Impact Visibility in Lookups Typical Use Case Pending Blocked for MATUSETRANS, MATRECTRANS, INVTRANS*

❌ Hidden New items awaiting approval Planning Blocked for MATUSETRANS, MATRECTRANS (Issue/Transfer/Receipt)

✅ Visible Items in procurement planning Active

✅ All transactions allowed

✅ Visible Standard operational items Pending Obsolescence

✅ Use existing stock; ❌ Cannot replenish

✅ Visible Phasing out items Obsolete ❌ Blocked except for invoicing/history ❌ Hidden Discontinued items

Status Roll-Down:

When you change an item’s status, use the “Roll New Status to Organizations” checkbox to propagate changes to all dependent organization/inventory records.

Stock Category Types: Reorder Strategy

Three Core Categories:

1. Non-Stocked (NS) Items

• Not kept in regular inventory
• NOT auto-reordered
• Retained in database for:
  - Cost tracking
  - Historical reference
  - Occasional reordering (e.g., annual inspection parts)
Example: Air filters replaced once yearly

2. Special Order (SP) Items

• One-time purchase for unexpected need
• No permanent record required
• Typically deleted after receipt/use
Example: Custom part for emergency repair

3. Stocked (STK) Items Default

• Continuously stocked due to frequent use
• INCLUDED in automated reorder processes
• Require storeroom-specific reorder criteria:
  - Reorder Point (min balance trigger)
  - Economic Order Quantity (optimal order size)
Example: Common bearings, seals, fasteners

Reorder Logic Flow:

Inventory Balance < Reorder Point
       ↓
System flags item for reorder
       ↓
Reorder process generates PR/PO based on:
• Vendor lead time
• Contract pricing
• Economic order quantity

Consignment Items: Vendor-Managed Inventory

Definition:

Items owned by vendors but stored in your storeroom; you pay only upon consumption.

Key Constraints:

❌ Cannot be rotating items
❌ Cannot be condition-enabled items
✅ Must specify Consignment Vendor
✅ Must define Invoice Generation Method

Invoice Generation Methods:

Method Trigger Configuration Consumption Item issued from storeroom Automatic via MATUSETRANS Frequency Scheduled cron task Set frequency/units; ConsignmentInvoiceCronTask runs daily Manual User-initiated Generate invoice via UI action

Accounting Note:

Consignment items use vendor company account settings (not storeroom defaults) for:

• Inventory control account
• Shrinkage cost account
• Cost adjustment account

Meters & Meter Groups: Usage Tracking

Meters on Items:

Associate meters with items to automatically update asset/location readings when items are issued.

Meter Types:

📈 Continuous: Gallons used, running hours, distance traveled
🌡️ Gauge: Temperature, pressure, vibration levels at time of issue
🎨 Characteristic: Color, material grade, certification level

Practical Example: Fuel Tracking

Item: GASOLINE
Meter: FUEL (Continuous, unit: Gallons)

Workflow:
1. Issue 15 gallons of GASOLINE to Truck-101
2. System actions:
   → Storeroom balance: -15 gallons
   → Truck-101 asset record: Fuel meter +15 gallons
   → Work order cost: Updated with fuel expense

Meter Groups: Efficiency at Scale

Scenario: All pumps of type PUMP-5HP need pressure/vibration tracking

Solution:
1. Create Meter Group: "Pump-Monitoring"
   • Inlet Pressure (PSI)
   • Outlet Pressure (PSI)
   • Vibration Level (mm/s)
2. Associate group with rotating item PUMP-5HP
3. Every new pump asset auto-inherits these meters

Tax-Exempt Status: Compliance Flexibility

When Tax-Exempt Applies:

📍 Location-based: Storeroom in tax-free jurisdiction
🔧 Usage-based: Item becomes part of manufactured product (resale exemption)
🏢 Organization policy: Non-profit/government exemptions

Override Capability:

Tax-exempt status can be overridden at transaction level in:

• Purchase Requisitions
• Purchase Orders
• Invoices

Configuration Levels:

Item Level → Organization Level → Vendor Level → Transaction Level
(Lowest precedence)                          (Highest precedence)

Service Items: Managing Non-Physical Procurements

What Are Service Items?

Recurring or one-time services requisitioned through Maximo:

• Grounds maintenance
• Equipment calibration
• Security services
• Consulting hours

Key Features:

✅ Prorate costs across multiple items/work orders
✅ Assign GL accounts for automatic charging
✅ Manage vendor lists per service
✅ Apply same status lifecycle as physical items
✅ Define units of measure (HOURS, VISITS, MONTHS)

Proration Logic:

Without Proration:
• Service cost added to average cost of stocked items
• May distort inventory valuation

With Proration (Prorate checkbox):
• Service cost allocated only to items issued "on receipt"
• Direct issues to WO/GL/Asset carry service cost individually
• Configured in Organizations application

Units of Measure & Conversion Factors

Why Conversions Matter:

Ordering Unit ≠ Issuing Unit ≠ Storeroom Balance Unit

Example: Light Bulbs
• Order: CASE (bulk purchasing)
• Receive: 1 CASE = 36 EACH
• Issue: EACH (technician takes single bulbs)
• Storeroom Balance: Tracked in EACH

Conversion Setup Workflow:

1. Define Units of Measure: CASE, EACH
2. Create Conversion Factor:

• From: CASE → To: EACH Factor: 36 (Optional) Item-specific: BULB-LED-9W

System auto-converts during:

• Receiving (CASE → EACH balance update)
• Issuing (EACH → deduct from balance)
• Transfers (unit validation)

Critical Constraint:

You can delete a Unit of Measure ONLY if it’s not used in:

• Active conversions
• Specification templates
• Meter records

Item Sets: Cross-Organization Standardization

Purpose:

Enable multiple organizations to share a common item catalog while maintaining organizational autonomy.

Architecture:

Company
├── Item Set: "Global-MRO-Items" (shared catalog)
│   ├── Organization A → Uses Global-MRO-Items
│   ├── Organization B → Uses Global-MRO-Items
│   └── Organization C → Uses "Regional-Items" (different set)

Key Rules:

✅ One item set per organization
✅ Multiple organizations can share one item set
✅ Item numbers must be unique WITHIN an item set
✅ New items default to the item set of your default insert site

Practical Implementation Checklist

For Inventory Module Rollout:

Phase 1: Foundation

• [ ] Define commodity groups/codes hierarchy
• [ ] Establish unit of measure library + conversions
• [ ] Configure item sets per organizational structure
• [ ] Set default reorder parameters in Organizations app

Phase 2: Item Master Setup

• [ ] Create item templates for common categories
• [ ] Define status workflows (Pending → Active → Obsolete)
• [ ] Configure tax-exempt rules by organization/vendor
• [ ] Load vendor master data with lead times/pricing

Phase 3: Advanced Features

• [ ] Identify rotating items → create serialization strategy
• [ ] Design item kits for high-frequency work orders
• [ ] Build assembly structures for complex assets
• [ ] Configure consignment agreements with key vendors

Phase 4: Operational Enablement

• [ ] Train storeroom staff on issue/return/transfer workflows
• [ ] Configure reorder alerts and approval workflows
• [ ] Set up meter associations for critical consumables
• [ ] Validate GL account mappings for inventory transactions

Takeaways:

1. Item Master is the single source of truth — invest time in clean, consistent item definitions
2. Status controls workflow — use Pending/Planning statuses to enforce approval gates
3. Kits and assemblies save time but have strict composition rules — document constraints clearly
4. Rotating items bridge inventory and assets — ensure cross-application training for Inventory + Assets teams
5. Conversions prevent data errors — validate unit logic before go-live
6. Consignment requires vendor collaboration — align invoice generation methods contractually

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Contact me on LinkedIn:

https://www.linkedin.com/in/sayed-saeed-ab3286214/

#maximo #Inventory#ItemSet

Full course exists here on Udemy: https://www.udemy.com/course/mastering-ibm-maximo-comprehensive-guide-for-professional/?referralCode=C768555C4F3E0DBB7664