Predictika · Ethernet service orders

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

An AI sales agent prepares an order for an Ethernet service: the service type, the client handoff, the bandwidth, the fibre run, the number of sites and the VLAN mapping. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published Ethernet Services Technical Overview and returns a verdict, every reason and the figures it computed.

Scope: Zayo Ethernet service orders: service type, client handoff, bandwidth, fibre reach, sites and VLAN mapping. See everything this validator covers

This validator models Ethernet service orders built on the public Zayo Ethernet Services Technical Overview (EPL, EVPL and ELAN), not just the scenarios shown below.

  • Bandwidth — the sizes the overview lists (100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps), compared with the line rate of the client handoff the order selects. The comparison with the line rate is a consistency check the validator adds; it is not a rule Zayo publishes.
  • Client handoff and reach — ten handoff types from 100 Mbps copper to 100GBASE-ER4, each with the reach the overview lists (for 10GBASE-SR the reach depends on the fibre grade, OM1 to OM4). A run past the listed reach is blocked; a run in the range where reach depends on fibre quality or link budget, and any 10GBASE-ZR handoff, goes to a person to confirm with Zayo.
  • Service structure — an Ethernet Private Line is provisioned between two ports with one EVC per port, an EVPL carries VLAN IDs for each EVC, and any service needs at least two sites. The port speed the order states is compared with the handoff line rate.

Any Ethernet service order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Zayo does not publish them, so this validator produces no price build-up or line-item quote), wavelengths, dark fibre, class of service, protection, availability, and diverse routing.

The AI sales agentBuilds the Ethernet service 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
A bandwidth that is not an offered sizeOnly with care
The offered sizes are a set of steps that change at 1 and 10 Gbps, so the rule needs a list or arithmetic per band, kept in step with the product sheet.		The bandwidth is in the same request as everything else and is checked on every call.
A reach that depends on the handoff and the fibreOnly with workarounds
The limit depends on the optic chosen and, for 10G-SR, on the fibre grade, so it takes a cross-field rule with a table behind it.		Handoff, fibre grade and distance are checked together, in whatever order they were chosen.
A reach range that needs a person to confirmOnly with workarounds
A run between the clear range and the maximum is neither right nor wrong; a rule engine tends to pass it or block it.		It comes back as a separate approval, listed next to the blocking findings.
EVCs and VLAN IDs that must match the service typeOnly with care
The limits differ for EPL, EVPL and ELAN, so each service type needs its own rule across several fields.		Service type, EVC count and VLAN IDs travel in one request and are compared 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.

    
1A bandwidth of 150 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
2A bandwidth of 1500 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
3A bandwidth of 15000 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
4The service bandwidth of 15000 Mbps is above the 10000 Mbps line rate of the selected client handoff.
5A bandwidth of 50000 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
6The service bandwidth of 2000 Mbps is above the 1000 Mbps line rate of the selected client handoff.
7The service bandwidth of 200 Mbps is above the 100 Mbps line rate of the selected client handoff.
8The fibre run of 101 metres is beyond the 100 metre reach listed for the selected client handoff.
9The fibre run of 276 metres is within the listed reach range for the handoff but past 275 metres, where reach depends on the fibre grade or on link budget engineering; Zayo should confirm it.
10The fibre run of 551 metres is beyond the 550 metre reach listed for the selected client handoff.

  

  

    
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. Bandwidth and fibre reach: A 2.5 Gbps order on 450 metres of OM3 fibre

    
The agent's request. Please quote an Ethernet Private Line (EPL) with 2 sites, 2500 Mbps of service on a 10GBASE-SR client handoff over OM3 fibre, a fibre run of 450 metres, 1 EVCs per port and 1 VLAN IDs. The order states a 10000 Mbps port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Bandwidth not an offered size. A bandwidth of 2500 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
    • 
      
  • Fibre run beyond the listed reach. The fibre run of 450 metres is beyond the 300 metre reach listed for the selected client handoff.
    • 
    

    
2. Bandwidth and fibre reach: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Ethernet Private Line (EPL) with 2 sites, 3000 Mbps of service on a 10GBASE-SR client handoff over OM4 fibre, a fibre run of 450 metres, 1 EVCs per port and 1 VLAN IDs. The order states a 10000 Mbps port. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 sites; 3000 Mbps of service on a 10000 Mbps client handoff with a 450 metre fibre run.
    • 
    

    
3. Handoff speed and VLAN mapping: An EVPL on a 1 Gbps copper handoff at 2 Gbps, with 3 VLAN IDs for 4 EVCs

    
The agent's request. Please quote an Ethernet Virtual Private Line (EVPL) with 2 sites, 2000 Mbps of service on a 1 Gbps copper client handoff, a fibre run of 80 metres, 4 EVCs per port and 3 VLAN IDs. The order states a 10000 Mbps port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Bandwidth above the handoff speed. The service bandwidth of 2000 Mbps is above the 1000 Mbps line rate of the selected client handoff.
    • 
      
  • EVC without a VLAN ID. EVPL maps one or more VLAN IDs to each EVC; the order has 3 VLAN IDs for 4 EVCs per port.
    • 
      
  • Stated port speed does not match. The order states a 10000 Mbps port; the selected client handoff has a 1000 Mbps line rate.
    • 
    

    
4. Handoff speed and VLAN mapping: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Ethernet Virtual Private Line (EVPL) with 2 sites, 2000 Mbps of service on a 10GBASE-SR client handoff over OM3 fibre, a fibre run of 80 metres, 4 EVCs per port and 3 VLAN IDs. The order states a 10000 Mbps port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • EVC without a VLAN ID. EVPL maps one or more VLAN IDs to each EVC; the order has 3 VLAN IDs for 4 EVCs per port.
    • 
    

    
5. Handoff speed and VLAN mapping: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Ethernet Virtual Private Line (EVPL) with 2 sites, 2000 Mbps of service on a 10GBASE-SR client handoff over OM3 fibre, a fibre run of 80 metres, 4 EVCs per port and 4 VLAN IDs. The order states a 10000 Mbps port. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 sites; 2000 Mbps of service on a 10000 Mbps client handoff with an 80 metre fibre run.
    • 
    

    
6. 100G handoff, bandwidth and reach: A 50 Gbps order on a 100GBASE-LR4 handoff over 12 km

    
The agent's request. Please quote an Ethernet Private Line (EPL) with 2 sites, 50000 Mbps of service on a 100GBASE-LR4 client handoff, a fibre run of 12000 metres, 1 EVCs per port and 1 VLAN IDs. The order states a 100000 Mbps port. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Bandwidth not an offered size. A bandwidth of 50000 Mbps is not offered; Zayo lists 100 to 900 Mbps in steps of 100, 1 to 9 Gbps in steps of 1 Gbps and 10 to 40 Gbps in steps of 10 Gbps.
    • 
      
  • Fibre run beyond the listed reach. The fibre run of 12000 metres is beyond the 8000 metre reach listed for the selected client handoff.
    • 
    

    
7. 100G handoff, bandwidth and reach: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Ethernet Private Line (EPL) with 2 sites, 40000 Mbps of service on a 100GBASE-ER4 client handoff, a fibre run of 12000 metres, 1 EVCs per port and 1 VLAN IDs. The order states a 100000 Mbps port. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 sites; 40000 Mbps of service on a 100000 Mbps client handoff with a 12000 metre fibre run.
    • 
    

  

  

    
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 an Ethernet service: the service type, the client handoff, the bandwidth, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published Ethernet Services Technical Overview 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 an Ethernet Virtual Private Line (EVPL) with 2 sites, 2000 Mbps of service on a 1 Gbps copper client handoff. The order states a 10000 Mbps port. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings, all in one answer. The service bandwidth of 2000 Mbps is above the 1000 Mbps line rate of the selected client handoff. EVPL maps one or more VLAN IDs to each EVC; the order has 3 VLAN IDs for 4 EVCs per port. The order states a 10000 Mbps port; the selected client handoff has a 1000 Mbps line rate.
    6. 
      
  6. The validator returned three 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. 
      
  7. What this shows: for EVCs and VLAN IDs that must match the service type, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the client handoff to 10GBASE-SR. It sets the fibre type to OM3.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. EVPL maps one or more VLAN IDs to each EVC; the order has 3 VLAN IDs for 4 EVCs per port.
    12. 
      
  12. Two findings cleared. Still blocking: EVC without a VLAN ID.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the VLAN IDs to 4.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the quote.
    18. 
      
  18. Three 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.
    19.