Predictika · Network infrastructure

An AI sales agent's DDI appliance order, checked before it goes out

An AI sales agent prepares an order for Trinzic X6 enterprise DNS, DHCP and IPAM (DDI) appliances: a physical or a software appliance, the model, whether it serves DDI or reporting and analytics, power supplies, NIC card, transceivers, rail kit, deployment platform, indexing capacity and licenses, with the rack units and DNS rate it states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the tables in the public Trinzic X6 datasheet and returns a verdict, every reason and the figures it computed.

Scope: Trinzic X6 enterprise DDI appliances (physical TE-906 to TE-4106, software TE-926 to TE-4126 and TR-5005 reporting): the datasheet's models, options, hosting, capacities and bundled licenses. See everything this validator covers

This validator models one product line, the Trinzic X6 enterprise DNS, DHCP and IPAM (DDI) appliances in the public Trinzic X6 datasheet (version 20260902v4), for any order that touches the rules below, not just the scenarios shown here.

  • Physical appliances — the TE-906, TE-1506, TE-1606, TE-2306 and TE-4106: 1U or 2U, one or two power supplies (a single supply only on the TE-906 and TE-1506), AC power or, for telco use only, DC power (not on the TE-906), the 4 port 1GE NIC card (TE-906) or the quad 10GE NIC card (not on the TE-906), up to four SFP or SFP+ transceivers (none on the TE-906), and a 2-post, up-to-600 mm 4-post or 600 to 900 mm 4-post rail kit that has to match the rack.
  • Software appliances — the TE-926, TE-1516, TE-1526, TE-2326 and TE-4126 on VMware ESXi, Hyper-V, Nutanix AHV, OpenStack or KVM, or in AWS, Google Cloud, Azure or OCI; and the TR-5005 reporting and analytics appliance, which runs on ESXi, Hyper-V, AHV and OpenStack KVM and in AWS and Azure only.
  • Reporting and analytics — hosted on a physical appliance from the TE-1606 up, with the indexing capacity per day limited to 10 GB on the TE-1606, 20 GB on the TE-2306 and 50 GB on the TE-4106, in the tiers 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.
  • Stated figures and licenses — the rack units the order states (one or two per appliance, times the quantity), the DNS queries per second the order states against the datasheet's reference rate for the size, an HA pair of exactly two appliances, and a separate Cloud Platform API, DNS Firewall or DNS Traffic Control license, which the X6 subscription already includes.

Any order for this product line that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (the datasheet publishes none, so this page shows no price build-up), part numbers and SKUs, Network Insight (ND) software, NIOS subscription tiers, Trinzic X5 appliances, Threat Defense, support and warranty upgrades, and CPU, RAM and storage sizing for a particular hypervisor or cloud. The datasheet states that performance numbers are lab reference figures and that some models support only a subset of options, so the final configuration is confirmed with the vendor.

The AI sales agentBuilds the appliance 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
Which options each model offers: single power supply, DC power, NIC card, transceiversOnly with workarounds
The options differ by model (the TE-906 has no DC power, no 10GE card and no transceivers; a single power supply exists only on two models). A rules-based CPQ needs a compatibility table or one rule per model and option, and a new datasheet means editing them.
Model and options arrive in one request and are checked together on every call.
Reporting hosted only from the TE-1606 up, with a daily indexing limit per modelOnly with workarounds
Whether reporting can be hosted, and the largest indexing tier, depend on the model; the valid tiers are a separate list. Rules usually cover the list or the model limit, rarely both.
Model, role and indexing tier are compared together, in any order.
Rail kit against the rack posts and depthOnly with care
A kit is valid only for one rack type and depth range, so the rule has to read two rack fields and the chosen kit.
The kit, posts and depth are compared on every call.
Stated rack units and DNS rate against the datasheetOnly with care
A figure the agent states is just text to a rules-based CPQ unless someone builds a calculation and a comparison for each size.
The units, the size and the datasheet rate are computed on every call, and a difference blocks the order.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a person 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 order has 0 appliances; at least 1 is needed.
2An HA pair is two appliances; the order has 3.
3The TE-1606 comes with two hot-swappable power supplies; a single power supply is offered only on the TE-906 and TE-1506.
4A physical appliance has one or two power supplies; the order has 3.
5The TE-906 has no DC power supply option.
6The DC power supply is a SKU option for telco use only.
7The optional quad 10GE NIC card is not available on the TE-906.
8The 4 port 1GE NIC card is the TE-906 option; the TE-1606 offers no card or the quad 10GE NIC card.
9The TE-906 has no SFP transceiver interfaces.
10An appliance has four SFP or SFP+ interfaces; the order has 5 transceivers.
11The datasheet lists the four SFP or SFP+ interfaces with the 10GE NIC card options; a person should confirm that 2 transceiver(s) can be fitted without the card.
12The 2-post rail kit fits a 2-post rack; the rack has 4 posts.
13The 4-post rail kits fit a 4-post rack; the rack has 2 posts.
14The up-to-600 mm 4-post rail kit needs a rack no deeper than 600 mm; the rack is 750 mm deep.
15The 600 to 900 mm 4-post rail kit needs a rack between 600 and 900 mm deep; the rack is 1,000 mm deep.
16The order states 3 rack units in total; 2 appliance(s) of this model occupy 2.
17The order states 2 rack units in total; 2 appliance(s) of this model occupy 4.
18A software appliance needs a hypervisor or cloud platform to run on.
19Power supplies, power type, NIC cards, transceivers and rail kits apply only to physical appliances.
20A deployment target applies only to software appliances.
21The order states 300,000 DNS queries per second per appliance; the datasheet lists 250,000 for this size.
22The TE-1506 does not host reporting and analytics software; the datasheet lists it from the TE-1606 up.
23The TE-1606 appliance hosts reporting up to 10 GB per day; the order asks for 20,000 MB.
2415 GB per day is not an available indexing capacity; the tiers are 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.
25The TR-5005 software appliance runs on VMware ESXi, Hyper-V, Nutanix AHV and OpenStack KVM, and in AWS and Azure; Google Cloud and OCI are not listed.
26Indexing capacity applies only to reporting and analytics appliances.

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. Large appliance pair with DC power: A pair of TE-2306 physical appliances with DC power and quad 10GE NIC cards

The agent's request. Please quote 2 physical TE-2306 appliances as an HA pair for DNS, DHCP and IPAM, each with 2 power supplies, DC for a telco site, the quad 10GE NIC card, 4 SFP transceivers and the 600 to 900 mm 4-post rail kit, for a 4-post rack 750 mm deep, on the Trinzic X6 subscription. The order states 2 rack units in total and 250,000 DNS queries per second per appliance. It is ready to send.

Verdict: Blocked.

  • DC power is for telco use only. The DC power supply is a SKU option for telco use only.
  • Stated rack units differ from the datasheet. The order states 2 rack units in total; 2 appliance(s) of this model occupy 4.

2. Large appliance pair with DC power: The agent resubmits after fixing the errors

The agent's request. Please quote 2 physical TE-2306 appliances as an HA pair for DNS, DHCP and IPAM, each with 2 power supplies, AC, the quad 10GE NIC card, 4 SFP transceivers and the 600 to 900 mm 4-post rail kit, for a 4-post rack 750 mm deep, on the Trinzic X6 subscription. The order states 4 rack units in total and 250,000 DNS queries per second per appliance. It is ready to send.

Verdict: Allowed.

  • Order summary. 2 physical TE-2306 appliance(s), 4 rack unit(s) in total, about 58 lb in total.

3. Reporting on a cloud platform: A TR-5005 reporting appliance in Google Cloud indexing 15 GB per day

The agent's request. Please quote 1 TR-5005 reporting and analytics software appliance for Google Cloud, indexing 15 GB per day, on the Trinzic X6 subscription. It is ready to send.

Verdict: Blocked.

  • TR-5005 does not run on this platform. The TR-5005 software appliance runs on VMware ESXi, Hyper-V, Nutanix AHV and OpenStack KVM, and in AWS and Azure; Google Cloud and OCI are not listed.
  • Indexing capacity is not an available tier. 15 GB per day is not an available indexing capacity; the tiers are 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.

4. Reporting on a cloud platform: The agent resubmits after fixing the errors

The agent's request. Please quote 1 TR-5005 reporting and analytics software appliance for AWS, indexing 15 GB per day, on the Trinzic X6 subscription. It is ready to send.

Verdict: Blocked.

  • Indexing capacity is not an available tier. 15 GB per day is not an available indexing capacity; the tiers are 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.

5. Reporting on a cloud platform: The agent resubmits after fixing the errors

The agent's request. Please quote 1 TR-5005 reporting and analytics software appliance for AWS, indexing 20 GB per day, on the Trinzic X6 subscription. It is ready to send.

Verdict: Allowed.

6. Branch pair with unconfirmed options: A pair of TE-1506 physical appliances with four transceivers and a DNS Firewall license

The agent's request. Please quote 2 physical TE-1506 appliances as an HA pair for DNS, DHCP and IPAM, each with 1 power supply, AC, no NIC card, 4 SFP transceivers and the up-to-600 mm 4-post rail kit, for a 4-post rack 600 mm deep, on the Trinzic X6 subscription plus a separate DNS Firewall license. The order states 2 rack units in total and 67,500 DNS queries per second per appliance. It is ready to send.

Verdict: Needs approval.

  • Transceivers without the 10 gigabit network card. The datasheet lists the four SFP or SFP+ interfaces with the 10GE NIC card options; a person should confirm that 4 transceiver(s) can be fitted without the card.
  • Separate license already included in the subscription. The Cloud Platform API, DNS Firewall and DNS Traffic Control licenses are included in the Trinzic X6 subscription; a person should confirm that a separate license is intended.
  • Order summary. 2 physical TE-1506 appliance(s), 2 rack unit(s) in total, about 40 lb in total.

7. Branch pair with unconfirmed options: The agent resubmits after fixing the errors

The agent's request. Please quote 2 physical TE-1506 appliances as an HA pair for DNS, DHCP and IPAM, each with 1 power supply, AC, the quad 10GE NIC card, 4 SFP transceivers and the up-to-600 mm 4-post rail kit, for a 4-post rack 600 mm deep, on the Trinzic X6 subscription. The order states 2 rack units in total and 67,500 DNS queries per second per appliance. It is ready to send.

Verdict: Allowed.

  • Order summary. 2 physical TE-1506 appliance(s), 2 rack unit(s) in total, about 40 lb in total.

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 Trinzic X6 enterprise DNS, DHCP and IPAM (DDI) appliances: a physical or a software appliance, the model, whether it serves DDI or reporting and analytics, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the tables in the public Trinzic X6 datasheet and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote 1 TR-5005 reporting and analytics software appliance for Google Cloud, indexing 15 GB per day, on the Trinzic X6 subscription. It is ready to send.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. The TR-5005 software appliance runs on VMware ESXi, Hyper-V, Nutanix AHV and OpenStack KVM, and in AWS and Azure; Google Cloud and OCI are not listed. 15 GB per day is not an available indexing capacity; the tiers are 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.
  6. The validator returned two 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. What this shows: for reporting hosted only from the TE-1606 up, with a daily indexing limit per model, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the platform to AWS.
  10. It calls the validator again.
  11. Still blocked, with one finding, all in one answer. 15 GB per day is not an available indexing capacity; the tiers are 500 MB and 1, 2, 5, 10, 20, 50, 100, 200 and 500 GB.
  12. One finding cleared. Still blocking: indexing capacity is not an available tier.
  13. The agent resubmits once more.
  14. The revised request. It changes the indexing capacity per day to 20 GB.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The earlier finding is cleared.
  18. Two problems caught in one call, fixed in two passes, 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.