Predictika · Hardware security module quotes

An AI sales agent's HSM appliance quote, checked before it goes out

An AI sales agent prepares a quote for network hardware security modules with partition upgrades, an authentication device and optional modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the product rules and returns a verdict, every reason and the figures it computed.

Scope: Luna Network HSM 7 quotes (A700, A750, A790, S700, S750 and S790) with partition upgrade five-packs, Functionality Modules, PED authentication and high-availability groups. See everything this validator covers

This validator models Luna Network HSM 7 appliance quotes, not just the scenarios shown below.

  • Model limits — base partitions, the most partition upgrade five-packs, and secure memory for each model, checked against what the customer needs and what the quote states.
  • Authentication — S-series models use PED (multifactor) authentication, so the quote needs a Luna PED, new or existing; an existing PED goes to a person to confirm.
  • Options and groups — Functionality Modules only on FM-ready HSMs, high-availability groups of at least two appliances, and upgrade orders that must contain something to upgrade.

Any Luna Network HSM 7 appliance quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Thales does not publish list prices, so this validator produces no price build-up or line-item quote), Luna Cloud HSM and other product lines, and support contracts. Assumptions: the PED requirement for S-series models is read from the public documentation's description of PED authentication, and the group-of-two rule is generic high-availability logic, not a quoted Thales rule.

The AI sales agentBuilds the appliance quote from the conversation 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
Stated partition totals that must equal what the quoted appliances actually giveOnly with care
A stated figure is a free-entry field; a rule can compare it with a computed total, but each model needs its own base and upgrade lookup that has to be kept in step with the documentation.		The stated total travels with the quote and is compared with the computed total on every call.
Limits that differ by model: base partitions, upgrade five-packs, secure memoryOnly with care
A product rule per model. It works, but every new model is another set of rules to maintain.		Model limits are looked up from the model and every one is checked together.
A companion item that one family needs: a PED on every S-series quoteOnly with workarounds
The requirement depends on the model on one line and a device on another, so it needs a cross-line rule that interacts with the others.		The model and every item are in one request and the requirement is checked with the rest.
An option that only some units accept: Functionality Modules on FM-ready HSMsOnly with workarounds
The condition depends on a property of the appliance and the option on a different line, and a missing match is usually caught only at the end or not at all.		All items are in one request and every dependency is checked together.
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 quote has 4 partition upgrade five-packs per appliance; this model allows at most 3.
2The customer needs 30 partitions per appliance; the quoted configuration gives 25.
3The customer needs 24 MB of secure memory per appliance; this model has 16 MB.
4The quote states 60 partitions in total; the quoted appliances give 40.
5S-series models use PED (multifactor) authentication and the quote has no Luna PED, new or existing.
6Functionality Modules can be used only on FM-ready HSMs; this appliance is not FM-ready.
7A high-availability group needs at least 2 appliances; the quote has 1.
8An upgrade order needs partition five-packs or a Functionality Module; the quote has neither.
9The quote relies on a PED the customer already owns; a person should confirm it works with the quoted S-series appliance.

  

  

    
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. Partition upgrades: Partition upgrades over the model limit on a two-appliance HA group

    
The agent's request. Please quote two Luna Network HSM A750 appliances in a high-availability group, each with 4 partition upgrade five-packs, for a customer that needs 25 partitions and 12 MB of secure memory per appliance. The quote states 50 partitions in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Partition upgrades over the limit. The quote has 4 partition upgrade five-packs per appliance; this model allows at most 3.
    • 
    

    
2. Partition upgrades: The agent resubmits after fixing the errors

    
The agent's request. Please quote two Luna Network HSM A790 appliances in a high-availability group, each with 3 partition upgrade five-packs, for a customer that needs 25 partitions and 12 MB of secure memory per appliance. The quote states 50 partitions in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 appliance(s) with 25 partitions each, 50 partitions in total, 32 MB of secure memory per appliance.
    • 
    

    
3. S-series, PED and Functionality Module: S-series order with no PED and a Functionality Module on a non-FM-ready HSM

    
The agent's request. Please quote three Luna Network HSM S790 appliances in a high-availability group, each with 6 partition upgrade five-packs, for a customer that needs 40 partitions and 20 MB of secure memory per appliance, with a Functionality Module. The quote states 120 partitions in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • S-series needs a PED. S-series models use PED (multifactor) authentication and the quote has no Luna PED, new or existing.
    • 
      
  • Functionality Module needs an FM-ready HSM. Functionality Modules can be used only on FM-ready HSMs; this appliance is not FM-ready.
    • 
    

    
4. S-series, PED and Functionality Module: The agent resubmits after fixing the errors

    
The agent's request. Please quote three Luna Network HSM S790 appliances in a high-availability group, each with 6 partition upgrade five-packs, for a customer that needs 40 partitions and 20 MB of secure memory per appliance, with a Functionality Module and a new Luna PED. The quote states 120 partitions in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 3 appliance(s) with 40 partitions each, 120 partitions in total, 32 MB of secure memory per appliance.
    • 
    

    
5. Memory and partition totals: Secure memory and stated partition total do not fit the model

    
The agent's request. Please quote two Luna Network HSM A750 appliances, each with 3 partition upgrade five-packs, for a customer that needs 20 partitions and 24 MB of secure memory per appliance. The quote states 60 partitions in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Secure memory exceeded. The customer needs 24 MB of secure memory per appliance; this model has 16 MB.
    • 
      
  • Stated partitions do not match. The quote states 60 partitions in total; the quoted appliances give 40.
    • 
    

    
6. Memory and partition totals: The agent resubmits after fixing the errors

    
The agent's request. Please quote two Luna Network HSM A790 appliances, each with 3 partition upgrade five-packs, for a customer that needs 20 partitions and 24 MB of secure memory per appliance. The quote states 50 partitions in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 appliance(s) with 25 partitions each, 50 partitions in total, 32 MB of secure memory per appliance.
    • 
    

  

  

    
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 a quote for network hardware security modules with partition upgrades, an authentication device and optional modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the product 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 three Luna Network HSM S790 appliances in a high-availability group, each with 6 partition upgrade five-packs, for a customer that needs 40 partitions and 20 MB of secure memory per appliance. The quote states 120 partitions in total. 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. S-series models use PED (multifactor) authentication and the quote has no Luna PED, new or existing. Functionality Modules can be used only on FM-ready HSMs; this appliance is not FM-ready.
    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 an option that only some units accept: Functionality Modules on FM-ready HSMs, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the HSM is FM-ready to yes and the New Luna PED on the quote to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. Both earlier findings are cleared, and the validator's figure matches the quote.
    13. 
      
  13. Two 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.