Predictika · Monitoring software license orders

An AI sales agent's monitoring license order, checked before it goes out

An AI sales agent prepares an order for self-hosted SolarWinds Orion Platform licenses: the network (NPM), traffic analysis (NTA), configuration management (NCM) and server and application (SAM) license tiers, the number of things to monitor, and the polling engines. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of SolarWinds' published licensing rules and returns a verdict, every reason and the figures it computed.

Scope: SolarWinds Orion Platform NPM, NTA, NCM and SAM license orders: tiers, monitored counts and polling engines. See everything this validator covers

This validator models self-hosted SolarWinds Orion Platform license orders for NPM, NTA, NCM and SAM, not just the scenarios shown below.

  • NPM and NTA — NPM is licensed by the largest of the nodes, interfaces and volumes to monitor (SL100, SL250, SL500, SL2000 or unlimited SLX); NTA needs NPM and must be at the same license level.
  • NCM and SAM — NCM is licensed by managed devices (DL50 up to DL3000, or unlimited DLX); SAM is licensed either by nodes (SAM10 up to SAM5000) or by component monitors (AL150 to AL2500), or as unlimited; a tier must be a listed tier and large enough for the order; a node count beyond SAM5000 needs SolarWinds sales.
  • Polling engines — one polling engine polls up to 12,000 elements (nodes, interfaces and volumes); each additional polling engine adds that much capacity, and the polling capacity the quote states must equal what the engines on the order cover.

Any self-hosted Orion order that touches these rules is in scope — not only the scenarios pictured here. Polling capacity uses the documented SolarWinds figure of 12,000 elements for one polling engine and counts another 12,000 for each additional engine on the order. Not covered: prices (SolarWinds publishes no price list in the documentation read, so this validator produces no price build-up), other Orion modules, subscription and SolarWinds Observability offerings, maintenance terms, and hardware sizing.

The AI sales agentBuilds the license order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
A license tier set by the largest of several countsOnly with care
The NPM tier depends on the largest of three free-entry counts, so a rule has to compute the maximum and compare it with a tier that is a separate choice; each tier needs its own comparison.		The largest count is computed on every call and compared with the tier chosen.
A second license that must match the firstOnly with care
NTA must be at the same level as NPM; the rule has to compare two product lines and also cover the case where one is missing.		Both levels and the missing-license case are checked together in one request.
A tier that is not a real tierOnly with workarounds
SAM is sold in fixed node tiers and a different set of component tiers; a free-entry size needs a list of valid values per licensing type, kept in step with the documentation.		The valid sizes for the licensing type chosen are part of the model and every size is checked.
Polling capacity that grows with each extra polling engineOnly with workarounds
Total capacity is a multiple of the engines on the order, compared with a count summed from three other lines; a rep often fixes one error and meets the next.		Elements, polling engines and the capacity stated on the quote are computed and compared together.
Stated figures that must match the computed onesOnly with care
A stated figure is a free-entry field; a rule can compare it with the computed capacity, but someone has to write and maintain that comparison.		The stated figure travels with the order and is compared with the computed figure on every call.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1NPM is licensed by the largest of nodes, interfaces and volumes; the largest count is 501 but the NPM tier covers 500.
2NPM is licensed by the largest of nodes, interfaces and volumes; the largest count is 600 but the NPM tier covers 500.
3NPM is licensed by the largest of nodes, interfaces and volumes; the largest count is 101 but the NPM tier covers 100.
4The order has 1,050 nodes, interfaces and volumes to monitor with NPM, but no NPM license.
5NTA licensing follows NPM, but the order has no NPM license.
6The NTA license level must match the NPM license level, and they differ.
7NCM is licensed by managed devices; the order has 201 devices but the NCM tier covers 200.
8The order has 150 devices for configuration management but no NCM license.
9The SAM tier (100) is smaller than the 101 managed nodes or component monitors the order needs.
10350 is not an available SAM license tier for the licensing type chosen.
11The SAM tier (150) is smaller than the 151 managed nodes or component monitors the order needs.
12200 is not an available SAM license tier for the licensing type chosen.
13SAM5000 is the largest listed node tier and the order has 5,200 managed nodes; additional tiers exist but must be arranged with SolarWinds sales.
14The order has servers or component monitors for SAM but no SAM license.
1512,001 monitored elements exceed the 12,000 that the polling engines on the order can poll; one polling engine polls up to 12,000 elements.
1626,000 monitored elements exceed the 24,000 that the polling engines on the order can poll; one polling engine polls up to 12,000 elements.
17The quote states a polling capacity of 48,000 elements, but the polling engines on it cover 36,000.
18The quote states a polling capacity of 6,000 elements, but the polling engines on it cover 12,000.
19NPM is licensed by the largest of nodes, interfaces and volumes; the largest count is 900 but the NPM tier covers 250.
20NCM is licensed by managed devices; the order has 250 devices but the NCM tier covers 200.
21The quote states a polling capacity of 24,000 elements, but the polling engines on it cover 12,000.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Branch network: An order with NPM SL250 and NTA SL500 for 900 interfaces

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SL250 for 220 nodes, 900 interfaces and 240 volumes with NTA SL500. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • NPM tier too small. NPM is licensed by the largest of nodes, interfaces and volumes; the largest count is 900 but the NPM tier covers 250.
    • 
      
  • NTA level differs from NPM. The NTA license level must match the NPM license level, and they differ.
    • 
    

    
2. Branch network: The agent resubmits after fixing the errors

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SL2000 for 220 nodes, 900 interfaces and 240 volumes with NTA SL2000. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 1,360 monitored elements; the polling engines on the order cover 12,000.
    • 
    

    
3. Servers and configuration management: An order with SAM350 and a small NCM tier

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SL500 for 300 nodes, 450 interfaces and 300 volumes; NCM DL100 for 140 devices; SAM licensed by nodes at the 350 tier for 340 servers. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • NCM tier too small. NCM is licensed by managed devices; the order has 140 devices but the NCM tier covers 100.
    • 
      
  • Not a SAM license tier. 350 is not an available SAM license tier for the licensing type chosen.
    • 
    

    
4. Servers and configuration management: The agent resubmits after fixing the errors

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SL500 for 300 nodes, 450 interfaces and 300 volumes; NCM DL100 for 140 devices; SAM licensed by nodes at the 400 tier for 340 servers. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • NCM tier too small. NCM is licensed by managed devices; the order has 140 devices but the NCM tier covers 100.
    • 
    

    
5. Servers and configuration management: The agent resubmits after fixing the errors

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SL500 for 300 nodes, 450 interfaces and 300 volumes; NCM DL200 for 140 devices; SAM licensed by nodes at the 400 tier for 340 servers. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 1,050 monitored elements; the polling engines on the order cover 12,000.
    • 
    

    
6. Large estate: An order with one extra polling engine for 26,000 elements

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SLX for 2000 nodes, 22000 interfaces and 2000 volumes with NTA SLX; NCM DLX for 2500 devices; unlimited SAM for 1800 servers. The order has 1 additional polling engine, and the quote states a polling capacity of 36,000 elements. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Beyond polling engine capacity. 26,000 monitored elements exceed the 24,000 that the polling engines on the order can poll; one polling engine polls up to 12,000 elements.
    • 
      
  • Stated polling capacity differs. The quote states a polling capacity of 36,000 elements, but the polling engines on it cover 24,000.
    • 
    

    
7. Large estate: The agent resubmits after fixing the errors

    
The agent's request. Please quote self-hosted SolarWinds Orion licenses: NPM SLX for 2000 nodes, 22000 interfaces and 2000 volumes with NTA SLX; NCM DLX for 2500 devices; unlimited SAM for 1800 servers. The order has 2 additional polling engines, and the quote states a polling capacity of 36,000 elements. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 26,000 monitored elements; the polling engines on the order cover 36,000.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares an order for self-hosted SolarWinds Orion Platform licenses: the network (NPM), traffic analysis (NTA), configuration management (NCM) and server and application (SAM) license tiers, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of SolarWinds' published licensing rules and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote self-hosted SolarWinds Orion licenses: NPM SL500 for 300 nodes, 450 interfaces and 300 volumes; NCM DL100 for 140 devices; SAM licensed by nodes at the 350 tier for 340 servers. The order has 0 additional polling engines, and the quote states a polling capacity of 12,000 elements. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. NCM is licensed by managed devices; the order has 140 devices but the NCM tier covers 100. 350 is not an available SAM license tier for the licensing type chosen.
    6. 
      
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for a license tier set by the largest of several counts, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the SAM tier to 400.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. NCM is licensed by managed devices; the order has 140 devices but the NCM tier covers 100.
    12. 
      
  12. One finding cleared. Still blocking: NCM tier too small.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the NCM license to DL200.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the quote.
    18. 
      
  18. Two problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    19.