Predictika · role license quote validator, modeled on 3DEXPERIENCE-style role licenses

A sales agent's role license quote, checked before it is sent

A sales agent prepares a role license quote for an engineering customer and says it is ready to send. Before it goes out, the agent sends it to Predictika's validator, which checks the role, the deployment, the reseller tier, the token allocation, the contract and the discounts together, and confirms that the net total the agent states matches the total the validator computes.

Scope: Quotes for four user roles on three deployment options through three reseller tiers, with token allocations, onboarding training and premium support, contracts of 1 to 5 years and stacked discounts. All prices and limits are illustrative estimates, not a Dassault Systemes price list. See everything this validator covers

This validator checks any quote made of these roles, deployments and tiers, not just the scenarios shown below.

  • Roles and deployment — mechanical designer, simulation analyst, manufacturing engineer and viewer roles on on-premise, private cloud and public cloud deployments. The on-premise server cannot run the simulation analyst role.
  • Token allocation — the monthly allocation per user against the role limit and the deployment pool cap, with a compute capacity review above 150 tokens.
  • Options and reseller tiers — onboarding training and premium support only on the roles that offer them, and direct, authorized reseller and strategic reseller tiers with their user minimums and discounts.
  • Contract and size — 1 to 5 years with a finance review above 3 years, up to 2,000 users with a compliance review above 500.
  • Discounts and the stated total — stacked discounts against the rep authority and the limit, and a check that the net total the agent states matches the computed total.

Any quote made of these roles, deployments and tiers is in scope, not only the scenarios pictured here. Not checked: other Dassault Systemes brands, real list prices, usage metering, outcome-based pricing, tax and multi-currency quoting.

The sales agentPrepares the role license quote from the customer's request and says it is ready to send.
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 sales agent says

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

Proposing agent: sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where a rules-based quote checklist gets this wrong
Click to expand
    
Our assessment of what a typical rules-based quote checklist or configurator form (one rule per field, each limit checked on its own) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtA rules-based quote checklistPredictika
Role and deployment compatibilityOnly with workarounds
A pairwise compatibility between two catalogs usually becomes one rule per combination.		Compatibility is a property of the role and the deployment, checked on every call.
Token allocation against two limitsOnly with care
A number that must fit both a role limit and a deployment pool cap spans several validation rules.		Both limits and the review band are evaluated together.
Discount stacking and approval bandsOnly with workarounds
Reseller, volume and extra discounts add up across rules and approval levels, and the total is rarely checked in one place.		The discounts are added once and compared with both the rep authority and the limit.
The total the agent statesOnly with workarounds
Comparing a stated total with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures.		The stated net total is a field in the request and is checked against the computed total.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved, 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.

    
1A role can be quoted only on a deployment that supports it; the on-premise server cannot run the simulation analyst role.
2The monthly token allocation per user must stay within the role limit and the cap of the deployment pool.
3A token allocation above 150 needs a compute capacity review.
4Onboarding training and premium support are available only on the roles that offer them.
5A reseller tier needs its user minimum: 100 users for a strategic reseller.
6A contract runs from 1 to 5 years, and above 3 years needs a finance review.
7An order is limited to 2,000 users, and above 500 users needs a license compliance review.
8Reseller, volume and extra discounts add up: a rep can give up to 22 percent in total, a sales director approves above that, and 30 percent is the limit.
9An order above USD 2,000,000 needs a deal desk review.
10The net total the agent states must match the contract value the validator computes, within USD 1.

  

  

    
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. The total the agent states: A net total that does not match

    
The agent's request. The engineering firm Northwind Aerospace Tooling wants 20 mechanical designer licenses on the public cloud for one year, buying direct, with 30 tokens per user per month. The net total is USD 107,100. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated net total does not match. The net total of USD 107,100 does not match the USD 119,000 the validator computed from the same choices.
    • 
      
  • Price. 20 users for 1 year: USD 4,900 per user and USD 21,000 per year of service, USD 119,000 before discount and no discount applies. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

    
2. The total the agent states: The agent resubmits after fixing the errors

    
The agent's request. Same quote for Northwind Aerospace Tooling: 20 mechanical designer licenses on the public cloud for one year, buying direct, 30 tokens per user per month. I corrected the net total to USD 119,000. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price. The stated net total now matches the computed USD 119,000: USD 4,900 per user and USD 21,000 per year of service, with no discount. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

    
3. Role and deployment: A simulation role on an on-premise server

    
The agent's request. Cedar Ridge Engineering wants 20 simulation analyst licenses on an on-premise server for one year, buying direct, with 60 tokens per user per month. The net total is USD 146,000. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Deployment cannot run the role. The on-premise server cannot run the simulation analyst role.
    • 
      
  • Price. 20 users for 1 year: USD 7,000 per user and USD 6,000 per year of service, USD 146,000 before discount and no discount. The stated net total matches the computed total. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

    
4. Role and deployment: The agent resubmits after fixing the errors

    
The agent's request. I moved the Cedar Ridge Engineering quote to the private cloud: 20 simulation analyst licenses for one year, buying direct, 60 tokens per user per month. The net total is USD 152,000. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price. The private cloud can run the role. The price is USD 7,120 per user and USD 9,600 per year of service, USD 152,000 with no discount, and the stated net total matches. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

    
5. Reseller tier: A strategic reseller below its user minimum

    
The agent's request. A strategic reseller is quoting 60 mechanical designer licenses on the public cloud for one year for a customer team, with 30 tokens per user per month. The net total is USD 282,030. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Below the reseller minimum. 60 users are below the 100 users minimum of the strategic reseller tier.
    • 
      
  • Price. 60 users for 1 year: USD 357,000 before discount and 21 percent total discount, USD 282,030 net. The stated net total matches the computed total. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

    
6. Reseller tier: The agent resubmits after fixing the errors

    
The agent's request. I raised the reseller quote to 100 users: mechanical designer licenses on the public cloud for one year, strategic reseller, 30 tokens per user per month. The net total is USD 470,050. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price. 100 users meet the tier minimum. USD 595,000 before discount and 21 percent total discount give USD 470,050 net, and the stated net total matches. Illustrative estimate in US dollars, not a Dassault Systemes price.
    • 
    

  

  

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

    
    
      
  1. Welcome to a demo of Predictika's Validator. A sales agent prepares a role license quote for an engineering customer and says it is ready to send. Before it goes out, the agent sends it to Predictika's validator, which checks the role, the deployment, the reseller tier, the token allocation, the contract and the discounts together, and confirms that the net total the agent states matches the total the validator computes.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. The engineering firm Northwind Aerospace Tooling wants 20 mechanical designer licenses on the public cloud for one year, buying direct, with 30 tokens per user per month. The net total is USD 107,100. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding, all in one answer. The net total of USD 107,100 does not match the USD 119,000 the validator computed from the same choices.
    6. 
      
  6. The validator returned one blocking finding 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 and against the stated total.
    7. 
      
  7. What this shows: for the total the agent states, a rules-based quote checklist can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the net total the agent states to 119,000.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. The earlier finding is cleared.
    13. 
      
  13. One problem 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.