Predictika · Network visibility node and license quotes

An AI sales agent's traffic-visibility node quote, checked before it goes out

An AI sales agent prepares a quote for traffic-visibility chassis with GigaSMART modules and application licenses. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the platform and licensing rules and returns a verdict, every reason and the figures it computed.

Scope: GigaVUE HC-series node quotes (HC1, HC1-Plus, HC3 and HCT) with GigaSMART modules, application licenses and support. See everything this validator covers

This validator models GigaVUE HC-series node and license quotes, not just the scenarios shown below.

  • Platform fit — GigaSMART module limits per chassis, the most ports at each speed, total throughput, and the capacity and engine figures a quote states.
  • Application licenses — GigaSMART applications need a GigaSMART module; inline TLS decryption is not available on the HCT.
  • License terms — Node-locked and floating licenses (floating needs GigaVUE-FM and stays within one platform), subscription terms, perpetual licenses with Elite support, evaluation length, hardware-only devices that need an OS license, cluster install order, no transfer of OS licenses, and no automatic renewal on node-locked licenses.

Any HC-series node or license quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Gigamon does not publish list prices, so this validator produces no price build-up or line-item quote), TA-series switches, cloud and virtual deployments, and volume-based cloud licenses. Assumptions: port counts are the datasheet's maximum per speed, so a quote that mixes speeds goes to approval; the 90 percent throughput headroom flag is a sizing guideline set by this model, not a Gigamon rule.

The AI sales agentBuilds the node and license 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.

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
Stated capacity and engine figures that must equal what the quoted chassis and modules actually giveOnly with care
Stated figures are free-entry fields; a rule can compare them with a computed total, but each platform needs its own lookup that has to be kept in step with the datasheets.		The stated figures travel with the quote and are compared with the computed figures on every call.
Limits that differ by platform: modules per chassis, ports at each speed, throughputOnly with care
A product rule per platform and per speed. It works, but every new model is another set of rules to maintain.		Platform limits are looked up from the model and every one is checked together.
A feature license that is not available on one platform (inline TLS decryption on the HCT)Only with workarounds
The restriction depends on a license and a platform on different lines, so it needs a cross-line rule that interacts with the others.		The platform and every license are in one request and the restriction is checked with the rest.
License terms that depend on each other: floating needs GigaVUE-FM, perpetual needs Elite support, hardware-only devices need an OS licenseOnly with workarounds
Each condition looks at a different part of the order, and a missing companion item is usually caught only at the end or not at all.		All items are in one request and every dependency is checked together.
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 5 GigaSMART modules per chassis; this platform holds at most 4.
22 GigaSMART application license(s) are quoted but no GigaSMART module; the applications run only on a GigaSMART module.
3The quote needs 4 ports at 25 Gb; the quoted chassis provide up to 0.
4The quote needs 4 ports at 100 Gb; the quoted chassis provide up to 2.
5The quote needs 800 Gbps of traffic; the quoted chassis give 604 Gbps in total.
6The quote states 6,400 Gbps of capacity; the quoted chassis give 12,800 Gbps.
7The quote states 4 GigaSMART engines; the quoted modules give 8.
8Inline TLS decryption is not supported on the GigaVUE-HCT.
9Floating licenses are bought and managed through GigaVUE-FM, which is not on the quote.
10Subscription terms are monthly or 1, 3, 5 or 7 years; the quote has 24 months.
11A perpetual license does not include Elite support; it is bought separately and is not on the quote.
12An evaluation license lasts 45 days; the quote asks 60 days.
13A device ordered without software (-HW) needs a GigaVUE-OS license on the quote.
14In an inband cluster the GigaVUE-OS licenses must be installed on each node before the cluster is formed.
15GigaVUE-OS and module licenses cannot be transferred between chassis or cards.
16Node-locked licenses are not renewed automatically; automatic renewal is available for floating licenses.

  

  

    
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. Capacity figures: Capacity figure misstated on a two-chassis order

    
The agent's request. Please quote two GigaVUE-HC3 chassis, each with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a 3-year node-locked subscription, for 200 ports at 25 Gb, with 9,000 Gbps of traffic. The quote states 6,400 Gbps of total capacity and 16 GigaSMART engines. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated capacity does not match. The quote states 6,400 Gbps of capacity; the quoted chassis give 12,800 Gbps.
    • 
    

    
2. Capacity figures: The agent resubmits after fixing the errors

    
The agent's request. Please quote two GigaVUE-HC3 chassis, each with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a 3-year node-locked subscription, for 200 ports at 25 Gb, with 9,000 Gbps of traffic. The quote states 12,800 Gbps of total capacity and 16 GigaSMART engines. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 chassis give 12,800 Gbps, 16 GigaSMART engines and 2 application licenses.
    • 
    

    
3. Compact node and TLS: Inline TLS decryption and 100G ports on a compact node

    
The agent's request. Please quote two GigaVUE-HCT chassis, each with 1 GigaSMART module, with De-duplication and inline TLS decryption licenses on a 3-year node-locked subscription, for 6 ports at 100 Gb, with 900 Gbps of traffic. The quote states 1,000 Gbps of total capacity and 2 GigaSMART engines. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • 100G ports exceeded. The quote needs 6 ports at 100 Gb; the quoted chassis provide up to 4.
    • 
      
  • Inline TLS not supported on HCT. Inline TLS decryption is not supported on the GigaVUE-HCT.
    • 
    

    
4. Compact node and TLS: The agent resubmits after fixing the errors

    
The agent's request. Please quote two GigaVUE-HC1-Plus chassis, each with 3 GigaSMART modules, with De-duplication and inline TLS decryption licenses on a 3-year node-locked subscription, for 6 ports at 100 Gb, with 900 Gbps of traffic. The quote states 3,600 Gbps of total capacity and 6 GigaSMART engines. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 chassis give 3,600 Gbps, 6 GigaSMART engines and 2 application licenses.
    • 
    

    
5. Licensing and support: Perpetual license without support and a hardware-only device without an OS license

    
The agent's request. Please quote one GigaVUE-HC3 chassis, ordered as hardware only, with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a perpetual node-locked license, for 96 ports at 25 Gb, with 3,000 Gbps of traffic. The quote states 6,400 Gbps of total capacity and 8 GigaSMART engines. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Perpetual license needs Elite support. A perpetual license does not include Elite support; it is bought separately and is not on the quote.
    • 
      
  • Hardware-only device needs OS license. A device ordered without software (-HW) needs a GigaVUE-OS license on the quote.
    • 
    

    
6. Licensing and support: The agent resubmits after fixing the errors

    
The agent's request. Please quote one GigaVUE-HC3 chassis, ordered as hardware only, with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a perpetual node-locked license, with Elite support and a GigaVUE-OS license, for 64 ports at 25 Gb and 32 ports at 100 Gb, with 3,000 Gbps of traffic. The quote states 6,400 Gbps of total capacity and 8 GigaSMART engines. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Mixed port speeds. The quote mixes 2 port speeds; the datasheet lists the most ports per speed, so the combined port plan needs confirming with Gigamon.
    • 
      
  • Order summary. 1 chassis gives 6,400 Gbps, 8 GigaSMART engines and 2 application licenses.
    • 
    

    
7. Licensing and support: The agent resubmits after fixing the errors

    
The agent's request. Please quote one GigaVUE-HC3 chassis, ordered as hardware only, with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a perpetual node-locked license, with Elite support and a GigaVUE-OS license, for 96 ports at 25 Gb, with 3,000 Gbps of traffic. The quote states 6,400 Gbps of total capacity and 8 GigaSMART engines. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 1 chassis gives 6,400 Gbps, 8 GigaSMART engines and 2 application licenses.
    • 
    

  

  

    
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 traffic-visibility chassis with GigaSMART modules and application licenses. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the platform and licensing rules 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 two GigaVUE-HC3 chassis, each with 4 GigaSMART modules, with De-duplication and NetFlow Generation licenses on a 3-year node-locked subscription. The quote states 6,400 Gbps of total capacity and 16 GigaSMART engines. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding, all in one answer. The quote states 6,400 Gbps of capacity; the quoted chassis give 12,800 Gbps.
    6. 
      
  6. The validator returned one blocking finding 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 stated capacity and engine figures that must equal what the quoted chassis and modules actually give, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the stated capacity to 12,800 Gbps.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. The earlier finding is cleared, and the validator's figure matches the quote.
    13. 
      
  13. One problem 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.