Procurement, Contracts, Receiving & Specialized Inventory: The Complete MAS 9 Supply Chain Backbone
Who this is for: Supply chain managers, procurement specialists, inventory analysts, storeroom supervisors, and Maximo functional consultants who need to understand every procurement, contracting, receiving, and specialized inventory capability in MAS 9 Manage — including the automation, the costing, the lifecycle rules, and the gaps.
Estimated read time: 10 minutes
The Flow You Need to Understand
Before we get into every feature, understand the chain. In MAS 9 Manage, the procurement flow moves like this:
Desktop Requisition
|
v
Purchase Requisition <-- Auto-created from Work Orders
| Auto-created from Reorder Processing
v
Request for Quotation (optional)
|
v
Purchase Order <-- Change Orders for revisions
| Release POs from Contracts
v
Receiving & Inspection
|
v
Inventory (Storeroom) <-- Cost Accounting applied here
Lead Time updated hereEvery link in that chain has configuration depth that matters. Let's walk through each one.
Procurement Module: From Request to Purchase Order
Desktop Requisitions: Self-Service for End Users
Desktop Requisitions are the front door. End users who need materials but are not procurement specialists create purchase requests without procurement involvement.
| Feature | What It Does |
|---|---|
| Self-Service Creation | End users create purchase requests directly — no procurement involvement needed |
| Template Requisitions | Save templates for recurring orders — the same bearings, the same filters, every quarter |
| Frequently Ordered Items | Personal lists of commonly ordered items for quick reorder |
| Status Tracking | Monitor approval progress and receipt status from the desktop requisition itself |
| Auto-PR Creation | Approved desktop requisitions automatically create purchase requisitions for procurement to process |
The key design principle: Desktop Requisitions separate the "I need something" step from the "let me procure it properly" step. The end user says what they need. Procurement decides how to get it.
Purchase Requisitions: The Procurement Engine
Purchase Requisitions are where procurement takes over — and where automation lives.
| Feature | What It Does |
|---|---|
| Auto-Creation from Work Orders | Materials on approved work orders automatically generate PRs — no manual intervention |
| Reorder-Based Creation | Automatic PR generation when inventory drops below the reorder point |
| Direct Issue PRs | PRs for direct issue materials that bypass the storeroom entirely |
| Multi-Vendor Split | A single PR can result in POs to multiple vendors — line items split based on vendor assignment |
| Vendor Pre-Assignment | Optional — PRs can specify a preferred vendor or leave the decision to procurement |
| Approval Workflow | Configurable approval routing based on dollar value, commodity group, organization |
The two automatic creation triggers are critical. When a work order is approved with material requirements, Maximo creates PRs without anyone touching a procurement screen. When reorder processing detects a balance below the reorder point, it creates PRs automatically. These two paths eliminate the most common procurement delay in maintenance organizations: waiting for someone to notice that materials are needed.
Purchase Orders: Execution with Revision Control
Purchase Orders are the formal commitment to a vendor. In MAS 9, the PO application carries the full lifecycle from creation through receipt.
| Feature | What It Does |
|---|---|
| PO from PR | Create PO directly from an approved purchase requisition — copies all unassigned lines |
| Auto-Numbering | Automatic PO number generation or manual entry based on organization preference |
| Delivery Management | Configure delivery location, requested delivery date, payment terms per PO |
| PO Status Tracking | Track pending orders, received quantities, invoicing status |
| Multi-Line POs | Multiple line items per PO with independent delivery tracking per line |
| Change Orders | Modify POs after issuance with full revision tracking — price changes, quantity adjustments, delivery date updates |
| PO Approval Workflow | Configurable approval routing for purchase orders based on value and organizational rules |
| Vendor Integration | POs link to vendor records with contact, site, and payment information |
Change orders deserve emphasis. In many organizations, the initial PO is only the beginning. Quantities change. Delivery dates shift. Prices are renegotiated. MAS 9 tracks every revision against the original PO, maintaining a complete audit trail of what changed, when, and who approved it.
Request for Quotation: Multi-Vendor Competition
RFQs are the competitive sourcing tool. When you need vendor competition — or when policy requires it above a dollar threshold — RFQs formalize the process.
| Feature | What It Does |
|---|---|
| Standalone or Contract-Based | Create RFQs independently or against existing purchase contracts |
| Multi-Vendor Quoting | Send RFQs to multiple vendors — receive quotes on separate tabs for side-by-side review |
| Quote Comparison | Compare unit costs, economic order quantities, and delivery times across vendor responses |
| Award and Convert | Award lines to the winning vendor — create PO or create Contract directly from the RFQ |
| Auto-Close | RFQ automatically closes when all lines are awarded and orders created |
The quote comparison capability is the key value. You send the same line items to five vendors. Each responds with their price, their delivery time, and their minimum order quantity. Maximo puts the responses side by side so procurement can make an informed decision. Award the lines, and the system creates the PO or contract automatically.
Contracts Module: Ten Types for Every Vendor Relationship
MAS 9 supports ten contract types for managing vendor agreements. Each serves a distinct procurement pattern.
| Contract Type | Purpose |
|---|---|
| Purchase Contract | Specific prices and terms for purchasing materials at agreed rates |
| Blanket (Volume) Contract | Total dollar amount agreement — release POs created at specified prices until the blanket is exhausted |
| Pricing Contract | Establish pricing schedules for services or materials without a volume commitment |
| Labor Contract | Define rates for craft and skill combinations — auto-generate invoices for approved labor |
| Lease Contract | Fixed-term equipment leasing with buy-out options at end of term |
| Rental Contract | Equipment rental terminated at will — no fixed term obligation |
| Service Contract | Service delivery terms with per-incident billing capability |
| Warranty Contract | Coverage scope for purchased assets or parts — defines what is covered and for how long |
| Software Contract | Software licensing and maintenance agreements |
| Master Contract | Umbrella contract associating multiple contract types for a single vendor |
The Master Contract is the organizational layer. When you have a vendor relationship that spans materials purchasing, labor services, and software licensing, the Master Contract ties those separate contracts together under one umbrella. Each sub-contract maintains its own terms and enforcement, but the Master provides a single view of the total vendor relationship.
Contract Features That Matter Operationally
| Feature | What It Does |
|---|---|
| Release PO Generation | Create release purchase orders against blanket and volume contracts — each release draws down the contract value |
| Contract Terms Enforcement | The system validates PO pricing against contracted rates — if someone tries to create a PO that exceeds contracted pricing, the system flags it |
| Expiration Management | Track contract expiration dates with notification capability — no more discovering that a critical vendor contract expired three months ago |
| Renewal Workflows | Support for contract renewal and renegotiation — initiate renewal process before expiration |
| Multi-Organization | Contracts can span organizational boundaries — a corporate-level agreement that applies to all sites |
| Vendor Performance | Track vendor performance against contracted SLAs — delivery on time, quality acceptance rates, response times |
Release POs against blanket contracts are worth understanding deeply. Suppose you negotiate a blanket contract with a bearing supplier for $500,000 annually at agreed pricing. Throughout the year, you create release POs against that blanket. Each release draws down the remaining value. Maximo tracks the remaining balance, the number of releases, and whether pricing on each release matches the contracted rates. When the blanket nears exhaustion or expiration, the system notifies procurement to renegotiate.
Receiving & Inspection: Closing the Procurement Loop
Receiving is where the procurement cycle closes. Materials arrive, quantities are validated, quality is inspected, and inventory balances update.
Core Receiving Features
| Feature | What It Does |
|---|---|
| Receive Against PO | Process receipts against specific purchase order lines — the system knows what was ordered and from whom |
| Quantity Validation | Accept less than, equal to, or more than the ordered quantity — tolerance configuration controls how much over-receipt is allowed |
| Inspection on Receipt | Inspect received goods with pass/fail recording — critical for safety-rated materials |
| Put-Away Processing | Assign received items to storage bins with put-away location tracking |
| Rotating Asset Receipt | Creates receipt in a "waiting for asset" status until serialization is complete — because a rotating asset needs an individual asset record before it can be fully received |
| Tolerance Configuration | Define acceptable over-receipt and under-receipt percentages at the organization level |
| Receipt Reversal | Reverse incorrect receipts with full audit trail — for when the wrong quantity was entered or the wrong PO line was selected |
| Multi-Line Receipt | Receive multiple PO lines in a single receipt transaction — the typical scenario when a vendor delivers multiple items on one shipment |
| Void Receipts | Void receipts for items that should not have been received — distinct from reversal in that void implies the receipt should never have happened |
| Receipt History | Complete record of all receiving transactions — who received what, when, against which PO, in what quantity |
MAS 9.1 Receiving Enhancements
MAS 9.1 added meaningful improvements to the mobile receiving experience:
| Enhancement | What Changed |
|---|---|
| Receiving Bin Updates | Update receiving bins and additional item attributes directly upon receipt — no need to go back to the desktop application |
| Enhanced Item Identification | Additional information displayed to help identify items, receipts, and PO data during the receiving process |
| Performance Improvements | Data loading optimizations, enhanced sorting, filtering, and search in the mobile receiving interface |
| Return Processing | Process vendor returns directly from the mobile receiving interface — a workflow that previously required the desktop application |
Specialized Inventory Types: Beyond Standard Stock
MAS 9 Manage supports four specialized inventory types, each with distinct tracking, costing, and management rules.
Rotating Assets: Individual Tracking for Serialized Items
Rotating assets are items that are individually tracked throughout their lifecycle — tools, instruments, serialized spare parts. Every rotating asset has its own asset record with a unique serial number, and it moves between storerooms, locations, and work orders as a tracked individual rather than as fungible stock.
| Feature | What It Does |
|---|---|
| Individual Asset Tracking | Each rotating asset has a unique asset record with serial number — not counted as bulk inventory |
| Location History | Track movement across campus, building, floor, and storeroom over the asset's entire lifecycle |
| Condition Tracking | Monitor condition of tools and instruments over their lifecycle |
| Calibration Integration | Link to calibration work orders for instruments requiring periodic calibration — the system tracks calibration due dates and generates work orders automatically |
| Tool Reservation | Reserve specific tools for upcoming work — ensures the right tool is available when the work order is scheduled |
| Tool Issue and Return | Mandatory personnel recording when issuing tools — you know who has what, and when it was issued |
| Tool Transfer | Transfer tools between storerooms with or without reservations |
| Audit Compliance | Full audit trail for equipment accountability — critical in regulated industries where tool traceability is a compliance requirement |
The calibration integration is where rotating assets connect to the maintenance world. A torque wrench in the tool crib is a rotating asset. It has a calibration schedule. When calibration is due, Maximo generates a work order. When the work order is completed, the calibration record updates. If calibration fails, the tool's status changes. This entire lifecycle is tracked automatically.
Condition-Enabled Items: Multi-Condition Valuation
Condition-enabled items allow the same item number to exist at different quality conditions, each with its own valuation percentage.
| Condition Code | Valuation Percentage | Example |
|---|---|---|
| New | 100% | Factory-fresh replacement pump |
| Good | 80% | Refurbished pump, tested and certified |
| Fair | 40% | Used pump, functional but with wear |
| Poor | 10% | Pump with significant wear, emergency-only use |
| Feature | What It Does |
|---|---|
| Multi-Condition Valuation | Same item at different conditions carries different inventory value — a $1,000 pump in "Good" condition is valued at $800 |
| Condition Codes | Defined at item set level — one code must be 100% (full value) |
| Condition-Based Costing | Inventory value automatically calculated based on condition percentage |
| Condition on Issue | Users must select a condition code when issuing — you cannot issue a condition-enabled item without declaring its condition |
| Condition on Return | Update condition when returning items to the storeroom — a pump that went out as "Good" might come back as "Fair" |
| Permanent Designation | Once inventory exists for a condition-enabled item, the condition-enabled status cannot be reversed — this is permanent |
The permanent designation rule is the one that catches organizations off guard. You enable condition tracking on an item, you add inventory at various conditions, and from that point forward, you cannot turn condition tracking off for that item. Plan this decision carefully.
Consignment Inventory: Vendor-Owned, Your Storeroom
Consignment inventory is stock that the vendor owns but stores in your storeroom. You only pay when you consume it. This model eliminates carrying cost for materials you want available but do not want to own until needed.
| Feature | What It Does |
|---|---|
| Vendor-Owned Stock | Items are owned by the vendor, stocked in your storeroom, paid on consumption |
| Three Invoice Types | CONSUMPTION — auto-generated when items are issued; FREQUENCY — generated periodically on a schedule; MANUAL — triggered manually by procurement |
| Automatic Invoice Generation | The ConsignmentInvoiceCronTask generates invoices based on consumption data automatically |
| Vendor Account Linking | Consignment items are linked to the vendor's consignment account record — all consumption and invoicing traces back to the vendor |
| Configurable Max Lines | Control invoice size through the Organizations application settings — prevents a single invoice from having thousands of lines |
The three invoice types serve different operational models. CONSUMPTION invoicing works for high-volume, high-frequency items where you want real-time billing tied to actual usage. FREQUENCY invoicing works when you negotiate monthly or quarterly billing cycles. MANUAL invoicing works for ad-hoc situations or when invoicing needs review before submission.
Service Items: Procuring Services Through the Materials Workflow
Service items represent purchased services — not physical materials — that flow through the standard procurement workflow.
| Feature | What It Does |
|---|---|
| Service Requisition | Request purchased services through the standard procurement workflow — same PR and PO process as materials |
| Proration Support | Service items can be prorated across cost centers — a maintenance service contract split between three departments |
| Status Management | Service items support the full item status lifecycle |
| Unit of Measure | Define measurement units for services — hours, visits, monthly, per-incident |
Cost Accounting Methods: Five Ways to Value Your Inventory
MAS 9 Manage supports five cost accounting methods, configured at the organization level. The method you choose affects every inventory transaction — issues, receipts, adjustments, and transfers.
| Method | How It Works | When to Use It |
|---|---|---|
| Average Cost | Running average of all purchase costs — each receipt adjusts the average | Default for most organizations — smooths price fluctuations across purchases |
| Last Cost | Most recent purchase price becomes the item cost | Simple — reflects current market pricing, but can cause valuation swings |
| FIFO (First-In-First-Out) | Oldest receipt cost consumed first | Matches physical flow for perishable or date-sensitive items |
| LIFO (Last-In-First-Out) | Most recent receipt cost consumed first | Tax optimization in rising-price environments |
| Standard Cost | Predetermined fixed cost set by finance | Budgeting and variance analysis — actual costs compared against standard |
The Cost Dialog Behavior
When using FIFO or LIFO, Maximo presents a Specify Inventory Costs dialog during balance increases — adjustments, returns, and certain transfers. The dialog requires users to specify which receipt cost applies to the adjustment. This is an operational detail that catches users off guard if they are accustomed to average costing, where adjustments simply update at the running average.
Lead Time Calculation: Dynamic and Self-Correcting
Maximo Manage does not treat lead time as a static number. It dynamically calculates lead times based on actual procurement data, continuously refining the estimate as new purchase orders are received.
The Formula
newLeadTime = currentLeadTime x (1 - recentLeadTimeWeight) + lastPODays x recentLeadTimeWeight| Parameter | What It Is | Typical Value |
|---|---|---|
| Recent Lead Time Weight | How much weight the most recent procurement cycle gets | 20% |
| Historical Weight | Derived as (1 - recentWeight) — how much the historical average counts | 80% |
| lastPODays | Days between PO date and actual delivery date for the most recent order | Calculated per receipt |
How It Works in Practice
Suppose a bearing has a current lead time of 14 days. The most recent PO was placed on March 1 and delivered on March 22 — 21 days. With the default 20% weight:
newLeadTime = 14 x 0.80 + 21 x 0.20
newLeadTime = 11.2 + 4.2
newLeadTime = 15.4 daysThe lead time nudges upward to reflect the longer delivery, but the 80% historical weight prevents a single slow delivery from drastically changing the estimate. Over time, if deliveries consistently take longer, the lead time gradually adjusts. If deliveries speed up, it adjusts downward.
This matters because lead time directly feeds reorder point calculations. A more accurate lead time means reorder triggers at the right moment — not too early (excess inventory) and not too late (stockout).
Item Status Lifecycle: From Planning to Obsolete
Every item in MAS 9 follows a defined status lifecycle. Understanding which statuses allow which operations prevents confusion when items are not available for purchase or issue.
PLANNING --> ACTIVE --> PENDOBS --> OBSOLETE
| ^ ^
v | |
PENDING ------+----------+| Status | Available for Issue/Receipt | Available for Purchase | Can Revert to Active |
|---|---|---|---|
| PLANNING | No | No | Yes |
| PENDING | No — hidden from lookups | No | Yes |
| ACTIVE | Yes | Yes | N/A (already active) |
| PENDOBS | Yes — issue only | No — cannot reorder | Yes |
| OBSOLETE | No | No | No — permanent |
Status Transitions That Matter
PLANNING is for items in the definition phase. You are setting up the item master record, defining specifications, assigning vendors. The item is not available for any transactions.
PENDING is the holding state. The item is defined but not yet approved for use. It is hidden from lookups, so end users cannot see it or request it.
ACTIVE is the operational state. The item is fully available for issue, receipt, purchase, and reorder.
PENDOBS (Pending Obsolescence) is the phase-out state. You can still issue existing stock — you want to deplete what you have — but the system will not create new purchase orders or reorder automatically. This is the "use it up" status.
OBSOLETE is permanent and irreversible. The item is dead. It cannot be issued, received, purchased, or reactivated. Only use this status when you are certain the item will never be needed again. We have seen organizations mark items obsolete prematurely and then discover they need them six months later — at which point the only option is to create a new item record.
Reorder Processing: Automated Replenishment
Reorder processing is MAS 9's automated replenishment engine. When inventory drops below defined thresholds, the system creates purchase requisitions or internal transfer requests automatically.
Reorder Parameters
| Parameter | What It Controls |
|---|---|
| Reorder Point (ROP) | When current balance drops below ROP, the system triggers a reorder |
| Reorder Quantity (ROQ) | Default quantity to order when the reorder is triggered |
| Safety Stock | Minimum inventory level maintained as a buffer — reorder triggers before you reach zero |
| Economic Order Quantity (EOQ) | Calculated optimal order quantity that balances order cost against carrying cost |
| Maximum Stock Level | Upper limit for inventory — prevents over-ordering when multiple reorder triggers fire |
Reorder Types
| Type | How It Works |
|---|---|
| Internal Reorder | Auto-replenish from a designated reorder storeroom — creates an internal transfer request, not a purchase requisition |
| External Reorder | Auto-create a purchase requisition when the reorder is triggered — the PR flows through normal approval and PO creation |
| Multi-Vendor Reorder | Reorder from different vendors based on item-vendor relationships — the system selects the vendor based on configured priority |
Reorder Execution
| Feature | What It Does |
|---|---|
| Reorder Review | Review pending reorders before execution — procurement can approve or modify before PRs are created |
| Cron Task Scheduling | Schedule automatic reorder processing at defined intervals — the REORDER cron task runs on the schedule you configure |
| Batch Processing | Process all items below reorder point in a single cron task execution |
The cron task is the automation heart. You configure the REORDER cron task to run nightly, or every four hours, or whatever cadence matches your operational tempo. Each time it runs, it scans all storeroom items, compares current balance against reorder point (accounting for pending receipts and reservations), and creates PRs for items that need replenishment. No human intervention required for routine reorders.
The RBA Gap: No Purchasing Role-Based Application Yet
This is the gap you need to know about.
MAS 9 has been systematically replacing classic Maximo Work Centers with Role-Based Applications (RBAs) built on the Carbon Design System. For supply chain, three RBAs are available:
| RBA | Status | What It Replaces |
|---|---|---|
| Inventory Count RBA | Available | Inventory Count Work Center |
| Issues and Transfers RBA | Available | Issues and Transfers Work Center |
| Receiving RBA | Available | Receiving Work Center |
| Manage Inventory Work Center | Available | Inventory Management Work Center |
| Purchasing/Procurement RBA | NOT YET AVAILABLE | Purchasing Work Centers |
There is no Purchasing or Procurement RBA as of MAS 9.1. If your organization customized the Purchasing Work Centers in Maximo 7.6, those customizations have no RBA equivalent. All procurement workflows — Purchase Requisitions, Purchase Orders, RFQs, Contracts — require the classic Maximo applications.
This means procurement users do not get the Carbon Design System experience. They do not get the modernized, mobile-friendly interface that inventory users now have. They are still working in the classic application framework.
Plan for this. If your MAS 9 rollout includes procurement training, set expectations that the procurement interface looks and behaves like classic Maximo, not like the modernized RBAs your inventory team is using. IBM has not published a timeline for Procurement RBAs, so plan for classic applications as your procurement interface for the foreseeable future.
Putting It All Together: The Integrated Supply Chain Picture
Here is how all of these capabilities connect in a real operational scenario:
A work order is approved for a pump replacement. The pump item is ACTIVE status, tracked as a rotating asset with condition-enabled valuation. Maximo automatically generates a purchase requisition because the current storeroom balance (one pump in "Fair" condition) does not satisfy the "New" condition requirement on the work order.
The PR routes through approval workflow. Procurement checks for an existing blanket contract with the pump vendor — there is one, with $120,000 remaining. They create a release PO against the blanket, drawing down the contract value.
When the pump arrives, receiving processes it against the PO. Because it is a rotating asset, the receipt enters "waiting for asset" status until the storeroom clerk creates the individual asset record with serial number. The receiving clerk inspects the pump, records pass, and completes the receipt.
The receipt updates three things simultaneously: inventory balance increases, the lead time calculation adjusts based on the days between PO and receipt, and the cost accounting method (average cost) recalculates the item's unit cost.
Meanwhile, the reorder cron task runs overnight. It sees that the storeroom now has two pumps (the new one and the fair-condition one), which is above the reorder point. No PR is generated. But three other items in the same storeroom fell below their reorder points during the day — the cron task creates PRs for all three.
This entire flow — from work order approval through automated procurement, receiving, asset creation, cost update, lead time adjustment, and reorder processing — runs with minimal human intervention. That is the MAS 9 supply chain backbone working as designed.
Key Takeaways
- Procurement flows are deeply automated — work order approval and reorder processing both generate purchase requisitions without manual intervention, and RFQs enable structured multi-vendor competition with side-by-side quote comparison
- Ten contract types cover every vendor pattern — from purchase and blanket contracts with release PO generation and term enforcement, to lease, rental, warranty, and software contracts, all under optional Master contract umbrellas
- Receiving closes the loop with full validation — PO-based receipt, quantity tolerance, inspection, rotating asset receipt with "waiting for asset" status, reversal capability, and MAS 9.1 enhancements for mobile bin updates and return processing
- Specialized inventory goes far beyond standard stock — rotating assets with calibration and tool accountability, condition-enabled items with permanent multi-condition valuation, consignment with three invoice types, and service items with proration
- Cost accounting, lead time, and item lifecycle are interconnected — five costing methods feed inventory valuation, dynamic lead time feeds reorder point accuracy, and the item status lifecycle controls what is available for purchase and issue at every stage
- No Purchasing RBA yet — procurement workflows remain in classic Maximo applications as of MAS 9.1, a gap that affects training, user experience, and mobile access for procurement teams
References
- IBM Maximo Manage 9 — Procurement Documentation
- IBM Maximo Manage 9 — Contracts Documentation
- IBM Maximo Manage 9 — Receiving Documentation
- IBM Maximo Manage 9 — Inventory Configuration
- IBM Maximo Application Suite Documentation
Series Navigation:
Previous: Part 21 — Inventory, Storerooms & Material Flow
Next: Part 23 — Mobile Field Operations & Offline Capabilities
View the full MAS FEATURES series index
Part 22 of the "MAS FEATURES" series | Published by TheMaximoGuys
Procurement, contracts, receiving, and specialized inventory are where Maximo's supply chain depth becomes undeniable. Ten contract types, five cost methods, dynamic lead time, automated reorder, condition-enabled valuation, and consignment invoicing — this is not a lightweight inventory system. It is a full enterprise supply chain platform embedded inside your maintenance management system. The only missing piece is a modern Purchasing RBA, and IBM knows it.
Posam Lakshminarayana