Predictika · Fuel site monitoring orders

An AI sales agent's tank gauge console order, checked before it goes out

An AI sales agent prepares an order for a Veeder-Root TLS automatic tank gauge console with its expansion boxes, in-tank probes, sensors and optional leak detection and software options. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the specifications Veeder-Root publishes and returns a verdict, every reason and the figures it computed.

Scope: TLS-450PLUS, TLS4 and TLS4B tank gauge console orders: expansion boxes, in-tank probes, probe and sensor inputs, tanks, and which options each console offers. See everything this validator covers

This validator models orders for the three Veeder-Root TLS consoles on the public specification sheet (TLS-450PLUS, TLS4 and TLS4B), not just the scenarios shown below.

  • Capacity — the most TLS-XB expansion boxes, in-tank probes, universal probe and sensor inputs and sensors of any one type each console takes, and the TLS-450PLUS limits of 64 tanks (32 with Business Inventory Reconciliation) and 16 lines for line leak testing.
  • Options by console — the 7-Amp Controller Module, optional inputs and outputs, continuous statistical leak detection, digital pressurized line leak detection, in-station diagnostics, the DC power input and HydrX fuel conditioning, each only on the consoles where the specification sheet lists it.
  • Dependencies and stated counts — HydrX on a TLS4 needs one expansion box, and the probe and sensor count the agent states must equal the quote's probes plus sensors.

Any TLS console order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Veeder-Root does not publish a price list), probe and sensor part numbers, communication modules, software options other than those named, other Veeder-Root console families, and installation. The maximum counts are read from the specification sheet as maximum values.

The AI sales agentBuilds the console 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
An option that only some consoles offerOnly with care
A per-console product rule for each option, written and maintained one by one.		The console and every option are in one request and checked together on every call.
Probe and sensor counts that depend on the console and its expansion boxesOnly with care
Limits differ by console and are compared with counts on separate lines, so each needs its own validation rule.		Counts, console and expansion boxes are compared on every call, in any order.
A stated count that disagrees with the quote linesOnly with workarounds
A stated figure is free entry; checking it against a derived total takes extra formulas that interact with the other rules.		The stated count is a field in the request and is compared with the computed one.
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 quote has 4 TLS-XB expansion boxes; the selected console supports up to 3.
2The quote has 65 in-tank probes; the selected console takes at most 64.
3The quote has 257 probes and sensors in all; the selected console has at most 256 universal probe and sensor inputs.
4The quote has 100 sensors of one type; the selected console allows at most 99 of any one sensor type.
5The quote monitors 33 tanks; the TLS-450PLUS monitors up to 32 with this combination of options (64 tanks, or 32 with Business Inventory Reconciliation).
6The quote has 17 lines for line leak testing; the TLS-450PLUS lists a line leak testing capacity of 16 lines.
7The optional DC power input is listed for the TLS4 and TLS4B, not the TLS-450PLUS.
8The quote has 2 TLS-XB expansion boxes; the selected console supports up to 1.
9The quote has 33 in-tank probes; the selected console takes at most 32.
10The quote has 77 probes and sensors in all; the selected console has at most 76 universal probe and sensor inputs.
11HydrX fuel conditioning on a TLS4 needs one TLS-XB expansion box; the quote has none.
12Digital pressurized line leak detection is listed as an option for the TLS-450PLUS only.
13In-station diagnostics are listed for the TLS-450PLUS only.
14The quote has 7 in-tank probes; the selected console takes at most 6.

  

  

    
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. Console model and options: A TLS4B order with an expansion box, the 7-Amp module, statistical leak detection and optional I/O

    
The agent's request. Please quote a Veeder-Root TLS4B tank gauge console with 6 in-tank probes and 6 other sensors, monitoring 6 tanks, with 1 TLS-XB expansion box, with the 7-Amp Controller Module, optional inputs and outputs and continuous statistical leak detection. The order states 12 probes and sensors in all. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many expansion boxes. The quote has 1 TLS-XB expansion box; the selected console supports none.
    • 
      
  • Too many probes and sensors for the console. The quote has 12 probes and sensors in all; the selected console has at most 6 universal probe and sensor inputs.
    • 
      
  • 7-Amp Controller Module on a TLS4B. The 7-Amp Controller Module is not available on the TLS4B.
    • 
      
  • Continuous statistical leak detection on a TLS4B. Continuous statistical leak detection is not available on the TLS4B.
    • 
      
  • Optional inputs and outputs on a TLS4B. Optional inputs and outputs are not available on the TLS4B.
    • 
    

    
2. Console model and options: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Veeder-Root TLS4 tank gauge console with 6 in-tank probes and 6 other sensors, monitoring 6 tanks, with 1 TLS-XB expansion box, with the 7-Amp Controller Module, optional inputs and outputs, continuous statistical leak detection and the DC power input. The order states 12 probes and sensors in all. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 6 probes and 6 sensors (12 in all) against a console maximum of 76 probe and sensor inputs; 1 expansion box(es) against a maximum of 1.
    • 
    

    
3. Site size and stated count: A TLS-450PLUS order for 40 tanks with BIR, 20 leak-test lines and a short device count

    
The agent's request. Please quote a Veeder-Root TLS-450PLUS tank gauge console with 40 in-tank probes and 60 other sensors, monitoring 40 tanks, with 2 TLS-XB expansion boxes, with digital pressurized line leak detection and Business Inventory Reconciliation, testing 20 lines. The order states 90 probes and sensors in all. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many tanks for the console. The quote monitors 40 tanks; the TLS-450PLUS monitors up to 32 with this combination of options (64 tanks, or 32 with Business Inventory Reconciliation).
    • 
      
  • Too many lines for line leak testing. The quote has 20 lines for line leak testing; the TLS-450PLUS lists a line leak testing capacity of 16 lines.
    • 
      
  • Stated probes and sensors do not match. The quote states 90 probes and sensors; the quote lines come to 100 (40 probes plus 60 sensors).
    • 
    

    
4. Site size and stated count: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Veeder-Root TLS-450PLUS tank gauge console with 40 in-tank probes and 60 other sensors, monitoring 32 tanks, with 2 TLS-XB expansion boxes, with digital pressurized line leak detection and Business Inventory Reconciliation, testing 16 lines. The order states 90 probes and sensors in all. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated probes and sensors do not match. The quote states 90 probes and sensors; the quote lines come to 100 (40 probes plus 60 sensors).
    • 
    

    
5. Site size and stated count: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Veeder-Root TLS-450PLUS tank gauge console with 40 in-tank probes and 60 other sensors, monitoring 32 tanks, with 2 TLS-XB expansion boxes, with digital pressurized line leak detection and Business Inventory Reconciliation, testing 16 lines. The order states 100 probes and sensors in all. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 40 probes and 60 sensors (100 in all) against a console maximum of 256 probe and sensor inputs; 2 expansion box(es) against a maximum of 3.
    • 
    

    
6. Options by console: A TLS4 order with HydrX, line leak detection and in-station diagnostics

    
The agent's request. Please quote a Veeder-Root TLS4 tank gauge console with 12 in-tank probes and 20 other sensors, monitoring 12 tanks, with 0 TLS-XB expansion boxes, with digital pressurized line leak detection, in-station diagnostics and HydrX fuel conditioning. The order states 32 probes and sensors in all. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Line leak detection on the wrong console. Digital pressurized line leak detection is listed as an option for the TLS-450PLUS only.
    • 
      
  • In-station diagnostics on the wrong console. In-station diagnostics are listed for the TLS-450PLUS only.
    • 
      
  • HydrX on a TLS4 needs an expansion box. HydrX fuel conditioning on a TLS4 needs one TLS-XB expansion box; the quote has none.
    • 
    

    
7. Options by console: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Veeder-Root TLS-450PLUS tank gauge console with 12 in-tank probes and 20 other sensors, monitoring 12 tanks, with 1 TLS-XB expansion box, with digital pressurized line leak detection, in-station diagnostics and HydrX fuel conditioning. The order states 32 probes and sensors in all. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 12 probes and 20 sensors (32 in all) against a console maximum of 256 probe and sensor inputs; 1 expansion box(es) against a maximum of 3.
    • 
    

  

  

    
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 a Veeder-Root TLS automatic tank gauge console with its expansion boxes, in-tank probes, sensors and optional leak detection and software options. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the specifications Veeder-Root publishes 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 a Veeder-Root TLS4B tank gauge console with 6 in-tank probes and 6 other sensors, monitoring 6 tanks, with 1 TLS-XB expansion box. The order states 12 probes and sensors in all. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with five findings, all in one answer. The quote has 1 TLS-XB expansion box; the selected console supports none. The quote has 12 probes and sensors in all; the selected console has at most 6 universal probe and sensor inputs. The 7-Amp Controller Module is not available on the TLS4B. The other two are on screen.
    6. 
      
  6. The validator returned five 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 probe and sensor counts that depend on the console and its expansion boxes, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the console to TLS4. It sets the DC power input to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All five earlier findings are cleared, and the validator's figure matches the quote.
    13. 
      
  13. Five 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.