Predictika · Test and measurement instrument option configuration

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

An AI sales agent prepares a quote for an MXO 3 oscilloscope with a bandwidth upgrade, MSO digital channels, protocol decoding and analysis options. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published ordering information and returns a verdict, every reason and the figures it computed.

Scope: Rohde & Schwarz MXO 3 oscilloscopes (MXO 34 and MXO 38): bandwidth upgrades, MSO option, protocol decoding and analysis options, and application bundle PK1. See everything this validator covers

This validator models MXO 3 oscilloscope quotes, not just the scenarios shown below.

  • Model, channels and bandwidth — MXO 34 (4 channels) and MXO 38 (8 channels); the bandwidth upgrade codes for each (B242, B243, B245, B2410 and B282, B283, B285, B2810) to 200, 350, 500 and 1,000 MHz; the required bandwidth against the bandwidth the configuration delivers, and the stated bandwidth against the computed one.
  • MSO and analysis options — the MSO option (B1, 16 digital channels), the arbitrary waveform generator (B6) and the frequency response analysis option (K36), which requires B6.
  • Protocol decoding and bundle — the serial decode options K510, K520, K530, K550, K560 and K570 against the protocols each covers, and application bundle PK1, which already includes B6, B105, K31, K36, K510, K520, K530, K550 and K560.

Any MXO 3 quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (no price list is modeled, so this validator produces no price build-up or line-item quote), memory depth rules, the other MXO and R&S oscilloscope families, probes and accessories, and service and calibration plans.

The AI sales agentBuilds the oscilloscope 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
Upgrade codes that fit only one modelOnly with care
Each upgrade code belongs to the 4-channel or the 8-channel model, so each needs a rule tying it to the model, kept up to date as codes are added.		The model and the upgrade code are in one request and compared on every call.
A bandwidth need that must be met by the upgradeOnly with care
The delivered bandwidth depends on the upgrade code, so it takes a lookup and a comparison rule per code.		The upgrade code and the required bandwidth are in one request and the delivered bandwidth is computed and compared on every call.
Protocol options that cover specific protocolsOnly with workarounds
Which option decodes which protocol, and whether a bundle already includes it, needs a rule per protocol and per bundle member.		The protocols and every option are in one request, so a missing or bundled option is found whichever order the choices arrive in.
Options that duplicate a bundleOnly with workarounds
Detecting that an option is already inside the bundle needs a cross-line rule for each member, and the list changes with the bundle.		The bundle and all options travel together and the overlap is counted on every call.
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 customer needs 5 analog channels; the quoted model has 4.
2The bandwidth upgrade on the quote is for the other model; MXO 34 (4 channels) takes B242, B243, B245 and B2410, and MXO 38 (8 channels) takes B282, B283, B285 and B2,810.
3The customer needs 700 MHz of bandwidth; the quoted configuration delivers 500 MHz.
4The customer needs 200 MHz of bandwidth; the quoted configuration delivers 100 MHz.
5The quote states 1,000 MHz of bandwidth; the quoted configuration delivers 500 MHz.
6The customer needs digital channels and the quote has no MSO option (MXO3-B1, 16 digital channels).
7The customer needs 17 digital channels; the MSO option provides 16.
8Option K36 (frequency response analysis) requires option B6 (arbitrary waveform generator), which is not on the quote.
9The quote has application bundle PK1 and also 1 option(s) that PK1 already includes.
10The first protocol to decode needs option MXO3-K520, which is not on the quote.
11The first protocol to decode needs option MXO3-K510, which is not on the quote.
12The second protocol to decode needs option MXO3-K570, which is not on the quote.
13The first protocol to decode needs option MXO3-K560, which is not on the quote.
14The quote has application bundle PK1 and also 3 option(s) that PK1 already includes.
15The first protocol to decode needs option MXO3-K530, which is not on the quote.

  

  

    
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. Model, channels and options: Six channels, a mismatched upgrade code, digital channels and CAN decode, quoted without the matching options

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 34, with bandwidth upgrade B285, for 6 analog channels, a bandwidth requirement of 500 MHz, a quoted bandwidth of 500 MHz, 16 digital channels, decoding CAN and SPI, with option K510. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Analog channels over the model. The customer needs 6 analog channels; the quoted model has 4.
    • 
      
  • Bandwidth upgrade for the other model. The bandwidth upgrade on the quote is for the other model; MXO 34 (4 channels) takes B242, B243, B245 and B2410, and MXO 38 (8 channels) takes B282, B283, B285 and B2,810.
    • 
      
  • Digital channels need the MSO option. The customer needs digital channels and the quote has no MSO option (MXO3-B1, 16 digital channels).
    • 
      
  • First protocol option missing. The first protocol to decode needs option MXO3-K520, which is not on the quote.
    • 
    

    
2. Model, channels and options: The agent resubmits after fixing the errors

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 38, with bandwidth upgrade B285, for 6 analog channels, a bandwidth requirement of 500 MHz, a quoted bandwidth of 500 MHz, 16 digital channels, decoding CAN and SPI, with options B1, K510, K520. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. MXO 3 with 8 analog channels and 500 MHz of delivered bandwidth.
    • 
    

    
3. Bundle PK1: Bundle PK1 with options it already includes and a stated bandwidth that does not match

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 34, with bandwidth upgrade B2410, for 4 analog channels, a bandwidth requirement of 1,000 MHz, a quoted bandwidth of 700 MHz, decoding ARINC 429 and USB 2.0, with options B6, B105, K36, K570, PK1. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated bandwidth does not match. The quote states 700 MHz of bandwidth; the quoted configuration delivers 1,000 MHz.
    • 
      
  • Options already in bundle PK1. The quote has application bundle PK1 and also 3 option(s) that PK1 already includes.
    • 
    

    
4. Bundle PK1: The agent resubmits after fixing the errors

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 34, with bandwidth upgrade B2410, for 4 analog channels, a bandwidth requirement of 1,000 MHz, a quoted bandwidth of 1,000 MHz, decoding ARINC 429 and USB 2.0, with options K570, PK1. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. MXO 3 with 4 analog channels and 1,000 MHz of delivered bandwidth.
    • 
    

    
5. Bandwidth and analysis options: A 500 MHz need on a 350 MHz upgrade, frequency response analysis and USB decode

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 38, with bandwidth upgrade B283, for 8 analog channels, a bandwidth requirement of 500 MHz, a quoted bandwidth of 500 MHz, 16 digital channels, decoding USB 2.0 and I3C, with options B1, K36, K550. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Bandwidth below the requirement. The customer needs 500 MHz of bandwidth; the quoted configuration delivers 350 MHz.
    • 
      
  • Stated bandwidth does not match. The quote states 500 MHz of bandwidth; the quoted configuration delivers 350 MHz.
    • 
      
  • Frequency response analysis needs the AWG. Option K36 (frequency response analysis) requires option B6 (arbitrary waveform generator), which is not on the quote.
    • 
      
  • First protocol option missing. The first protocol to decode needs option MXO3-K570, which is not on the quote.
    • 
    

    
6. Bandwidth and analysis options: The agent resubmits after fixing the errors

    
The agent's request. Please quote an R&S MXO 3 oscilloscope, model MXO 38, with bandwidth upgrade B285, for 8 analog channels, a bandwidth requirement of 500 MHz, a quoted bandwidth of 500 MHz, 16 digital channels, decoding USB 2.0 and I3C, with options B1, B6, K36, K550, K570. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. MXO 3 with 8 analog channels and 500 MHz of delivered bandwidth.
    • 
    

  

  

    
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 an MXO 3 oscilloscope with a bandwidth upgrade, MSO digital channels, protocol decoding and analysis options. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published ordering information 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 R&S MXO 3 oscilloscope, model MXO 38, with bandwidth upgrade B283, for 8 analog channels, a bandwidth requirement of 500 MHz. 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 four findings, all in one answer. The customer needs 500 MHz of bandwidth; the quoted configuration delivers 350 MHz. The quote states 500 MHz of bandwidth; the quoted configuration delivers 350 MHz. Option K36 (frequency response analysis) requires option B6 (arbitrary waveform generator), which is not on the quote. The other one is on screen.
    6. 
      
  6. The validator returned four 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 bandwidth need that must be met by the upgrade, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the bandwidth upgrade to B285 (500 MHz, MXO 38). It sets the Option B6 to yes and the Option K570 to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All four earlier findings are cleared.
    13. 
      
  13. Four 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.