Predictika · Semiconductor test handlers

An AI sales agent's test handler order, checked before it goes out

An AI sales agent prepares an order for an Eclipse or EclipseX pick-and-place test handler from the public Cohu product page: the platform, the number of test sites, the temperature range, the package size, the test force per site, the power the device dissipates and the throughput. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of those published figures and returns a verdict, every reason and the figures it computed.

Scope: Cohu Eclipse and EclipseX handlers: test sites, temperature range, package size, test force, power dissipation and throughput. See everything this validator covers

This validator models orders for the Eclipse and EclipseX pick-and-place handlers as set out on the public Cohu Eclipse product page, not just the scenarios shown below.

  • Platform limits — Eclipse parallelism from X1 to X16 and EclipseX from X1 to X8; package sizes of 3 x 3 mm to 110 x 110 mm on Eclipse and 25 x 25 mm to 135 x 315 mm on EclipseX; test force up to 650 kgf per site on Eclipse and 900 kgf on EclipseX.
  • Temperature — a standard range of -40 C to 130 C, an optional extended range of -55 C to +155 C listed for Eclipse, and EclipseX listed as tri-temp only. The extended range on an EclipseX goes to a person to confirm.
  • Power and throughput — thermal control listed up to 6 kW and throughput listed up to 12,000 units per hour. The total test force the order states must equal the sites times the force per site.

Any order for these handlers that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Cohu publishes none for these handlers, so this validator produces no price build-up or line-item quote), other Cohu handlers, device kits and change kits, chiller selection and service. Assumptions: the package size is entered as a short and a long side, and the limits are read from one product page, so any limit that depends on package or temperature together is not modeled.

The AI sales agentBuilds the handler 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 total test force that must equal the sites times the force per siteOnly with care
A stated figure is a free-entry field; a rule can compare it with a computed total, but the check has to be kept in step with the quote.		The stated total travels with the order and is compared with the computed total on every call.
Limits that differ by platform: sites, package size, test forceOnly with care
A product rule per platform. It works, but every new platform is another set of rules to maintain.		Platform limits are looked up from the platform and every one is checked together.
A temperature option that depends on the platformOnly with workarounds
The extended range depends on the platform on one line and an option on another, so it needs a cross-line rule that interacts with the others.		The platform, the range and the option are in one request and checked with the rest.
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 quote; approval findings need a person to sign off; everything else is computed.

    
1The order has 17 test sites; this platform is listed from 1 up to 16.
2The order has 9 test sites; this platform is listed from 1 up to 8.
3EclipseX is listed as tri-temp only; the order asks for a passive configuration.
4The package long side is 120 mm; this platform is listed up to 110 mm.
5The package short side is 2 mm; this platform is listed from 3 mm.
6The package short side is 20 mm; this platform is listed from 25 mm.
7The package long side is 320 mm; this platform is listed up to 315 mm.
8The order needs 140 C; the standard range tops out at 130 C and the extended range option is not on the order.
9The order needs -50 C; the standard range starts at -40 C and the extended range option is not on the order.
10The order needs -40 C to 160 C; the extended range is listed as -55 C to +155 C.
11The extended temperature range is listed for Eclipse, not for EclipseX; a person should confirm it with Cohu.
12The order needs 700 kgf per site; this platform is listed up to 650 kgf.
13The order needs 950 kgf per site; this platform is listed up to 900 kgf.
14The device dissipates 7 kW; the thermal control is listed up to 6 kW.
15The order needs 12,500 units per hour; the handler is listed up to 12,000.
16The order states 3,000 kgf of total test force; 8 sites at the chosen force give 2,400 kgf.
17The order has 0 test sites; this platform is listed from 1 up to 16.

  

  

    
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. Force and temperature: 12-site Eclipse at 700 kgf per site and 140 C

    
The agent's request. Please quote an Eclipse handler with 12 test sites at 700 kgf each, for 60 x 60 mm packages, running from -40 C to 140 C, in a passive configuration, for devices dissipating 4 kW at 11,000 units per hour. The order states 8,400 kgf of total test force. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Temperature above 130 C without the extended range. The order needs 140 C; the standard range tops out at 130 C and the extended range option is not on the order.
    • 
      
  • Test force above the platform maximum. The order needs 700 kgf per site; this platform is listed up to 650 kgf.
    • 
    

    
2. Force and temperature: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Eclipse handler with 12 test sites at 600 kgf each, for 60 x 60 mm packages, running from -40 C to 150 C, in a passive configuration with the extended temperature range, for devices dissipating 4 kW at 11,000 units per hour. The order states 7,200 kgf of total test force. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 12 test sites at 600 kgf each, 7,200 kgf in total, 11,000 units per hour.
    • 
    

    
3. EclipseX configuration: Passive EclipseX with 10 sites and an oversize package

    
The agent's request. Please quote an EclipseX handler with 10 test sites at 800 kgf each, for 140 x 300 mm packages, running from -40 C to 125 C, in a passive configuration, for devices dissipating 5 kW at 9,000 units per hour. The order states 8,000 kgf of total test force. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Test sites outside the platform range. The order has 10 test sites; this platform is listed from 1 up to 8.
    • 
      
  • Package short side above the maximum. The package short side is 140 mm; this platform is listed up to 135 mm.
    • 
      
  • EclipseX is tri-temp only. EclipseX is listed as tri-temp only; the order asks for a passive configuration.
    • 
    

    
4. EclipseX configuration: The agent resubmits after fixing the errors

    
The agent's request. Please quote an EclipseX handler with 6 test sites at 800 kgf each, for 100 x 300 mm packages, running from -40 C to 150 C, in a tri-temp configuration with the extended temperature range, for devices dissipating 5 kW at 9,000 units per hour. The order states 4,800 kgf of total test force. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Extended range on EclipseX to confirm. The extended temperature range is listed for Eclipse, not for EclipseX; a person should confirm it with Cohu.
    • 
      
  • Order summary. 6 test sites at 800 kgf each, 4,800 kgf in total, 9,000 units per hour.
    • 
    

    
5. EclipseX configuration: The agent resubmits after fixing the errors

    
The agent's request. Please quote an EclipseX handler with 6 test sites at 800 kgf each, for 100 x 300 mm packages, running from -40 C to 125 C, in a tri-temp configuration, for devices dissipating 5 kW at 9,000 units per hour. The order states 4,800 kgf of total test force. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 6 test sites at 800 kgf each, 4,800 kgf in total, 9,000 units per hour.
    • 
    

    
6. Package and throughput: Eclipse with 120 mm packages at 12,500 units per hour

    
The agent's request. Please quote an Eclipse handler with 8 test sites at 400 kgf each, for 120 x 120 mm packages, running from -40 C to 125 C, in a passive configuration, for devices dissipating 3 kW at 12,500 units per hour. The order states 3,200 kgf of total test force. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Package short side above the maximum. The package short side is 120 mm; this platform is listed up to 110 mm.
    • 
      
  • Package long side above the maximum. The package long side is 120 mm; this platform is listed up to 110 mm.
    • 
      
  • Throughput above 12,000 UPH. The order needs 12,500 units per hour; the handler is listed up to 12,000.
    • 
    

    
7. Package and throughput: The agent resubmits after fixing the errors

    
The agent's request. Please quote an EclipseX handler with 8 test sites at 400 kgf each, for 120 x 120 mm packages, running from -40 C to 125 C, in a tri-temp configuration, for devices dissipating 3 kW at 12,000 units per hour. The order states 3,200 kgf of total test force. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 8 test sites at 400 kgf each, 3,200 kgf in total, 12,000 units per hour.
    • 
    

  

  

    
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 an Eclipse or EclipseX pick-and-place test handler from the public Cohu product page: the platform, the number of test sites, the temperature range, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of those published figures 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 an EclipseX handler with 10 test sites at 800 kgf each, for 140 x 300 mm packages, running from -40 C to 125 C. The order states 8,000 kgf of total test force. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings, all in one answer. The order has 10 test sites; this platform is listed from 1 up to 8. The package short side is 140 mm; this platform is listed up to 135 mm. EclipseX is listed as tri-temp only; the order asks for a passive configuration.
    6. 
      
  6. The validator returned three 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 limits that differ by platform: sites, package size, test force, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the test sites to 6, the package short side to 100 mm, the temperature range to -40 to 150, the temperature configuration to tri-temp, the extended temperature range option to yes and the stated total test force to 4,800.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The three blocking findings are cleared; one approval remains for a person: extended range on EclipseX to confirm.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the temperature range to -40 to 125 and the extended temperature range option to no.
    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. Three 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.