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

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator

Waiting for the call.

What this means

Run the validator to see the outcome

The explanation appears here once the validator returns.

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 caught	Typical rules-based CPQ	Predictika
Stated capacity and engine figures that must equal what the quoted chassis and modules actually give	Only 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, throughput	Only 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 license	Only 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 answer	Only 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.

1	The quote has 5 GigaSMART modules per chassis; this platform holds at most 4.
2	2 GigaSMART application license(s) are quoted but no GigaSMART module; the applications run only on a GigaSMART module.
3	The quote needs 4 ports at 25 Gb; the quoted chassis provide up to 0.
4	The quote needs 4 ports at 100 Gb; the quoted chassis provide up to 2.
5	The quote needs 800 Gbps of traffic; the quoted chassis give 604 Gbps in total.
6	The quote states 6,400 Gbps of capacity; the quoted chassis give 12,800 Gbps.
7	The quote states 4 GigaSMART engines; the quoted modules give 8.
8	Inline TLS decryption is not supported on the GigaVUE-HCT.
9	Floating licenses are bought and managed through GigaVUE-FM, which is not on the quote.
10	Subscription terms are monthly or 1, 3, 5 or 7 years; the quote has 24 months.
11	A perpetual license does not include Elite support; it is bought separately and is not on the quote.
12	An evaluation license lasts 45 days; the quote asks 60 days.
13	A device ordered without software (-HW) needs a GigaVUE-OS license on the quote.
14	In an inband cluster the GigaVUE-OS licenses must be installed on each node before the cluster is formed.
15	GigaVUE-OS and module licenses cannot be transferred between chassis or cards.
16	Node-locked licenses are not renewed automatically; automatic renewal is available for floating licenses.