IBM Support

Q&A Guidelines for auto work order creation against custom alerts

Question & Answer


Question

Q1. What is the most likely reason auto work orders are not created when a custom alert is generated?

Q2. What first setting should I verify for the custom alert?

Q3. How do I confirm the alert actually triggered?

Q4. The alert is triggered, but no work order was created. What next?

Q5. What happens if the Device Node ID is missing or incorrect?

Q6. How do I update the Device Node ID correctly?

Q7. How can I confirm the issue is resolved?

Cause

  • Primary cause: Missing or misconfigured Device Node ID in the Asset Master, preventing the system from mapping a triggered custom alert to an asset and therefore blocking automatic work order creation.
  • Other possible contributors: Auto Work Order Creation disabled on the custom alert; alert not actually triggered; asset record missing or inactive; mismatch in device identifiers or formatting.
 

Answer

A1: The most common root cause is a missing or incorrect device node ID in the asset master. Without a valid device node ID, the system cannot map the triggered alert to an asset, so the work order creation process fails.

A2: Check the Custom Alert Settings:

  1. Open the custom alert configuration.
  2. Confirm Auto Work Order Creation is set to Yes.
  3. If it is No, change it to Yes and save the configuration.
A3: Validate on the Alarm Management page:
  1. Search or filter for the custom alert.
  2. Confirm that there is a recorded triggered alert (a timestamped alarm).

 

A4: Verify the asset linkage and device identity:

  1. Open the Asset Master and locate the asset associated with the alert.
  2. Confirm the asset record exists and is active.
  3. Check that the Device Node ID field is populated and matches the device configuration that generated the alert.

A5:If the device ID is missing, the system cannot initiate an asset, and no work order will be generated.

A6: Update procedure:

  1. Identify the device configuration that produced the alert (device identifier from telemetry or alarm details).
  2. Open the corresponding asset record in Asset Master.
  3. Update the Device Node ID to exactly match the device identifier.
  4. Save the asset record.
  5. Wait for the next alert trigger to confirm a work order is created.

A7. Confirmation steps:

  1. Trigger the alert condition (or wait for the next alert trigger).
  2. Verify the alarm appears in Alarm Management.
  3. Check the Work Order queue or work order history for a newly created auto work order linked to the asset.

 

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSV0CLD","label":"IBM Maximo Renewables"},"ARM Category":[{"code":"a8mgJ0000000A93QAE","label":"Operate-\u003EWork Order"}],"ARM Case Number":"TS019436086","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Product Synonym

Maximo Renewables

Document Information

Modified date:
06 May 2026

UID

ibm17270360

Page Feedback