Predictika · Motion-control orders

An AI sales agent's linear-guide order, checked before it goes out

An AI sales agent prepares an order for THK LM Guide HSR-M1 (high-temperature) linear guides: size, block type, long or standard block, rail length and the number of blocks and rails. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the catalog tables and returns a verdict, every reason and the figures it computed.

Scope: THK LM Guide model HSR-M1 (high-temperature type) in sizes 15 to 35, with block types A, B, C, R and YR, long blocks and standard rail lengths. See everything this validator covers

This validator models orders for the HSR-M1 range, not just the scenarios shown below.

  • Size and block type — sizes 15, 20, 25, 30 and 35; block types A, B, C, R and YR; long blocks, which the catalog lists for every combination except size 15 with A or B and the YR type.
  • Rails — the standard maximum rail length for each size (1,240 mm for size 15, 1,480 mm for size 20 and 1,500 mm for sizes 25, 30 and 35), jointed rails beyond it, the number of LM blocks on each rail and the number of rail sets, compared with the maximum the agent states.

Any HSR-M1 order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (THK does not publish list prices, so this validator produces no price build-up or line-item quote), other LM Guide models, ball screws and other THK products, the HSR-M1VV variant, and which contamination-protection, preload and accuracy options suit each application. Assumptions: contamination protection is limited to the UU and SS seals named in the catalog; a rail longer than the standard maximum needs the jointed-rail option; preload and accuracy choices are accepted as listed on the coding line and are not cross-checked.

The AI sales agentBuilds the guide 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.

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
Block types that exist only at some sizesOnly with care
A product rule per size and type, written from the catalog tables. It works, but every size and type is another rule to keep in step with the catalog.		Size, block type and long block are in one request and the availability rule is checked with the rest.
Rail length limits that differ by sizeOnly with care
A validation rule for each size. It works, but the limits are easy to mistype and a stated figure on the order is a free-entry field.		The maximum is computed from the size and compared with the rail ordered and with the figure the agent states.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order 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 order; everything else is computed.

    
1Size 10 is not available in the HSR-M1 range; the sizes are 15, 20, 25, 30 and 35.
2The long block is not listed for this combination of size 15 and block type; HSR-M1YR has no long version and sizes below 20 have no long A or B block.
3A rail of 1,241 mm is longer than the standard maximum of 1,240 mm for this size and is not marked as jointed.
4The quote has a rail length of 0 mm; a rail length is needed.
5The quote has 0 LM blocks on each rail; at least 1 is needed.
6The quote has 0 rail sets; each rail is one set and at least 1 is needed.
7The quote states a standard maximum rail length of 1,480 mm; the catalog lists 1,500 mm for this size.

  

  

    
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. Block types: Long A block ordered at size 15

    
The agent's request. Please prepare an order for Kestrel Automation: 4 rail sets of HSR 15M1LA, with 2 LM blocks on each rail and rails of 1,000 mm. The standard maximum rail length for this size is 1,240 mm. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Long block not available for this size and type. The long block is not listed for this combination of size 15 and block type; HSR-M1YR has no long version and sizes below 20 have no long A or B block.
    • 
    

    
2. Block types: The agent resubmits after fixing the errors

    
The agent's request. Please prepare an order for Kestrel Automation: 4 rail sets of HSR 15M1LC, with 2 LM blocks on each rail and rails of 1,000 mm. The standard maximum rail length for this size is 1,240 mm. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Size 15 HSR-M1, 2 LM blocks per rail, 4 rail sets, rail of 1,000 mm against a standard maximum of 1,240 mm.
    • 
    

    
3. Rail length: Rail longer than the size 20 limit with a wrong stated maximum

    
The agent's request. Please prepare an order for Kestrel Automation: 6 rail sets of HSR 20M1LB, with 2 LM blocks on each rail and rails of 1,800 mm. The standard maximum rail length for this size is 1,500 mm. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Rail longer than the standard maximum. A rail of 1,800 mm is longer than the standard maximum of 1,480 mm for this size and is not marked as jointed.
    • 
      
  • Stated maximum rail length does not match. The quote states a standard maximum rail length of 1,500 mm; the catalog lists 1,480 mm for this size.
    • 
    

    
4. Rail length: The agent resubmits after fixing the errors

    
The agent's request. Please prepare an order for Kestrel Automation: 6 rail sets of HSR 20M1LB, with 2 LM blocks on each rail and rails of 1,480 mm. The standard maximum rail length for this size is 1,480 mm. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Size 20 HSR-M1, 2 LM blocks per rail, 6 rail sets, rail of 1,480 mm against a standard maximum of 1,480 mm.
    • 
    

    
5. Sizes: Size 40 ordered from the HSR-M1 range

    
The agent's request. Please prepare an order for Kestrel Automation: 2 rail sets of HSR 40M1R, with 3 LM blocks on each rail and rails of 1,500 mm. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Size is not in the HSR-M1 range. Size 40 is not available in the HSR-M1 range; the sizes are 15, 20, 25, 30 and 35.
    • 
    

    
6. Sizes: The agent resubmits after fixing the errors

    
The agent's request. Please prepare an order for Kestrel Automation: 2 rail sets of HSR 35M1R, with 3 LM blocks on each rail and rails of 1,500 mm. The standard maximum rail length for this size is 1,500 mm. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Size 35 HSR-M1, 3 LM blocks per rail, 2 rail sets, rail of 1,500 mm against a standard maximum of 1,500 mm.
    • 
    

  

  

    
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 THK LM Guide HSR-M1 (high-temperature) linear guides: size, block type, long or standard block, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the catalog tables 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 prepare an order for Kestrel Automation: 4 rail sets of HSR 15M1LA, with 2 LM blocks on each rail and rails of 1,000 mm. The standard maximum rail length for this size is 1,240 mm. 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 long block is not listed for this combination of size 15 and block type; HSR-M1YR has no long version and sizes below 20 have no long A or B block.
    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.
    7. 
      
  7. What this shows: for block types that exist only at some sizes, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the block type to C.
    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.