Predictika · Switched Ethernet service quotes

An AI sales agent's Switched Ethernet quote, checked before it goes out

An AI sales agent prepares a Switched Ethernet quote for a business customer: the service (Dedicated Ethernet, E-Line or E-LAN), the number of sites, the port speed, the EVC bandwidth, the class of service and its bandwidth allocations, the term, and the monthly charge the quote states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of how these choices fit together, and returns a verdict, every reason and the monthly charge it computed.

Scope: One Switched Ethernet quote: service, sites, port, EVC bandwidth, class of service, term and the stated monthly charge. See everything this validator covers

This validator models Switched Ethernet quotes for three services, not just the scenarios shown below.

  • Service and sites — Dedicated Ethernet and E-Line as point-to-point services with two sites, E-LAN as a multipoint service with at least three, and one EVC per Dedicated Ethernet port.
  • Port and EVC bandwidth — the offered EVC sizes, the port speeds from 100 Mbps to 100 Gbps, and an EVC that cannot be faster than its port.
  • Class of service — Fixed CoS (Standard, Expedite, Critical) and Per-Packet CoS (Critical, Real-Time), which classes may carry bandwidth allocations, and allocations that cannot add up to more than the EVC.
  • Approvals and the stated charge — a capacity check at 10 Gbps and above, a check for a 100 Gbps port, a review of very large E-LANs and of mostly real-time traffic, and the monthly charge on the quote, which is compared with the computed one.

Any Switched Ethernet quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Consolidated Communications services. The service and class-of-service names come from public Consolidated Communications pages; the offered sizes, limits, approval thresholds and all prices are modeled from comparable carrier Ethernet products and are not published by Consolidated Communications.

The AI sales agentBuilds the quote from the conversation with the customer and says it is ready to send.
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
Site count that depends on the serviceOnly with workarounds
Dedicated Ethernet and E-Line need exactly two sites while E-LAN needs at least three, and Dedicated Ethernet allows one EVC per port, so each service needs its own rule on the site count and the EVCs.
Service, sites and EVCs are fields of one quote and are checked together on every call.
EVC bandwidth that depends on the portOnly with care
The EVC must be one of the offered sizes and cannot be faster than the port, so a list of sizes and a comparison with the port speed must be kept in step.
Port and bandwidth are fields of one quote and are compared on every call.
Class of service that decides which allocations are allowedOnly with workarounds
A Fixed class cannot carry per-class bandwidth, Critical Per-Packet CoS needs a critical allocation and no real-time one, Real-Time needs a real-time allocation, and the allocations cannot exceed the EVC.
The class of service and its allocations are fields of one quote and are checked together on every call.
Approvals that stack on top of blocksOnly with workarounds
A very fast EVC or a very large E-LAN needs a person while a wrong port or site count stops the quote outright, and a person should see them all at once.
Blocks and approvals are all reported together, so one problem never hides another.
A stated charge that must match the computed oneOnly with workarounds
The monthly charge adds the port, the per-Mbps rate for the size, the class of service and monitoring for every site, with a discount for the term, so a separate rule must recompute it and compare it with the stated figure.
The stated charge is a field of the quote and is compared with the computed charge on every call.

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.

1An EVC bandwidth of 4 Mbps is not an offered size; sizes start at 3 Mbps and step up to 100 Gbps.
2The EVC bandwidth of 2,000 Mbps is above the 1,000 Mbps speed of the selected port.
3An EVC of 10,000 Mbps needs a capacity check on the network before it is quoted.
4A 100 Gbps port needs a site and equipment check before it is quoted.
5Dedicated Ethernet and E-Line are point-to-point services; the order has 3 sites.
6E-LAN is a multipoint service; the order has 2 sites and needs at least 3.
7An E-LAN with 21 sites is larger than the usual design and needs a network engineer to review it.
8Dedicated Ethernet is one point-to-point connection per port; the order has 2 EVCs per port.
9Each port needs at least one EVC; the order has 0.
10A Fixed class of service gives every packet the same priority level, so it cannot carry per-class bandwidth (50 Mbps real-time, 0 Mbps critical); use Per-Packet CoS.
11Critical Per-Packet CoS has a Critical class, and the order allocates 0 Mbps to it.
12Critical Per-Packet CoS has only the Critical and Standard classes; 50 Mbps is allocated to real-time traffic.
13Real-Time Per-Packet CoS has a Real Time class, and the order allocates 0 Mbps to it.
14300 Mbps of real-time traffic is more than half of the 500 Mbps EVC; a person should confirm the traffic profile.
15The real-time (300 Mbps) and critical (300 Mbps) allocations add up to more than the 500 Mbps EVC.
16The order states a monthly charge of $10; the quote computes $3,690.

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. E-LAN quote: An E-LAN for 2 sites with a 25 Gbps EVC on a 1 Gbps port and Critical Per-Packet CoS

The agent's request. Please quote an E-LAN for 2 sites with a 25,000 Mbps EVC on a 1 Gbps port, Critical Per-Packet CoS, 1 EVC on the port and a 36-month term. The quote states a monthly charge of $3,690. It is ready to send.

Verdict: Blocked.

  • EVC bandwidth above the port speed. The EVC bandwidth of 25,000 Mbps is above the 1,000 Mbps speed of the selected port.
  • E-LAN with fewer than three sites. E-LAN is a multipoint service; the order has 2 sites and needs at least 3.
  • Critical PPCoS without critical bandwidth. Critical Per-Packet CoS has a Critical class, and the order allocates 0 Mbps to it.
  • Stated monthly charge does not match. The order states a monthly charge of $3,690; the quote computes $45,540.
  • Capacity of 10 Gbps or more. An EVC of 25,000 Mbps needs a capacity check on the network before it is quoted.

2. E-LAN quote: The agent resubmits after fixing the errors

The agent's request. Please quote an E-LAN for 5 sites with a 25,000 Mbps EVC on a 10 Gbps port, Critical Per-Packet CoS, 1 EVC on the port and a 36-month term. The class allocations are 2,000 Mbps critical. The quote states a monthly charge of $3,690. It is ready to send.

Verdict: Blocked.

  • EVC bandwidth above the port speed. The EVC bandwidth of 25,000 Mbps is above the 10,000 Mbps speed of the selected port.
  • Stated monthly charge does not match. The order states a monthly charge of $3,690; the quote computes $117,900.
  • Capacity of 10 Gbps or more. An EVC of 25,000 Mbps needs a capacity check on the network before it is quoted.

3. E-LAN quote: The agent resubmits after fixing the errors

The agent's request. Please quote an E-LAN for 5 sites with a 5,000 Mbps EVC on a 10 Gbps port, Critical Per-Packet CoS, 1 EVC on the port and a 36-month term. The class allocations are 2,000 Mbps critical. The quote states a monthly charge of $42,650. It is ready to send.

Verdict: Allowed.

  • Charge summary. 5 site(s); 5,000 Mbps EVC; modeled monthly charge $42,650, contract value $1,535,400.

4. Real-time traffic quote: Dedicated Ethernet with Expedite Fixed CoS, 100 Mbps of real-time traffic and 2 EVCs on the port

The agent's request. Please quote Dedicated Ethernet for 2 sites with a 400 Mbps EVC on a 1 Gbps port, Expedite Fixed CoS, 2 EVCs on the port and a 36-month term. The class allocations are 100 Mbps real-time. The quote states a monthly charge of $3,690. It is ready to send.

Verdict: Blocked.

  • Dedicated Ethernet with several EVCs on a port. Dedicated Ethernet is one point-to-point connection per port; the order has 2 EVCs per port.
  • Per-class bandwidth on a Fixed class of service. A Fixed class of service gives every packet the same priority level, so it cannot carry per-class bandwidth (100 Mbps real-time, 0 Mbps critical); use Per-Packet CoS.
  • Stated monthly charge does not match. The order states a monthly charge of $3,690; the quote computes $3,260.

5. Real-time traffic quote: The agent resubmits after fixing the errors

The agent's request. Please quote Dedicated Ethernet for 2 sites with a 400 Mbps EVC on a 1 Gbps port, Real-Time Per-Packet CoS, 1 EVC on the port and a 36-month term. The class allocations are 100 Mbps real-time and 100 Mbps critical. The quote states a monthly charge of $3,700. It is ready to send.

Verdict: Allowed.

  • Charge summary. 2 site(s); 400 Mbps EVC; modeled monthly charge $3,700, contract value $133,200.

6. Branch office quote: An E-Line for 3 sites on a 100 Mbps port with a 200 Mbps EVC and allocations of 150 and 100 Mbps

The agent's request. Please quote an E-Line for 3 sites with a 200 Mbps EVC on a 100 Mbps port, Real-Time Per-Packet CoS, 1 EVC on the port and a 36-month term. The class allocations are 150 Mbps real-time and 100 Mbps critical. The quote states a monthly charge of $3,690. It is ready to send.

Verdict: Blocked.

  • EVC bandwidth above the port speed. The EVC bandwidth of 200 Mbps is above the 100 Mbps speed of the selected port.
  • Point-to-point service with other than two sites. Dedicated Ethernet and E-Line are point-to-point services; the order has 3 sites.
  • Class bandwidth above the EVC bandwidth. The real-time (150 Mbps) and critical (100 Mbps) allocations add up to more than the 200 Mbps EVC.
  • Stated monthly charge does not match. The order states a monthly charge of $3,690; the quote computes $2,694.
  • Mostly real-time traffic. 150 Mbps of real-time traffic is more than half of the 200 Mbps EVC; a person should confirm the traffic profile.

7. Branch office quote: The agent resubmits after fixing the errors

The agent's request. Please quote an E-Line for 2 sites with a 200 Mbps EVC on a 1 Gbps port, Real-Time Per-Packet CoS, 1 EVC on the port and a 60-month term, with Proactive Monitoring. The class allocations are 80 Mbps real-time and 80 Mbps critical. The quote states a monthly charge of $2,090. It is ready to send.

Verdict: Allowed.

  • Charge summary. 2 site(s); 200 Mbps EVC; modeled monthly charge $2,090, contract value $125,400.

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 Switched Ethernet quote for a business customer: the service (Dedicated Ethernet, E-Line or E-LAN), the number of sites, the port speed, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of how these choices fit together, and returns a verdict, every reason and the monthly charge it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote an E-LAN for 2 sites with a 25,000 Mbps EVC on a 1 Gbps port, Critical Per-Packet CoS, 1 EVC on the port and a 36-month term. The quote states a monthly charge of $3,690. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with four findings and one approval, all in one answer. The EVC bandwidth of 25,000 Mbps is above the 1,000 Mbps speed of the selected port. E-LAN is a multipoint service; the order has 2 sites and needs at least 3. Critical Per-Packet CoS has a Critical class, and the order allocates 0 Mbps to it. The other one is on screen.
  6. The validator returned four blocking findings and one approval 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 EVC bandwidth that depends on the port, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the sites to 5, the port speed to 10 Gbps and the critical allocation to 2,000 Mbps.
  10. It calls the validator again.
  11. Still blocked, with two findings and one approval, all in one answer. The EVC bandwidth of 25,000 Mbps is above the 10,000 Mbps speed of the selected port. The order states a monthly charge of $3,690; the quote computes $117,900.
  12. Two findings cleared. Still blocking: EVC bandwidth above the port speed and stated monthly charge does not match. One approval also remains for a person: capacity of 10 Gbps or more.
  13. The agent resubmits once more.
  14. The revised request. It changes the EVC bandwidth to 5,000 Mbps and the monthly charge stated on the quote to $42,650.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. All three earlier findings are cleared.
  18. Five 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.