Supply Chain Overview and Core Inventory: The Foundation of MAS 9 Materials Management

Who this is for: Supply management leads, inventory managers, storeroom personnel, procurement coordinators, and technical teams preparing for the MAS 9 upgrade who need to understand every supply chain capability available -- what is included, what changed, what costs extra, and how the core inventory modules actually work.

Estimated read time: 10 minutes

"We have been running the same storeroom processes since 7.5. Are you telling me there are features we have been ignoring for a decade?"

Yes. And MAS 9 adds new ones on top of everything you already missed. This post covers the entire foundation -- every module, every transaction type, every classification method -- so your supply chain team can finally see the complete picture.

The Three-Tier Supply Chain Architecture

Before diving into individual modules, you need to understand how IBM packages supply chain features in MAS 9. Not everything comes free with the Manage license, and the distinction matters for budget planning.

Tier 1: Included with Manage License

Everything your organization relied on in Maximo 7.6 -- and more -- ships as part of the core Manage application at no additional cost beyond your existing license:

  • Core inventory management -- balances, transactions, bins, lots, multi-currency
  • Item master and item configuration -- all six item types, specifications, vendor associations
  • Storeroom management -- hierarchies, reorder storerooms, GL account association
  • Material reservations -- hard, soft, and backorder reservations
  • Count books and inventory counting -- six selection methods, blind counting, trial reconciliation
  • ABC analysis -- strategic inventory classification with automatic frequency updates
  • Material issues, transfers, and returns -- full lifecycle with shipment management
  • Procurement -- desktop requisitions, purchase requisitions, purchase orders, RFQs
  • Contracts -- all nine contract types
  • Receiving and inspection -- PO-based receiving, inspection recording, put-away
  • Maximo Mobile apps -- Issues and Transfers, Inventory Count, Receiving (all with offline capability)
  • Role-Based Applications -- modernized inventory count, issues/transfers, and receiving interfaces

Tier 2: MAS AppPoints (May Already Be in Your Entitlement)

These suite-level applications consume AppPoints and may already be part of your MAS entitlement. They add intelligence on top of the core supply chain:

  • AI Assist -- generative AI for supply chain guidance and recommendations
  • Parts Identifier -- computer vision for identifying parts from photographs
  • Maximo Health -- asset health scoring that drives spare parts demand
  • Maximo Predict -- machine learning forecasting for failure-driven demand
  • Maximo Monitor -- IoT-triggered supply chain events

Tier 3: Separate Paid SaaS Subscription

One supply chain capability requires an entirely separate purchase:

  • MRO Inventory Optimization -- AI-powered spare parts optimization, starting at $3,094/month

Understanding this three-tier structure is essential. We have seen organizations assume that MRO Inventory Optimization is included with MAS, budget accordingly, and then scramble when they discover it is a separate subscription. We have also seen organizations buy MRO IO when the built-in reorder processing and ABC analysis would have met their needs. Know what you have before you buy what you think you need.

What Changed: 7.6 vs MAS 9 Supply Chain at a Glance

The following comparison table captures every significant change between Maximo 7.6.1.3 and MAS 9 for supply chain operations. Print this. Pin it to the wall of your project war room.

Area — Maximo 7.6.1.3 — MAS 9 — Impact

UI Framework — Classic JSP-based screens — Carbon Design System + Role-Based Applications — All screens modernized; some Work Center customizations need rebuild

Mobile (Inventory) — Maximo Anywhere (requires MAF rebuild/deploy) — Maximo Mobile (native iOS/Android/Windows, server-side config) — No device-side redeployment; offline sync; barcode scanning built-in

Inventory Work Centers — Inventory Count WC, Issues/Transfers WC, Receiving WC — Inventory Count RBA, Issues/Transfers RBA, Receiving RBA — Modernized; some specialized pick list views not yet replicated

Purchasing Work Centers — Purchasing/Procurement Work Centers — Classic applications remain (no RBA replacement yet) — Use classic PO, RFQ, etc. until IBM releases procurement RBAs

AI for Supply Chain — None — AI Assist (GenAI), Parts Identifier (computer vision), Predict (ML forecasting) — Completely new -- not available in 7.6

Inventory Optimization — Manual ROP/MAX calculation — MRO Inventory Optimization (paid SaaS add-on) — AI-powered spare parts optimization -- new product

Count Books — Classic Count Book app — Inventory Counting RBA + Count Book mobile — Modernized with barcode-driven counting

Integration — MIF (SOAP-based primarily) — REST APIs + MIF + Kafka event streaming — Modern API-first architecture

Reporting — BIRT reports — Cognos Analytics + KPI dashboards — All BIRT reports must be recreated

Architecture — WebSphere on-prem — Liberty on OpenShift (containerized) — Cloud-native; scales independently

Java — Java 8/11 — Java 17 — Custom code may need migration

The Critical Gap Your Procurement Team Needs to Know

Purchasing and Procurement RBAs do not exist yet in MAS 9. This is worth repeating because it catches almost every upgrade team off guard. Your procurement team will continue using classic Maximo applications for Purchase Orders, Purchase Requisitions, RFQs, and Desktop Requisitions. Only the inventory side -- Count, Issues/Transfers, Receiving -- has been modernized to Role-Based Applications.

Plan your user training accordingly. Your storeroom staff will learn a completely new interface. Your buyers and procurement specialists will see the Carbon Design System styling but will still navigate classic application patterns underneath.

The Inventory Module: Cornerstone of Supply Chain

The Inventory module is the single most important application in Maximo supply chain management. Everything else -- procurement, receiving, counting, transfers -- feeds into or out of inventory balances. Get this module right and the rest follows. Get it wrong and your storeroom staff will never trust the system.

Core Capabilities

MAS 9 Manage carries forward and extends every inventory capability from 7.6:

Feature — Description

Inventory Balance Tracking — Tracks current and historical balances by item, storeroom, bin, and lot designation

Multi-Storeroom Management — Manage inventory across unlimited storerooms with hierarchical parent-child relationships

Bin Management — Track items at bin-level granularity within storerooms

Lot Tracking — Batch/lot traceability for regulatory compliance and quality assurance

Reservation Management — Hard and soft reservations to prevent stockouts on critical work orders

Cost Tracking — Average cost, last cost, FIFO, LIFO, and standard cost methods

Reorder Processing — Automated reorder point/reorder quantity calculations with safety stock

Cycle Counting — ABC-based cycle count scheduling with configurable frequencies

Transaction History — Complete audit trail of all inventory movements -- issues, receipts, transfers, adjustments

Barcode Integration — Barcode scanning support for issues, transfers, receiving, and counting

Negative Balance Control — Configurable setting to allow or prevent negative available balances

Multi-Currency Support — Handle inventory costs across multiple currencies

The negative balance control setting deserves special attention. In 7.6, many organizations left this permissive because enforcing it meant storeroom staff could not issue materials when the system balance was already zero (even though the physical item was sitting on the shelf). MAS 9 carries the same configuration -- but with better real-time balance visibility through the modernized RBAs, the argument for enforcing negative balance prevention is stronger. If your storeroom balances are consistently off, the problem is not the negative balance setting. The problem is your counting discipline. We will cover that in the count books section.

The Eight Inventory Transaction Types

Every movement of material in Maximo generates a transaction record. Understanding these transaction types is fundamental to reading inventory history and diagnosing balance discrepancies:

Transaction — Description

ISSUE — Issue material from storeroom to work order, location, or GL account

RETURN — Return previously issued material back to storeroom

TRANSFER — Move material between storerooms (with shipment tracking)

RECEIPT — Receive material against a purchase order

ADJUSTMENT — Manual adjustment of inventory balance (up or down)

RECBALADJ — Reconciliation balance adjustment from count book completion

CURBALADJ — Current balance adjustment

INVOICE — Invoice-related inventory transaction

There is also a CONSIGNMENT transaction type for consignment inventory consumption, which we will cover briefly later. But these eight transaction types account for 99% of inventory movement in a typical Maximo environment.

Every transaction records the date, the user, the quantity, the cost, the storeroom, the bin, the GL account debit and credit, and the reference document (work order number, PO number, count book number). This audit trail is permanent and cannot be deleted. When your auditors ask "who moved 47 units of item 12345 on March 3rd and why," the answer is in the transaction history.

Item Master: The Six Item Types

The Item Master application is the primary data governance tool for every item your organization purchases, stocks, or uses. Before a single item enters a storeroom, it must exist in the Item Master -- and the type you assign determines how Maximo handles it throughout its lifecycle.

Standard Item

The default item type. Regular stocked or non-stocked materials -- spare parts, consumables, raw materials, office supplies. No special tracking beyond standard balance management. This covers the vast majority of items in most organizations.

Rotating Item

Individually tracked equipment and tools that circulate between locations and storerooms. Each rotating item has a unique asset record with a serial number. When you issue a rotating item, Maximo does not just decrement a balance -- it moves a specific asset record. When a rotating drill motor is issued to Work Order 54321, you know exactly which serial number went out, who it was issued to, and when it is expected back.

Use cases: calibrated instruments, power tools, test equipment, repairable spares that maintain individual identity.

Condition-Enabled Item

Items tracked at multiple physical condition states -- New, Good, Fair, Poor -- with different valuations for each condition. A repairable pump that costs $5,000 new might be valued at $4,000 in "Good" condition, $2,000 in "Fair," and $500 in "Poor." The system maintains separate inventory balances for each condition code.

Critical detail: once inventory exists for a condition-enabled item, the condition-enabled designation cannot be reversed. Plan your item classification carefully.

Use cases: repairable spares, tires, refurbished components, any item where condition directly affects value.

Lotted Item

Batch-tracked items with unique lot identifiers. Every receipt creates a lot record, and every issue draws from a specific lot. This enables full traceability from vendor shipment through consumption -- essential for regulatory compliance in industries like pharmaceuticals, food processing, and chemical manufacturing.

Use cases: chemicals, lubricants, items with expiration dates or shelf life, any material requiring batch traceability.

Service Item

Purchased services managed alongside materials through the standard procurement workflow. Service items do not have physical inventory balances -- they represent intangible deliverables like grounds maintenance, security patrols, equipment repair services, or consulting hours. They flow through requisitions, purchase orders, and receiving just like physical items, but without storeroom transactions.

Use cases: contract services, repair services, consulting, any purchased service that needs procurement tracking.

Kit Item

A bundle of multiple items issued as a single unit. A preventive maintenance kit might contain five filters, two gaskets, one lubricant container, and a set of O-rings. When you issue the kit, Maximo decrements the balance of every component item. When you define a kit, you specify the component items and their quantities -- the system handles the rest.

Use cases: preventive maintenance kits, safety kits, emergency repair kits, any standard collection of items issued together.

Additional Item Master Features

Beyond item types, the Item Master supports:

  • Alternate Items -- specify substitute items that can replace a primary item when it is out of stock
  • Item Specifications -- define technical specifications and attributes per item
  • Vendor Associations -- link preferred vendors with default pricing
  • Cross-Reference Numbers -- map manufacturer part numbers and vendor part numbers to your internal item number
  • Commodity Codes -- hierarchical classification for spend analysis and sourcing
  • Safety Hazards -- associate safety hazard information visible on mobile devices during issue
  • Tax Code Configuration -- assign tax codes at the item level
  • Item Images -- attach photographs and documentation visible on mobile apps
  • Item Sets -- organization-level groupings for multi-org environments

Storeroom Management: Hierarchies, Bins, and GL Integration

A storeroom in Maximo is not just a physical location. It is a logical inventory container with its own cost method, GL account associations, security controls, and relationships to other storerooms.

Storeroom Features

Feature — Description

Storeroom Hierarchy — Parent-child relationships between storerooms for bulk operations

Reorder Storerooms — Designate internal supplier storerooms for automatic replenishment

GL Account Association — Link storerooms to general ledger accounts for financial tracking

Bin Management — Define storage bins within storerooms with default bins per item

Staging Bins — Designated areas for material picking and staging before shipment

Default Issue Cost — Configure default cost method per storeroom -- Average, Last, FIFO, LIFO, or Standard

Lead Time Weight — Configure how recent vs. historical lead time data weights reorder calculations

Storeroom Access Control — Security groups control who can issue, receive, and transfer within each storeroom

Multi-Site Support — Storerooms belong to specific sites within the organizational hierarchy

Parent-Child Storeroom Hierarchies

The parent-child storeroom relationship is one of the most underutilized features in Maximo. A parent storeroom can have multiple child storerooms. Certain operations can be performed at the parent level and cascade to all children. This is useful when you have a central warehouse that supplies satellite storerooms -- the parent storeroom can serve as the reorder source for its children.

Reorder Storerooms

When an item in Storeroom A drops below its reorder point, Maximo can be configured to automatically generate a transfer request from Storeroom B (the designated reorder storeroom) instead of generating an external purchase requisition. This is how internal replenishment works for organizations with central distribution models.

The reorder storeroom is configured at the item-storeroom level. Item 12345 in Storeroom A might reorder from Storeroom B, while item 67890 in the same storeroom reorders from Storeroom C. The flexibility is at the individual item level.

GL Account Integration

Every storeroom links to GL accounts that drive financial postings. When material is received, the inventory asset account is debited. When material is issued, the inventory asset account is credited and the work order or location cost account is debited. The GL account configuration on the storeroom determines which financial accounts are affected by every transaction.

Getting this wrong means your financial team sees incorrect inventory valuations. Getting it right is usually a one-time configuration effort -- but it requires close collaboration between supply chain and finance during initial setup.

Material Reservations: Hard, Soft, and Backorder

The reservation system prevents the single most frustrating experience in maintenance operations: a technician arrives at a job, opens the work order, walks to the storeroom, and discovers the parts they need were issued to someone else yesterday.

The Three Reservation Types

Type — When Created — Effect on Available Balance — Best For

Hard Reservation — When work order has a required date — Decreases available balance immediately — Critical planned work with firm schedule

Soft Reservation — When no specific date required — No effect on available balance — Long-term planning, future demand visibility

Backorder Reservation — Automatically when hard reservation would cause negative balance — Creates transparent record of material shortfall — Tracking unmet demand

Hard reservations are the enforcement mechanism. When a work order specifies that it needs 3 units of item 12345 on March 25th, a hard reservation immediately decreases the available balance by 3. If the current balance is 10, the available balance drops to 7. Another work order that needs 8 units will see only 7 available -- and if it tries to hard-reserve all 8, the system creates a backorder reservation for the shortfall and triggers the reorder process.

Soft reservations are planning tools. They say "we will need this material eventually" without committing inventory. They are useful for long-range maintenance planning where the exact date is not yet determined.

Reservation Features

Feature — Description

Automatic Creation — Reservations auto-created when materials specified on approved work orders

Manual Creation — Create reservations manually for future work planning

Issue from Reservation — Issue inventory directly from the reservation screen

Rotating Asset Reservation — Reserve specific rotating assets by asset number

Reservation Editing — Modify item type, date, quantity after creation

Reservation Deletion — Remove reservations when work scope changes

Reservation-to-PO Link — When reserved items are not in stock, track the PO that will fulfill the reservation

Cross-Storeroom Visibility — View reservations across storerooms by adjusting filters

The reservation-to-PO link is particularly valuable. When a backorder reservation triggers a purchase requisition, Maximo maintains the link all the way through the procurement cycle. Your planner can see: "Item 12345 is backordered on WO-54321. PR-789 was created. PO-456 was issued to Vendor ABC. Expected delivery: March 28th." That end-to-end visibility is the difference between a reactive supply chain and a managed one.

Count Books and Inventory Counting

Inventory accuracy is the foundation of everything else in supply chain management. If your balances are wrong, your reorder points are meaningless, your reservations are unreliable, and your financial valuations are fictional. Count books are how you keep balances honest.

Count Book Capabilities

Feature — Description

Count Book Creation — Auto-generated ID, storeroom selection, reason code (audit, cycle, ABC, random, ad hoc)

Six Selection Methods — ALL (every item), CNTFREQ (overdue items), and four additional targeted selection approaches

Trial Reconciliation — Automatic comparison of physical count vs. system balance with matched/unmatched indicators

Tolerance-Based Matching — Configure acceptable variance thresholds before items flag as unmatched

Blind Counting — Hide current balance, last count, and last count date fields so counters are not influenced

Rotating Asset Counting — Separate count rows for each rotating asset in the storeroom

Lotted Item Counting — Count by lot with lot-level reconciliation

Condition-Enabled Counting — Count each condition code separately if inventory balances exist

Overdue Count Indicators — Visual indicators for items past their next physical count date

Count Completion — Status change to COMP triggers RECBALADJ transactions that update balances

Count History — Permanent reconciliation transaction records with full audit trail

Count Frequency Tracking — Next count date calculated from last count date plus configured frequency in days

The Six Selection Methods

When creating a count book, you choose which items to include. The six selection methods give you precise control:

  1. ALL -- every item with a balance in the selected storeroom. Use this for annual wall-to-wall physical inventories.
  2. CNTFREQ -- only items whose next count date has passed. This is the workhorse method for cycle counting. Maximo looks at each item's last count date, adds the configured count frequency in days, and includes the item if today's date is past the result.
  3. ABC Type A -- only items classified as Type A. Use this for focused high-value counting.
  4. ABC Type B -- only items classified as Type B.
  5. ABC Type C -- only items classified as Type C.
  6. Ad Hoc / Manual -- manually add specific items to the count book.

In practice, most organizations run CNTFREQ-based count books on a weekly or biweekly cycle. The ABC analysis determines how often each item appears: Type A items might have a 30-day frequency, so they appear in every other CNTFREQ count book. Type C items might have a 90-day frequency, appearing quarterly.

Blind Counting

Blind counting is a best practice that too many organizations skip. When enabled, the system hides the current system balance, last count date, and last count quantity from the person performing the count. The counter records what they physically see on the shelf without being influenced by what the system says should be there.

Without blind counting, a counter who sees "System Balance: 47" and counts 46 items on the shelf will often record 47 -- assuming they miscounted rather than the system being wrong. Blind counting forces honest physical counts. The discrepancies you find are real discrepancies.

The Inventory Counting RBA

MAS 9 replaces the legacy Inventory Count Work Center with the modernized Inventory Counting Role-Based Application. The RBA provides:

  • Streamlined workflows for physical counting
  • Barcode scanning integration
  • Real-time matched/unmatched feedback
  • Offline counting capability via Maximo Mobile
  • Multi-bin counting support
  • Count approval workflow

The mobile counting capability is a significant upgrade from 7.6. Storeroom personnel can take a tablet into the aisles, scan barcodes, enter counts, and sync results -- even in areas with no network connectivity. Counts performed offline sync automatically when the device reconnects.

Trial Reconciliation

After counts are entered, trial reconciliation automatically compares each physical count against the current system balance. Items within the configured tolerance threshold are marked as "matched." Items outside tolerance are marked as "unmatched" and require review before the count book can be completed.

When a count book status changes to COMP (complete), the system generates RECBALADJ transactions for every unmatched item -- automatically adjusting the system balance to match the physical count. These reconciliation adjustments are permanent, auditable records.

ABC Analysis: Strategic Inventory Classification

ABC analysis is not just a counting tool. It is a strategic classification system that determines how much attention and resources each inventory item deserves. The principle is simple: not all items are equal, and treating them equally wastes resources.

The Four Categories

Classification — Typical Value Distribution — Count Frequency — Description

Type A — Top 30% of total value — Most frequent (e.g., every 30 days) — High-value, high-impact items requiring tight control

Type B — Next 30% of total value — Moderate (e.g., every 60 days) — Medium-value items with balanced oversight

Type C — Remaining 40% of total value — Least frequent (e.g., every 90 days) — Low-value items with minimal individual impact

Type N — Excluded from ABC — Per organizational policy — Items exempted from ABC classification updates

Type N is important. Some items should never have their ABC classification changed by an automated report -- critical safety items that must always be counted frequently regardless of their dollar value, or obsolete items that should not influence the distribution curve.

How the Classification Works

Maximo calculates ABC classification by multiplying year-to-date issued quantity by last cost for each item, then sorting the results in descending order. Items in the top 30% of cumulative value become Type A. The next 30% become Type B. The remaining 40% become Type C.

Two reports drive this process:

Report — Function

Inventory ABC Analysis — Multiplies YTD issued quantity by last cost, sorts descending, classifies items

Inventory ABC Transaction Date Analysis — Same classification logic with transaction date filtering

Both reports provide database update functionality that automatically modifies the ABC Type and Cycle Count Frequency fields on inventory records. This means running the report does not just produce a PDF -- it changes the data. Make sure your team understands this before running it in production for the first time.

The count frequencies assigned to each ABC type are configurable at the storeroom level. Your central warehouse might count Type A items every 30 days, while a satellite storeroom counts them every 45 days. The frequency drives the CNTFREQ selection method in count books, creating a self-sustaining cycle: ABC analysis classifies items, classification sets count frequency, count frequency determines which items appear in the next count book.

Issues, Transfers, and Inventory Usage

The Inventory Usage application manages the complete lifecycle of material movements -- getting materials from where they are to where they need to be.

Issue Processing

Feature — Description

Issue to Work Order — Issue materials against specific work orders with material line reference

Issue to Location — Issue materials to a location or GL account

Issue Without Reservation — Issue materials directly without prior reservation

Issue from Reservation — Fulfill existing reservations through the issue process

Rotating Asset Issue — Select specific rotating asset(s) when issuing rotating items

Personnel Assignment — Record who the item is being issued to (mandatory for tools)

Partial Issue — Issue less than the reserved or requested quantity

Multi-Bin Issue — Issue from multiple bins in a single transaction

The distinction between "issue to work order" and "issue to location" matters for cost tracking. Issues to work orders charge the material cost to the work order, making the cost visible in maintenance cost analysis. Issues to a location or GL account charge the cost directly to that financial center. If your maintenance cost reports look incomplete, check whether storeroom staff are issuing to locations instead of work orders.

Transfer Processing: The Four-Stage Lifecycle

Transfers move material between storerooms, and MAS 9 supports a formal multi-stage lifecycle that provides visibility at every step:

ENTERED -- The transfer has been created but no physical action has occurred. Material quantities and destinations are specified. This is the planning stage.

STAGED -- Material has been picked from storage bins and moved to staging bins within the sending storeroom. The system automatically adjusts bin-level balances (decreases storage bin, increases staging bin) while the storeroom-level balance remains unchanged. The material is physically separated and ready for shipment.

SHIPPED -- Material has left the sending storeroom. A shipment record is created with carrier information, packing slips, and shipment line details. The sending storeroom's balance decreases. The material is in transit.

COMPLETE -- The receiving storeroom has processed the incoming transfer through the Shipment Receiving application. The receiving storeroom's balance increases. The transfer is finished.

The intermediate statuses -- STAGED and SHIPPED -- are optional. Organizations with single-building campuses where transfers happen by walking parts down the hall may skip them. But for organizations with geographically distributed storerooms, multiple warehouse locations, or third-party carriers involved in transport, the full lifecycle provides critical visibility into where material actually is at any given moment.

Shipment Management

When a transfer reaches SHIPPED status, Maximo creates a shipment record that includes:

  • Carrier information
  • Packing slip numbers
  • Multiple shipment lines (one transfer can ship in multiple shipments)
  • Expected delivery dates
  • Actual delivery confirmation

The destination storeroom receives the transfer through the Shipment Receiving application -- the same application used for PO-based receiving, adapted for internal transfers. This means your receiving staff uses one consistent process whether material is coming from a vendor or from another storeroom.

Return Processing

Returns reverse previous issues:

Feature — Description

Return to Storeroom — Return previously issued items with automatic balance restoration

Condition Update on Return — For condition-enabled items, update condition code upon return

Rotating Asset Return — Track rotating assets back to inventory with condition assessment

When a rotating asset is returned, the system tracks it back to the storeroom and updates the asset record's location. For condition-enabled items, the returning user specifies the current condition -- a pump that went out as "New" might come back as "Fair" after six months of service, with the corresponding valuation adjustment applied automatically.

Faulty Item Returns

MAS 9 includes a formal return process for items found faulty upon receipt. When material received from a vendor does not meet specifications, the return process creates the documentation trail needed for vendor credit processing and replacement ordering. For transfers, the same mechanism handles items that arrive at the destination storeroom in damaged condition.

Putting It All Together: The Supply Chain Data Flow

Understanding individual modules is necessary. Understanding how they connect is essential.

Here is the complete data flow for a typical maintenance material lifecycle:

  1. Item Master -- the item is defined with its type, specifications, vendor associations, and commodity code
  2. Storeroom -- the item is added to one or more storerooms with reorder points, safety stock levels, bin assignments, and ABC classification
  3. Reservation -- a work order is approved and creates a hard reservation, decrementing available balance
  4. Reorder -- available balance drops below the reorder point, triggering a purchase requisition (or internal transfer from the reorder storeroom)
  5. Procurement -- the requisition becomes a purchase order sent to the vendor
  6. Receiving -- material arrives and is received against the PO, incrementing storeroom balance
  7. Issue -- material is issued to the work order, fulfilling the reservation, decrementing the balance, and charging the cost to the work order
  8. Count -- the next cycle count verifies the balance is accurate, and any discrepancy generates a RECBALADJ transaction
  9. ABC Analysis -- periodic analysis reclassifies items based on consumption patterns, adjusting count frequencies for the next cycle

Every step generates transactions. Every transaction is auditable. Every balance change is traceable to a source document. This is not just inventory management -- it is a closed-loop system that self-corrects through counting and self-prioritizes through ABC analysis.

The organizations that get the most value from MAS 9 supply chain are the ones that let the system work as designed. Use reservations. Enforce reorder points. Run count books on schedule. Let ABC analysis drive your counting frequency. The features are there. They have been there since 7.6 in most cases. MAS 9 makes them more accessible through modernized RBAs and mobile apps -- but the discipline of using them consistently is still on you.

Key Takeaways

  • Three-tier licensing -- core Manage features are included, AI suite features consume AppPoints, and MRO Inventory Optimization is a separate paid subscription. Know which tier each capability falls in before you budget.
  • The procurement RBA gap -- inventory operations have been modernized to RBAs, but procurement has not. Train your teams accordingly.
  • Eight transaction types -- ISSUE, RETURN, TRANSFER, RECEIPT, ADJUSTMENT, RECBALADJ, CURBALADJ, and INVOICE cover every material movement. Understanding these is fundamental to reading inventory history.
  • Six item types -- Standard, Rotating, Condition-Enabled, Lotted, Service, and Kit. The type you assign at item creation determines the item's entire lifecycle behavior.
  • Transfer lifecycle -- ENTERED, STAGED, SHIPPED, COMPLETE provides end-to-end visibility for inter-storeroom movements with full shipment management.
  • Blind counting matters -- hiding system balances from counters produces honest counts. If you are not using blind counting, your count accuracy is probably lower than you think.

References

Series Navigation:

Previous: Part 20 -- Failure Codes and Classification Hierarchies
Next: Part 22 -- Procurement, Contracts, and Receiving

View the full MAS FEATURES series index

Part 21 of the "MAS FEATURES" series | Published by TheMaximoGuys

The supply chain modules in MAS 9 are not new features waiting to be discovered -- they are proven capabilities that have been refined over two decades of Maximo development. What MAS 9 adds is modern interfaces, mobile access, and AI intelligence on top of a foundation that already works. Your job is to make sure your organization actually uses that foundation. Start with accurate balances. Everything else follows.