Predictika · Tolling reader and transponder quotes

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

An AI sales agent prepares a quote for Kapsch TrafficCom JANUS tolling readers: the reader model, RF modules, antennas, tolling protocols, transponders, synchronization and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the reader line and returns a verdict and every reason.

Scope: Kapsch JANUS 915 MHz readers (MPR2.0, MPR2.3, MPR2.4, MPR4.1) with RF modules, protocols, transponders, synchronization, discount and stated total. See everything this validator covers

This validator models Kapsch JANUS reader quotes, not just the scenarios shown below.

  • Reader and modules — which RF modules each reader takes, how many, and how modules and antennas relate, including redundant operation.
  • Protocols and transponders — how many tolling protocols may run at once, and that each transponder family needs its protocol enabled.
  • Site and commercial checks — cabinet, synchronization spacing and cable lengths, speed, site license, discount approval and the stated total.

Any JANUS reader quote that touches these rules is in scope — not only the scenarios pictured here. Reader, module and protocol names and the module, protocol and synchronization limits follow Kapsch datasheets and FAQ; prices (illustrative dollars), the highway speed threshold, discount thresholds, cabinet quoting and tag pairing are modeled and not published by Kapsch.

The AI sales agentBuilds the reader 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
Modules that depend on the reader modelOnly with care
Each reader needs its own list of allowed module types and counts, and every new model changes those lists.		The reader model, module type and module count are fields of one request and are checked together on every call.
A module limit that changes in redundant modeOnly with workarounds
The limit depends on redundancy, the TDM frame and the number of other protocols at once, so rules must be written for each combination.		Redundancy, module count and protocols are checked together on every call.
Cable and spacing limits across several readersOnly with care
Spacing, segment length and total length are separate numbers that must be tested against each other.		Reader spacing and both cable lengths are checked together on every call.
A stated total that must match the equipmentOnly with care
The total typed into the quote is compared with a sum a pricing rule produces, and the two often drift apart.		The stated total is checked against the computed total on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is saved or 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.

    
1MRFMS+ RF modules cannot be installed in an MPR2.0 reader; MPR2.0 takes its own MRFMS modules.
2An MPR2.4 reader requires at least one MRFMS+ RF module.
3MRFMS and MRFMS+ modules cannot be mixed within a single reader.
4The quote has 9 RF modules per reader; an MPR2 series reader holds at most 8.
5A redundant reader runs more than 5 MRFMS+ modules only with a TDM frame and no more than 2 other protocols.
6The quote has 5 antennas per reader; an MPR4.1 has 4 antenna ports.
7The MPR4.1 is a single-channel four-port reader with no plug-in RF modules; the quote lists 2.
8Redundant operation is an MPR2 series feature; the MPR4.1 is a single-channel reader.
9An MPR2 series reader uses one RF channel per antenna; the quote has 5 antennas for 4 RF modules.
10No tolling protocol is enabled on the reader.
115 protocols are enabled; at most 4 can be active at one time.
124 protocols are active at 65 mph; Kapsch recommends at most three protocols at highway speed, so a specialist should review the protocol setup.
13California Title-21 is listed for the MPR4.1; the other quoted reader datasheets do not list it.
14TDM transponders are quoted but the TDM protocol is not enabled on the reader.
15ISO 18,000-63 (6C) transponders are quoted but the 6C protocol is not enabled on the reader.
16TDMAv6 transponders are not in the reader datasheet protocol lists; a specialist should confirm protocol support.
17This reader is designed for a NEMA 4 cabinet and the quote has no cabinet; only the MPR4.1 mounts outdoors without one.
18Readers closer than 600 feet must be synchronized; the quote has 400 feet and no sync.
19A sync cable segment of 1,600 feet exceeds the 1,500 foot maximum.
202,100 feet of sync cable exceeds the 2,000 foot maximum for all segments to the hub.
21110 mph is above the 100 mph the readers were tested to; a specialist should confirm performance.
22Each site with an operating reader needs an FCC site license; the customer should confirm it.
23A discount of 15 percent needs sales leadership approval.
24The discount is 25 percent; the maximum is 20.
25The quote states a total of 500,000 dollars; the quoted equipment and discount give a different total.

  

  

    
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. Reader, modules and cabinet: An MPR2.0 reader quote with mixed modules, no cabinet, T21 and a 25 percent discount

    
The agent's request. Please quote 2 JANUS MPR2.0 readers, each with 4 MRFMS+ and MRFMS (mixed) RF modules and 4 antennas, protocols TDM, 6C, T21 at 65 mph, 50,000 TDM transponders, with a 25 percent discount. The readers are 800 feet apart and not synchronized. The cabinet is not quoted and the site license is held. The total is $373,800. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • MRFMS+ not allowed in MPR2.0. MRFMS+ RF modules cannot be installed in an MPR2.0 reader; MPR2.0 takes its own MRFMS modules.
    • 
      
  • Mixed MRFMS and MRFMS+ in one reader. MRFMS and MRFMS+ modules cannot be mixed within a single reader.
    • 
      
  • T21 needs MPR4.1. California Title-21 is listed for the MPR4.1; the other quoted reader datasheets do not list it.
    • 
      
  • Cabinet needed for MPR2 and legacy readers. This reader is designed for a NEMA 4 cabinet and the quote has no cabinet; only the MPR4.1 mounts outdoors without one.
    • 
      
  • Discount over the limit. The discount is 25 percent; the maximum is 20.
    • 
    

    
2. Reader, modules and cabinet: The agent resubmits after fixing the errors

    
The agent's request. Please quote 2 JANUS MPR2.3 readers, each with 4 MRFMS RF modules and 4 antennas, protocols TDM, 6C at 65 mph, 50,000 TDM transponders, with a 8 percent discount. The readers are 800 feet apart and not synchronized. The cabinet is quoted and the site license is held. The total is $471,224. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 2 reader(s), 2 protocols enabled, 512,200 dollars before discount.
    • 
    

    
3. Redundancy, protocols and sync: A redundant reader quote with four protocols and sync cable that is too long

    
The agent's request. Please quote 2 JANUS MPR2.4 readers, each with 6 MRFMS+ RF modules and 6 antennas, run redundant, protocols TDM, 6C, 6B, SeGo at 30 mph, 50,000 TDM transponders, with a 5 percent discount. The readers are 400 feet apart and synchronized, with sync cable segments of 1,600 feet and 2,100 feet in all. The cabinet is quoted and the site license is held. The total is $511,670. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Redundant reader with more than 5 MRFMS+ modules. A redundant reader runs more than 5 MRFMS+ modules only with a TDM frame and no more than 2 other protocols.
    • 
      
  • Sync cable segment too long. A sync cable segment of 1,600 feet exceeds the 1,500 foot maximum.
    • 
      
  • Sync cable total too long. 2,100 feet of sync cable exceeds the 2,000 foot maximum for all segments to the hub.
    • 
    

    
4. Redundancy, protocols and sync: The agent resubmits after fixing the errors

    
The agent's request. Please quote 2 JANUS MPR2.4 readers, each with 5 MRFMS+ RF modules and 5 antennas, run redundant, protocols TDM, 6C at 65 mph, 50,000 TDM transponders, with a 5 percent discount. The readers are 400 feet apart and synchronized, with sync cable segments of 1,400 feet and 1,900 feet in all. The cabinet is quoted and the site license is held. The total is $504,450. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 2 reader(s), 2 protocols enabled, 531,000 dollars before discount.
    • 
    

    
5. MPR4.1 limits and approvals: An MPR4.1 quote with RF modules, five antennas, redundancy and TDMAv6 tags at 110 mph

    
The agent's request. Please quote 2 JANUS MPR4.1 readers, each with 5 antennas and 2 RF modules, run redundant, protocols TDM, 6C at 110 mph, 50,000 TDMAv6 transponders, with a 5 percent discount. The readers are 800 feet apart and not synchronized. The cabinet is not quoted and the site license is not held. The total is $602,110. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • MPR4.1 has no RF modules. The MPR4.1 is a single-channel four-port reader with no plug-in RF modules; the quote lists 2.
    • 
      
  • Too many antennas on an MPR4.1. The quote has 5 antennas per reader; an MPR4.1 has 4 antenna ports.
    • 
      
  • Redundancy needs an MPR2 series reader. Redundant operation is an MPR2 series feature; the MPR4.1 is a single-channel reader.
    • 
      
  • Speed above tested 100 mph. 110 mph is above the 100 mph the readers were tested to; a specialist should confirm performance.
    • 
      
  • TDMAv6 tags to confirm. TDMAv6 transponders are not in the reader datasheet protocol lists; a specialist should confirm protocol support.
    • 
      
  • FCC site license not held. Each site with an operating reader needs an FCC site license; the customer should confirm it.
    • 
    

    
6. MPR4.1 limits and approvals: The agent resubmits after fixing the errors

    
The agent's request. Please quote 2 JANUS MPR4.1 readers, each with 4 antennas, protocols 6C at 65 mph, 50,000 6C transponders, with a 5 percent discount. The readers are 800 feet apart and not synchronized. The cabinet is not quoted and the site license is held. The total is $161,310. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 2 reader(s), 1 protocols enabled, 169,800 dollars before discount.
    • 
    

  

  

    
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 Kapsch TrafficCom JANUS tolling readers: the reader model, RF modules, antennas, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the reader line 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 2 JANUS MPR2.0 readers, each with 4 MRFMS+ and MRFMS (mixed) RF modules and 4 antennas, protocols TDM. The readers are 800 feet apart and not synchronized. The rest of the request is on screen. The total is $373,800.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with five findings, all in one answer. MRFMS+ RF modules cannot be installed in an MPR2.0 reader; MPR2.0 takes its own MRFMS modules. MRFMS and MRFMS+ modules cannot be mixed within a single reader. California Title-21 is listed for the MPR4.1; the other quoted reader datasheets do not list it. 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 cable and spacing limits across several readers, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the reader model to MPR2.3, the RF module type to MRFMS, the protocols to TDM, 6C, the cabinet quoted to yes, the discount to 8 percent and the stated total to 471,224.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All five earlier findings are cleared.
    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.