Predictika · Metrology accessory orders

An AI sales agent's FaroArm accessory order, checked before it goes out

An AI sales agent prepares an order that pairs a portable measuring arm with a laser line probe, a driver version, a probe and a probe adapter. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of FARO's published compatibility tables and returns a verdict and every reason.

Scope: FaroArm and ScanArm laser line probe compatibility with arm and driver, probe adapters, TrackArm prerequisites and a regional restriction. See everything this validator covers

This validator models accessory orders for FARO FaroArm and ScanArm measuring arms, not just the scenarios shown below: seven arm groups, four driver support versions, ten laser line probe models and four probe adapters.

  • Laser line probe compatibility — the probe must be marked compatible with the arm group and with the driver support version in FARO's compatibility table; the FAROBlu xE is not available in the US and Canada.
  • Probe and adapter — the Universal Adapter 20780 accepts M4 threaded probes (M6 probes need the Extension Adapter 21460); the TrackArm Adapter 21583 does not support M6 probes and is listed for a Quantum series FaroArm used with a FARO laser tracker; a Renishaw TP-20 probe goes with the TP-20 Adapter 20735.

Any order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (the public pages carry none, so this validator produces no price build-up or line-item quote), the arm models themselves and their measuring volumes, scanners, laser trackers, software modules and warranty tiers, probe interface generations, and the correspondence between a particular arm serial number and its table group.

The AI sales agentBuilds the accessory 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 part that works with only some arms and driversOnly with care
The laser line probe is compatible with some arm groups and some driver versions, so every probe needs a rule per arm group and per driver. It works, but ten probes, seven arm groups and four driver versions mean many rule entries to keep in step with the table.		Each probe is checked against both columns of the compatibility table, in one request, whatever order the choices arrive in.
A part that needs a particular companionOnly with workarounds
The TrackArm Adapter depends on the arm group and on a laser tracker that sits on a different line; a rule has to look across lines.		The adapter, the arm group, the tracker and the probe thread are checked together with everything else.
A restriction by regionOnly with care
Regional availability is an order-level fact that depends on the probe chosen; a rule can compare it, but someone has to write and maintain it.		The region travels with the order and is compared on every call.
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 laser line probe on the order is not marked compatible with the selected arm in the FARO compatibility table.
2The laser line probe on the order is not marked compatible with the selected driver support version in the FARO compatibility table.
3The FARO compatibility table states that the FAROBlu xE is not available in the US and Canada.
4The Universal Adapter 20780 accepts probes with M4 threads; an M6 threaded probe needs the Extension Adapter 21460.
5The TrackArm Adapter 21583 does not support the use of M6 threaded probes.
6The TrackArm Adapter 21583 is listed for a Quantum series FaroArm used together with a FARO laser tracker; the order lacks one of them.
7The TP-20 Adapter 20735 is the adapter used to communicate with a Renishaw TP-20 probe; the order has the probe without it.

  

  

    
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. Quantum Series arm with FAROBlu xE: A Quantum Series arm order with a FAROBlu xE laser line probe for the US

    
The agent's request. Please quote an accessory order for Brightline Aerospace Metrology, delivered in the US: a Quantum Series 7/8-axis arm on driver support v6.10.53 or later, laser line probe: FAROBlu xE, probe adapter: Universal Adapter 20780, probe: M4 threaded ball probe (21765), laser tracker: not ordered. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Laser Line Probe is not compatible with the arm. The laser line probe on the order is not marked compatible with the selected arm in the FARO compatibility table.
    • 
      
  • FAROBlu xE is not available in the US and Canada. The FARO compatibility table states that the FAROBlu xE is not available in the US and Canada.
    • 
    

    
2. Quantum X/Max arm with FAROBlu xR/xP/xS: The agent resubmits after fixing the errors

    
The agent's request. Please quote an accessory order for Brightline Aerospace Metrology, delivered in the US: a Quantum X/Max 7/8-axis arm on driver support v6.10.53 or later, laser line probe: FAROBlu xR, xP or xS, probe adapter: Universal Adapter 20780, probe: M4 threaded ball probe (21765), laser tracker: not ordered. It is ready to send.

    
Verdict: Allowed.

    
3. Legacy 7-axis arm with V1/V2 probe and M6 probe: A legacy 7-axis arm with a V1/V2 laser line probe and an M6 probe on the Universal Adapter

    
The agent's request. Please quote an accessory order for Northfield Tool and Die, delivered in the US: a 7-axis Platinum / Legacy Quantum / Fusion / Titanium arm on driver support v6.0 to 6.7, laser line probe: V1 or V2, probe adapter: Universal Adapter 20780, probe: M6 threaded probe, laser tracker: not ordered. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Laser Line Probe is not compatible with the driver version. The laser line probe on the order is not marked compatible with the selected driver support version in the FARO compatibility table.
    • 
      
  • M6 probe on the Universal Adapter. The Universal Adapter 20780 accepts probes with M4 threads; an M6 threaded probe needs the Extension Adapter 21460.
    • 
    

    
4. Legacy 7-axis arm with V1/V2 probe and M6 probe: The agent resubmits after fixing the errors

    
The agent's request. Please quote an accessory order for Northfield Tool and Die, delivered in the US: a 7-axis Platinum / Legacy Quantum / Fusion / Titanium arm on driver support v5.x, laser line probe: V1 or V2, probe adapter: Universal Adapter 20780, probe: M6 threaded probe, laser tracker: not ordered. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • M6 probe on the Universal Adapter. The Universal Adapter 20780 accepts probes with M4 threads; an M6 threaded probe needs the Extension Adapter 21460.
    • 
    

    
5. Legacy 7-axis arm with V1/V2 probe and M6 probe: The agent resubmits after fixing the errors

    
The agent's request. Please quote an accessory order for Northfield Tool and Die, delivered in the US: a 7-axis Platinum / Legacy Quantum / Fusion / Titanium arm on driver support v5.x, laser line probe: V1 or V2, probe adapter: Extension Adapter 21460, probe: M6 threaded probe, laser tracker: not ordered. It is ready to send.

    
Verdict: Allowed.

    
6. Quantum Series arm with TrackArm Adapter: A Quantum Series arm with the TrackArm Adapter, an M6 probe and no laser tracker

    
The agent's request. Please quote an accessory order for Brightline Aerospace Metrology, delivered in the US: a Quantum Series 7/8-axis arm on driver support v6.10.53 or later, laser line probe: none, probe adapter: TrackArm Adapter 21583, probe: M6 threaded probe, laser tracker: not ordered. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • M6 probe on the TrackArm Adapter. The TrackArm Adapter 21583 does not support the use of M6 threaded probes.
    • 
      
  • TrackArm Adapter prerequisites. The TrackArm Adapter 21583 is listed for a Quantum series FaroArm used together with a FARO laser tracker; the order lacks one of them.
    • 
    

    
7. Quantum Series arm with TrackArm Adapter: The agent resubmits after fixing the errors

    
The agent's request. Please quote an accessory order for Brightline Aerospace Metrology, delivered in the US: a Quantum Series 7/8-axis arm on driver support v6.10.53 or later, laser line probe: none, probe adapter: TrackArm Adapter 21583, probe: standard iProbe (20540), laser tracker: ordered. It is ready to send.

    
Verdict: Allowed.

  

  

    
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 that pairs a portable measuring arm with a laser line probe, a driver version, a probe and a probe adapter. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of FARO's published compatibility tables and returns a verdict and every reason.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote an accessory order for Northfield Tool and Die, delivered in the US: a 7-axis Platinum / Legacy Quantum / Fusion / Titanium arm on driver support v6.0 to 6.7. It is ready to send. 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. The laser line probe on the order is not marked compatible with the selected driver support version in the FARO compatibility table. The Universal Adapter 20780 accepts probes with M4 threads; an M6 threaded probe needs the Extension Adapter 21460.
    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 a part that works with only some arms and drivers, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the driver support version to Driver support v5.x.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The Universal Adapter 20780 accepts probes with M4 threads; an M6 threaded probe needs the Extension Adapter 21460.
    12. 
      
  12. One finding cleared. Still blocking: M6 probe on the Universal Adapter.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the probe adapter to Extension Adapter 21460.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared.
    18. 
      
  18. Two 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.