Predictika · Token-pool software licence quotes

An AI sales agent's aspenONE token pool quote, checked before it goes out

An AI sales agent prepares an aspenONE token pool quote for a process-industry customer: the AspenTech products the engineers will run, how many of them use each product at the same time, the size of the token pool, the support level, the term, the number of regions that share the pool and the number of tokens the quote says are needed at peak. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of how those choices fit together and returns a verdict, every reason and the totals it computed.

Scope: One aspenONE token pool quote: products and concurrent users, pool size, support, term, regions and the stated peak token need. See everything this validator covers

This validator models aspenONE token pool quotes, not just the scenarios shown below.

  • Engineering products — Aspen HYSYS, Aspen Plus, Aspen HYSYS Dynamics, Aspen Plus Dynamics, Aspen Flare System Analyzer, Aspen Energy Analyzer and Aspen Capital Cost Estimator, with dynamics and flare analysis depending on the base simulator.
  • Manufacturing and supply chain, and asset performance — Aspen Unified PIMS, Aspen DMC3, Aspen Fidelis and Aspen Mtell.
  • Token pool — the peak need is the sum, over the products, of concurrent users times the tokens one user of that product checks out; the pool has to cover it and be at least 50 tokens.
  • Support and term — Premium support is quoted from a 200 token pool, and the term is 12, 24 or 36 months.
  • Approvals — a pool of 1,000 or more tokens, a pool more than twice the peak need, three or more regions and a 12 month term each go to a person.
  • Stated need — the number of tokens the quote says are needed at peak against the number the products need.

Any aspenONE token pool quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: products outside this list and anything priced. This model computes no prices; the figures checked are tokens.

The AI sales agentBuilds the token pool quote from the conversation with the customer and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 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
Products that depend on another productOnly with care
Dynamics needs its base simulator and no more dynamics users than base users, and the flare analyzer is quoted with Aspen HYSYS, so one product choice depends on another.		The dependencies are checked together with the rest of the quote in the same pass.
Token pool against the peak needOnly with workarounds
The peak need adds up concurrent users times the tokens of each product, and the pool has to cover it, be at least 50 tokens and be at least 200 for Premium support.		The need is computed in the same pass and compared with the pool on every call.
A stated need that does not matchOnly with workarounds
The quote states a number of tokens needed at peak, and a validation rule can compare it only if the computed need is available to it.		The stated figure is compared with the computed one on every call.
Approvals that depend on the dealOnly with workarounds
A very large pool, an oversized pool, three or more regions and a 12 month term each send the quote to a person, alongside the blocks.		Blocks and approvals come back together, whatever order the choices arrived in.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
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.

    
1The quoted pool has 133 tokens; the selected products need 134 at peak.
2No product has any concurrent users, so the quote needs no tokens.
3The pool of 100 tokens is more than twice the 0 tokens needed at peak; a person should confirm the sizing.
4This model sells token pools of at least 50 tokens; the quote has 40.
5Aspen HYSYS Dynamics works from Aspen HYSYS models; add Aspen HYSYS users or remove it.
6In this model dynamics concurrent users cannot exceed the concurrent users of the base simulator.
7Aspen Plus Dynamics works from Aspen Plus models; add Aspen Plus users or remove it.
8Aspen Flare System Analyzer is quoted with Aspen HYSYS in this model.
9Premium support is quoted from a 200 token pool in this model; the quote has 199.
10The quote states 120 tokens needed at peak; the selected products need 134.
11Terms in this model are 12, 24 or 36 months; the quote has 48 months.
12A 12 month term needs a sales manager to confirm.
13A pool of 1,000 tokens needs a sales review before the quote goes out.
14Sharing the pool across 3 regions needs a licensing review.

  

  

    
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. Products and support: Dynamics and flare analysis without HYSYS, Premium support on a 60 token pool

    
The agent's request. Please quote an aspenONE token pool for 3 concurrent users of Aspen Plus, 2 concurrent users of Aspen HYSYS Dynamics and 2 concurrent users of Aspen Flare System Analyzer. The pool is 60 tokens across 1 region, with Premium support on a 36 month term. The quote states 62 tokens needed at peak. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Token pool too small. The quoted pool has 60 tokens; the selected products need 62 at peak.
    • 
      
  • HYSYS Dynamics needs Aspen HYSYS. Aspen HYSYS Dynamics works from Aspen HYSYS models; add Aspen HYSYS users or remove it.
    • 
      
  • Dynamics users exceed base users. In this model dynamics concurrent users cannot exceed the concurrent users of the base simulator.
    • 
      
  • Flare System Analyzer needs Aspen HYSYS. Aspen Flare System Analyzer is quoted with Aspen HYSYS in this model.
    • 
      
  • Premium support needs a 200 token pool. Premium support is quoted from a 200 token pool in this model; the quote has 60.
    • 
    

    
2. Products and support: The agent resubmits after fixing the errors

    
The agent's request. Please quote an aspenONE token pool for 3 concurrent users of Aspen HYSYS, 3 concurrent users of Aspen Plus, 2 concurrent users of Aspen HYSYS Dynamics and 2 concurrent users of Aspen Flare System Analyzer. The pool is 200 tokens across 1 region, with Premium support on a 36 month term. The quote states 104 tokens needed at peak. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Pool summary. 104 tokens needed at peak from a pool of 200 tokens across 1 region(s).
    • 
    

    
3. Pool, term and stated need: A 40 token pool, a 48 month term and a wrong stated need

    
The agent's request. Please quote an aspenONE token pool for 4 concurrent users of Aspen Energy Analyzer and 2 concurrent users of Aspen Capital Cost Estimator. The pool is 40 tokens across 1 region, with Standard support on a 48 month term. The quote states 20 tokens needed at peak. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Pool below the minimum. This model sells token pools of at least 50 tokens; the quote has 40.
    • 
      
  • Term not offered. Terms in this model are 12, 24 or 36 months; the quote has 48 months.
    • 
      
  • Stated tokens do not match. The quote states 20 tokens needed at peak; the selected products need 28.
    • 
    

    
4. Pool, term and stated need: The agent resubmits after fixing the errors

    
The agent's request. Please quote an aspenONE token pool for 4 concurrent users of Aspen Energy Analyzer and 2 concurrent users of Aspen Capital Cost Estimator. The pool is 50 tokens across 1 region, with Standard support on a 24 month term. The quote states 28 tokens needed at peak. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Pool summary. 28 tokens needed at peak from a pool of 50 tokens across 1 region(s).
    • 
    

    
5. Pool size and approvals: A manufacturing and asset pool six tokens short, a 12 month term and three regions

    
The agent's request. Please quote an aspenONE token pool for 4 concurrent users of Aspen Unified PIMS, 3 concurrent users of Aspen DMC3 and 2 concurrent users of Aspen Mtell. The pool is 240 tokens across 3 regions, with Standard support on a 12 month term. The quote states 246 tokens needed at peak. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Token pool too small. The quoted pool has 240 tokens; the selected products need 246 at peak.
    • 
      
  • Many regions need sharing review. Sharing the pool across 3 regions needs a licensing review.
    • 
      
  • One-year term needs confirmation. A 12 month term needs a sales manager to confirm.
    • 
    

    
6. Pool size and approvals: The agent resubmits after fixing the errors

    
The agent's request. Please quote an aspenONE token pool for 4 concurrent users of Aspen Unified PIMS, 3 concurrent users of Aspen DMC3 and 2 concurrent users of Aspen Mtell. The pool is 260 tokens across 2 regions, with Standard support on a 24 month term. The quote states 246 tokens needed at peak. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Pool summary. 246 tokens needed at peak from a pool of 260 tokens across 2 region(s).
    • 
    

  

  

    
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 aspenONE token pool quote for a process-industry customer: the AspenTech products the engineers will run, how many of them use each product at the same time, the size of the token pool, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of how those choices fit together and returns a verdict, every reason and the totals it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote an aspenONE token pool for 3 concurrent users of Aspen Plus, 2 concurrent users of Aspen HYSYS Dynamics and 2 concurrent users of Aspen Flare System Analyzer. The pool is 60 tokens across 1 region, with Premium support on a 36 month term. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with five findings, all in one answer. The quoted pool has 60 tokens; the selected products need 62 at peak. Aspen HYSYS Dynamics works from Aspen HYSYS models; add Aspen HYSYS users or remove it. In this model dynamics concurrent users cannot exceed the concurrent users of the base simulator. The other two are on screen.
    6. 
      
  6. The validator returned five 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 token pool against the peak need, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the token pool to 200 tokens and the tokens stated as needed at peak to 104. It sets the Aspen HYSYS to 3.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All five earlier findings are cleared.
    13. 
      
  13. Five problems caught in one call, fixed in one pass, 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.
    14.