Predictika · Ethernet connectivity orders

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

An AI sales agent prepares an order for a Colt On Demand Ethernet port with one or more circuits. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published port and circuit rules and returns a verdict and every reason.

Scope: Colt On Demand Ethernet orders: ports (on-net data centre, enterprise, hybrid on-net, off-net) and the circuits on them, with speeds, terms, VLAN mode and interfaces. See everything this validator covers

This validator models Colt On Demand Ethernet port and circuit orders, not just the scenarios shown below.

  • Ports — port type, the published port speeds (1, 10 and 100 Gbps on-net; 10 Mbps to 10 Gbps off-net), the contract terms for each location type, and the interface for each speed.
  • Circuits — the published circuit speeds from 10 Mbps to 10 Gbps, plus 20, 30 and 40 Gbps between key data centres, Flex and Traditional terms, and bandwidth downgrades.
  • Port sharing — one circuit on an open port, several with Add VLAN or Filter VLAN, a single circuit on an off-net port, fibre-only cross connects, and booked bandwidth above the port speed.

Any Colt On Demand Ethernet order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Colt publishes only two example port prices and no circuit price list, so this validator produces no price build-up or line-item quote), metro zones, nearnet buildings, cloud ports, internet on demand and other Colt products. Assumptions: the treatment of booked bandwidth above the port speed as a matter for approval is this model's reading of the overbooking note, and the key data centre rule for circuits above 10 Gbps comes from the published connections page.

The AI sales agentBuilds the Ethernet 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.

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
Port terms that depend on the location typeOnly with care
Each location type has its own term rule, so the term check has to sit beside the port type on every line.
The port type and its term are in one request and checked together on every call.
Interfaces that depend on the port speedOnly with care
A product rule per speed and interface pairing; each new interface is another rule to maintain.
Port speed and interface travel together and the pairing is checked on every call.
Circuits that are limited by the port they sit onOnly with workarounds
The circuit speed, the number of circuits and the port speed are on different lines, so the comparisons need cross-line rules.
Port and circuits are one request; speed, count and total are compared together.
Terms and downgrades that depend on the pricing modelOnly with workarounds
Flex and Traditional circuits have different term lists and different downgrade rules, which multiplies the rules.
The pricing model and term are fields of the request and are checked against their own lists on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order 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 order has no circuit on the port.
2On-net, hybrid on-net and nearnet ports come in 1, 10 and 100 Gbps; a 5,000 Mbps port is not available.
3Off-net ports run from 10 Mbps to 10 Gbps; a 100,000 Mbps port is not available.
4Off-net ports run from 10 Mbps to 10 Gbps; a 5 Mbps port is not available.
5A 10 Mbps circuit cannot be faster than the 5 Mbps port.
6On-net data centre ports are available on a 3 or 12 month contract; the order has 6 months.
7Ports at enterprise locations need a minimum 12 month commitment; the order has 6 months.
8Off-net and hybrid on-net ports are available on 12 to 60 month contracts; the order has 72 months.
9Off-net and hybrid on-net ports are available on 12 to 60 month contracts; the order has 6 months.
10A circuit speed of 75 Mbps is not available; speeds run 10 Mbps to 10 Gbps in published steps, plus 20, 30 and 40 Gbps between key data centres.
11A 2,000 Mbps circuit cannot be faster than the 1,000 Mbps port.
12A 40,000 Mbps circuit is available only between key data centres and on a 100 Gbps port.
13A 20,000 Mbps circuit is available only between key data centres and on a 100 Gbps port.
14The chosen optical or electrical interface is not available at the 10,000 Mbps port speed; 1 Gbps uses 1,000Base-LX, SX or T, 10 Gbps uses 10GBASE-LR or SR, and 100 Gbps uses 100GBASE-LR4 or SR4.
15This circuit pricing model does not offer a term of 5 months; Flex offers 1 hour or 3, 6, 12, 24 or 36 months, and Traditional offers 12, 24 or 36 months (0 means 1 hour).
16This circuit pricing model does not offer a term of 3 months; Flex offers 1 hour or 3, 6, 12, 24 or 36 months, and Traditional offers 12, 24 or 36 months (0 means 1 hour).
17This circuit pricing model does not offer a term of 0 months; Flex offers 1 hour or 3, 6, 12, 24 or 36 months, and Traditional offers 12, 24 or 36 months (0 means 1 hour).
18Bandwidth can be flexed down only on a 1 hour Flex contract; other circuits can be upgraded but not downgraded.
19An open port carries one circuit; 4 circuits need Add VLAN or Filter VLAN mode.
20An off-net port supports a single circuit as standard; the order has 2 circuits.
21Only fibre cross connects are supported; copper cross connects are not.
22The circuits total 12,000 Mbps on a 10,000 Mbps port; overbooking is available on request for NNI ports only, so a person should confirm.
23A 5,000 Mbps circuit cannot be faster than the 1,000 Mbps port.

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. Terms, interface and port sharing: A six-circuit Traditional order on a 6-month data centre port with a mismatched interface, an open port and a copper cross connect

The agent's request. Please order an on-net data centre port at 10 Gbps on a 6-month contract with 1000Base-SX interface and a copper cross connect, carrying 6 circuits of 500 Mbps each on Traditional pricing with a 6-month term, in open-port mode. It is ready to send.

Verdict: Blocked.

  • Data centre port term. On-net data centre ports are available on a 3 or 12 month contract; the order has 6 months.
  • Interface does not match the port speed. The chosen optical or electrical interface is not available at the 10,000 Mbps port speed; 1 Gbps uses 1,000Base-LX, SX or T, 10 Gbps uses 10GBASE-LR or SR, and 100 Gbps uses 100GBASE-LR4 or SR4.
  • Circuit term not available. This circuit pricing model does not offer a term of 6 months; Flex offers 1 hour or 3, 6, 12, 24 or 36 months, and Traditional offers 12, 24 or 36 months (0 means 1 hour).
  • Open port carries one circuit. An open port carries one circuit; 6 circuits need Add VLAN or Filter VLAN mode.
  • Copper cross connects are not offered. Only fibre cross connects are supported; copper cross connects are not.

2. Terms, interface and port sharing: The agent resubmits after fixing the errors

The agent's request. Please order an on-net data centre port at 10 Gbps on a 12-month contract with 10GBASE-LR interface and a fibre cross connect, carrying 6 circuits of 500 Mbps each on Flex pricing with a 12-month term, in Add VLAN mode. It is ready to send.

Verdict: Allowed.

  • Order summary. 6 circuit(s) totalling 3,000 Mbps on a 10,000 Mbps port.

3. Off-net port: An off-net port with three circuits and a short port term

The agent's request. Please order an off-net port at 1 Gbps on a 6-month contract with 1000Base-LX interface and a fibre cross connect, carrying 3 circuits of 200 Mbps each on Flex pricing with a 12-month term, in Add VLAN mode. It is ready to send.

Verdict: Blocked.

  • Hybrid and off-net port term. Off-net and hybrid on-net ports are available on 12 to 60 month contracts; the order has 6 months.
  • Off-net port carries one circuit. An off-net port supports a single circuit as standard; the order has 3 circuits.

4. Off-net port: The agent resubmits after fixing the errors

The agent's request. Please order an off-net port at 1 Gbps on a 24-month contract with 1000Base-LX interface and a fibre cross connect, carrying 1 circuit of 200 Mbps on Flex pricing with a 12-month term, in Add VLAN mode. It is ready to send.

Verdict: Allowed.

  • Order summary. 1 circuit(s) totalling 200 Mbps on a 1,000 Mbps port.

5. Circuits above 10 Gbps: A 40 Gbps circuit on a 10 Gbps data centre port

The agent's request. Please order an on-net data centre port at 10 Gbps on a 12-month contract with 10GBASE-LR interface and a fibre cross connect, carrying 1 circuit of 40 Gbps on Flex pricing with a 12-month term, in Add VLAN mode. It is ready to send.

Verdict: Blocked.

  • Circuits above 10 Gbps. A 40,000 Mbps circuit is available only between key data centres and on a 100 Gbps port.

6. Circuits above 10 Gbps: The agent resubmits after fixing the errors

The agent's request. Please order an on-net data centre port at 100 Gbps on a 12-month contract with 100GBASE-LR4 interface and a fibre cross connect, carrying 1 circuit of 40 Gbps on Flex pricing with a 12-month term, in Add VLAN mode, between two key data centres. It is ready to send.

Verdict: Allowed.

  • Order summary. 1 circuit(s) totalling 40,000 Mbps on a 100,000 Mbps port.

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 a Colt On Demand Ethernet port with one or more circuits. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published port and circuit rules and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please order an on-net data centre port at 10 Gbps on a 6-month contract. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with five findings, all in one answer. On-net data centre ports are available on a 3 or 12 month contract; the order has 6 months. The chosen optical or electrical interface is not available at the 10,000 Mbps port speed; 1 Gbps uses 1,000Base-LX, SX or T, 10 Gbps uses 10GBASE-LR or SR, and 100 Gbps uses 100GBASE-LR4 or SR4. This circuit pricing model does not offer a term of 6 months; Flex offers 1 hour or 3, 6, 12, 24 or 36 months, and Traditional offers 12, 24 or 36 months (0 means 1 hour). The other two are on screen.
  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. What this shows: for interfaces that depend on the port speed, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the port term to 12 months, the interface to 10GBASE-LR, the cross connect to fibre and the circuit pricing model to flex. Two more changes are on screen.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All five earlier findings are cleared.
  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.