Predictika · Radar system quotes

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

An AI sales agent prepares a quote for a customer that wants a Hensoldt Spexer 2000 3D Mk III radar installation with a number of antennas, beams, effector links and options. Before the quote goes out, the agent sends it to Predictika, which checks it against a declarative model of the product and returns a verdict, every reason and the coverage, range and track capacity it computed.

Scope: Hensoldt Spexer 2000 3D Mk III radar quotes: one to three antennas, beams per antenna, coverage, range, track capacity, effector links, scan-on-the-move, export review and discount. See everything this validator covers

This validator models Spexer 2000 3D Mk III quotes, not just the scenarios shown below.

  • Performance against the requirement — 120 degrees of coverage per antenna, 360 degrees with three antennas, a range that falls from 40 km with a single beam to 2.5 km with 16 beams, and over 300 simultaneous tracks per antenna sector.
  • Installation and links — scan-on-the-move on vehicle and maritime installations, a command-and-control Ethernet link for effectors, and the number of effectors linked.
  • Commercial checks — the stated coverage against the computed coverage, discount approval and block thresholds, export customer review, and an operating-concept check for vehicle counter-UAS use.

Any Spexer 2000 quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Hensoldt radars, integration work, support and training. The validator computes coverage, range and track capacity but no price, because no prices are modeled. The antenna, beam, range and track figures follow public Hensoldt and press pages; the intermediate range steps, the effector limit and the discount and review thresholds are modeled and are not published by Hensoldt.

The AI sales agentBuilds the radar 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
Range that depends on the beam countOnly with care
Range falls in steps as beams are added, so the step table has to be encoded and kept in step with each requirement.		The beam count is a field of the request and the reachable range is computed from it on every call.
Coverage and track capacity that scale with the antenna countOnly with care
Each requirement needs its own rule that recomputes what the antennas give and compares it with what the customer needs.		The antenna count and every requirement are in one request and compared on every call.
Links and options that depend on each other, such as effectors needing a C2 linkOnly with care
Each dependency needs its own rule, and the rule list grows with every option and installation type.		The link, the effectors and the platform are fields of one request and checked together on every call.
A stated coverage that must match the computed coverageOnly with workarounds
The coverage is derived from the antenna count, so a separate rule is needed to recompute it and compare it with the stated figure.		The stated coverage is a field of the request and is compared with the computed coverage 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 quote has 4 antennas; a Spexer 2,000 system uses 1 to 3 antennas.
2The customer needs 40,000 m of range; with the quoted beam count the radar reaches 15,000 m.
3The quote asks for 17 beams per antenna; the radar supports 1 to 16.
4The customer needs 360 degrees of coverage; the quoted antennas give 240.
5The customer needs 301 simultaneous tracks; the quoted antennas track 300.
6The quote states 240 degrees of coverage; the quoted antennas give 360.
7Effectors are linked but the quote has no command-and-control Ethernet link.
8The quote links 5 effectors; this model allows up to 4.
9Scan-on-the-move is for vehicle or maritime installations; the platform is fixed.
10A vehicle-mounted counter-UAS system is quoted without scan-on-the-move; an engineer should confirm the operating concept.
11The customer is outside the home market; export control review is required before the quote is sent.
12The 18 percent discount is above 10 percent and needs sales management approval.
13The quote has a 30 percent discount; discounts above 25 percent are not allowed.

  

  

    
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. Performance against the requirement: A two-antenna quote for a 360 degree requirement with 40 km range, 700 tracks and five effectors without a C2 link

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 2 antennas and 4 beams per antenna on a vehicle installation, with scan-on-the-move, 5 linked effectors and a 5 percent discount. The customer needs 360 degrees of coverage, 40,000 m of range and 700 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Coverage short of the requirement. The customer needs 360 degrees of coverage; the quoted antennas give 240.
    • 
      
  • Range short of the requirement. The customer needs 40,000 m of range; with the quoted beam count the radar reaches 15,000 m.
    • 
      
  • Track capacity exceeded. The customer needs 700 simultaneous tracks; the quoted antennas track 600.
    • 
      
  • Stated coverage does not match. The quote states 360 degrees of coverage; the quoted antennas give 240.
    • 
      
  • Effectors need a C2 link. Effectors are linked but the quote has no command-and-control Ethernet link.
    • 
      
  • Too many effectors. The quote links 5 effectors; this model allows up to 4.
    • 
    

    
2. Performance against the requirement: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 3 antennas and 1 beam per antenna on a vehicle installation, with scan-on-the-move, 4 linked effectors, a C2 Ethernet link and a 5 percent discount. The customer needs 360 degrees of coverage, 40,000 m of range and 700 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Radar summary. 3 antenna(s), 360 degrees coverage, 40,000 m range, 900 simultaneous tracks.
    • 
    

    
3. Installation and discount: A fixed-site quote with scan-on-the-move and a large discount

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 3 antennas and 4 beams per antenna on a fixed installation, with scan-on-the-move, 2 linked effectors, a C2 Ethernet link and a 30 percent discount. The customer needs 360 degrees of coverage, 12,000 m of range and 500 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Scan-on-the-move on a fixed site. Scan-on-the-move is for vehicle or maritime installations; the platform is fixed.
    • 
      
  • Discount over the limit. The quote has a 30 percent discount; discounts above 25 percent are not allowed.
    • 
    

    
4. Installation and discount: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 3 antennas and 4 beams per antenna on a fixed installation, with 2 linked effectors, a C2 Ethernet link and a 8 percent discount. The customer needs 360 degrees of coverage, 12,000 m of range and 500 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Radar summary. 3 antenna(s), 360 degrees coverage, 15,000 m range, 900 simultaneous tracks.
    • 
    

    
5. Beams and operating concept: A vehicle counter-UAS quote with sixteen beams for a 6 km range requirement and no scan-on-the-move

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 3 antennas and 16 beams per antenna on a vehicle installation, with counter-UAS use, 2 linked effectors, a C2 Ethernet link and a 5 percent discount. The customer needs 360 degrees of coverage, 6,000 m of range and 500 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Range short of the requirement. The customer needs 6,000 m of range; with the quoted beam count the radar reaches 2,500 m.
    • 
      
  • Moving platform without scan-on-the-move. A vehicle-mounted counter-UAS system is quoted without scan-on-the-move; an engineer should confirm the operating concept.
    • 
    

    
6. Beams and operating concept: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Spexer 2000 3D Mk III radar with 3 antennas and 8 beams per antenna on a vehicle installation, with scan-on-the-move, counter-UAS use, 2 linked effectors, a C2 Ethernet link and a 5 percent discount. The customer needs 360 degrees of coverage, 6,000 m of range and 500 simultaneous tracks. The quote states 360 degrees of coverage. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Radar summary. 3 antenna(s), 360 degrees coverage, 6,000 m range, 900 simultaneous tracks.
    • 
    

  

  

    
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 a customer that wants a Hensoldt Spexer 2000 3D Mk III radar installation. Before the quote goes out, the agent sends it to Predictika, which checks it against a declarative model of the product and returns a verdict, every reason and the coverage, range and track capacity it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a Spexer 2000 3D Mk III radar. The customer needs 360 degrees of coverage, 40,000 m of range and 700 simultaneous tracks. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with six findings, all in one answer. The customer needs 360 degrees of coverage; the quoted antennas give 240. The customer needs 40,000 m of range; with the quoted beam count the radar reaches 15,000 m. The customer needs 700 simultaneous tracks; the quoted antennas track 600. The other three are on screen.
    6. 
      
  6. The validator returned six 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 coverage and track capacity that scale with the antenna count, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the antennas to 3, the beams per antenna to 1, the effectors linked to 4 and the C2 Ethernet link to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All six earlier findings are cleared.
    13. 
      
  13. Six 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.