Configuring the RTAM Agent in IBM Sterling OMS for Real-Time Out-of-Stock Alerting

Introduction

The Real-Time Availability Monitor (RTAM) in IBM Sterling OMS is designed to detect inventory shortages quickly and surface actionable out-of-stock alerts. When configured correctly, RTAM continuously evaluates node-level inventory conditions and writes alert data for downstream operational use.

This blog-style guide consolidates the required setup into one implementation path for enterprise teams working with Sterling OMS availability and customer-service workflows.

Prerequisites

• Configured enterprise node in IBM Sterling OMS.
• Access to Application Manager and Business Center.
• At least one fulfillment or distribution node.
• Catalog items available for monitoring.
• Agent Server target available in Process Modeler.
• JMS queue/topic infrastructure provisioned.

Step 1: Create a Distribution Group

Create a dedicated distribution group to define which nodes RTAM will monitor. RTAM uses this group as its node evaluation scope for availability changes.

• Navigate: Cross Application > Order Promising > Sourcing and Scheduling > Product Being Shipped > Distribution Group.
• Create and save a group such as DG_RTAM_MONITOR.
• Add relevant fulfillment nodes and set priority values.
• Save again to persist node mapping.

Step 2: Create an Inventory Monitoring Rule

Configure monitor rules to bind RTAM behavior to the distribution group and define threshold-driven availability signaling behavior.

• Enable activity-based mode for real-time availability monitor.
• Select the distribution group created in Step 1.
• Set relog thresholds to 0.01 to capture granular quantity movements.
• Create an Event-Based ATP Monitor Rule and define high, medium, and low thresholds.

Step 3: Assign Monitor Rule to Items

RTAM does not monitor items automatically. Every monitored item must be explicitly assigned the ATP monitor rule in Business Center.

• Open Product > Fulfillment Information > Manage Inventory Information.
• Set ATP Rule and ATP Monitor Rule fields.
• Set Node Level ATP Monitor Rule to the same monitor rule.
• Save item changes for each tracked SKU.

Step 4: Configure RTAM Agent in Process Modeler

Process configuration activates event handling and schedules RTAM monitor operations that generate near real-time evaluation cycles.

• Activate REALTIME_AVAILABILITY_CHANGE event.
• Add Publish Data action and route to Alert Console destination DEFAULT.
• Set System Id as RTAM in publish configuration.
• Configure REALTIME_ATP_MONITOR_OP1, OP2, and OP3 with matching agent and JMS settings.
• Schedule each operation at 1-minute intervals.
• Set RaiseEventOnAllAvailabilityChanges = Y for all three operations.

Verification Checklist

• Validate alert row creation in YFS_INVENTORY_ALERT after known inventory change.
• Confirm alert visibility in Sterling Call Center out-of-stock views.
• Check OP1/OP2/OP3 execution and error status in agent logs.
• If alerts are missing, re-verify item ATP mapping and trigger criteria configuration.

Conclusion

RTAM configuration is operationally reliable when distribution-group setup, monitoring rules, item-level ATP assignment, and process triggers are treated as one integrated configuration set instead of isolated tasks.

The most common failure points are missing node-level ATP monitor mappings, inactive availability-change events, and inconsistent trigger criteria across OP1/OP2/OP3. Resolving these early significantly improves alert fidelity and operational response.