Predictika · Interconnection service orders

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

An AI sales agent prepares an order for a virtual connection: a layer 2 link to a cloud, a Digital Internet service or a bare metal server link. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of what the public ServiceFabric User Guide says and returns a verdict, every reason and the figures it computed.

Scope: ServiceFabric cloud links, Digital Internet and bare metal server links: speeds, cloud credentials, VLAN tagging, IP blocks, routing options and speed changes. See everything this validator covers

This validator models ServiceFabric orders based on the public ServiceFabric User Guide, not just the scenarios shown below.

  • Links to clouds and servers — the speeds the guide lists (50 Mbps to 100 Gbps, where the provider supports them); an Amazon AWS link uses the account ID while Azure, Google Cloud, IBM Cloud and Oracle Cloud use a service key; Azure does not accept untagged on the A-side, and its Single Peering VLAN option rules out Q-in-Q and untagged.
  • VLAN tagging and speed changes — an untagged port allows only one virtual cross connect; AWS links cannot change speed and Azure links can only be increased.
  • Digital Internet — 50 Mbps to 10 Gbps within the port's region; Basic is a single IP with no BGP; 1 to 10 WAN IP blocks, up to 10 routed LAN blocks and up to 10 private BGP blocks; a virtual router A-side needs an MTU of 1500 to 9100; public BGP with customer-owned blocks needs approval from the account team, and partner-served locations may not offer extra IPs or BGP.
  • Bare metal servers — the SSH key must be RSA or Ed25519, and Hivelocity supports only one virtual cross connect per server.

Any ServiceFabric order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (ServiceFabric prices are shown in the customer portal only, so this page shows no price build-up), ports and port groups, virtual routers beyond the MTU range, and the bare metal server configurations of the partners.

The AI sales agentBuilds the interconnection 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
Credentials that depend on the cloudOnly with care
A product rule per cloud and credential type, repeated whenever a provider is added.		The cloud and the credential are in one request and checked together.
VLAN limits that depend on the cloud and on what is already on the portOnly with workarounds
The untagged limit depends on how many cross connects the port already carries and the Azure limit on the cloud chosen, so rules must read data from other lines.		The cloud, the tagging and the existing cross connects are checked together on every call.
Rules that change when an existing service is editedOnly with care
New orders and speed changes follow different rules per cloud (AWS cannot change, Azure can only increase), so each needs its own rule.		The action, the current speed and the new speed arrive in one request.
A service tier that removes optionsOnly with care
Basic Internet has no BGP and no extra IP blocks, so each option needs a rule that reads the tier.		The tier and every option are checked together.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote 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.

    
1A link speed of 75 Mbps is not offered; links and connections support 50, 100, 200, 300, 400 and 500 Mbps and 1, 2, 2.5, 5, 10 and 100 Gbps, where the service provider supports them.
2A link to Amazon AWS is ordered with the AWS account ID; a service key is not used.
3Azure, Google Cloud, IBM Cloud and Oracle Cloud links use a service key rather than an account ID.
4Microsoft Azure does not support untagged mode on the A-side.
5With the Single Peering VLAN option the A-side cannot use Q-in-Q or untagged.
6An untagged port allows only one virtual cross connect and this port already has 2, so untagged cannot be selected.
7Connections to Amazon AWS do not support updating the speed.
8Connections to Microsoft Azure can only be increased in speed; the change is from 2000 Mbps to 1000 Mbps.
9Digital Internet speeds run from 50 Mbps to 10 Gbps; the order has 20000 Mbps.
10Digital Internet speeds run from 50 Mbps to 10 Gbps; the order has 25 Mbps.
11Digital Internet is available only within the same region as the port; a port in one region cannot attach to Digital Internet in another.
12At least one IP block must be assigned to the WAN port and up to 10 blocks can be rented; the order has 11.
13At least one IP block must be assigned to the WAN port and up to 10 blocks can be rented; the order has 0.
14Digital Realty can lease up to 10 additional routed LAN blocks; the order has 11.
15Private BGP supports up to 10 IP blocks; the order has 11.
16Basic Internet is a single-IP connection and does not include public or private BGP.
17Basic Internet is a single-IP connection and does not include multiple IP blocks.
18An MTU of 9500 is outside the supported range of 1500 to 9100 for the virtual router.
19An MTU of 1400 is outside the supported range of 1500 to 9100 for the virtual router.
20Public BGP with customer-owned IP blocks needs approval from the Digital Realty account team, with the IP ranges and proof of ownership; a person should confirm it.
21At a location served by a partner, additional IP addresses and BGP routing may not be supported; a person should confirm the location offers them.
22The bare metal server SSH key must be in RSA or Ed25519 format.

  

  

    
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. Azure link to a busy port: Azure link ordered with an account ID, untagged on a port with two cross connects, at 750 Mbps

    
The agent's request. Please order a layer 2 link to Microsoft Azure at 750 Mbps, identified with the account ID, with untagged traffic on the A-side on a port that already carries 2 virtual cross connects. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Link speed is not offered. A link speed of 750 Mbps is not offered; links and connections support 50, 100, 200, 300, 400 and 500 Mbps and 1, 2, 2.5, 5, 10 and 100 Gbps, where the service provider supports them.
    • 
      
  • This cloud needs a service key. Azure, Google Cloud, IBM Cloud and Oracle Cloud links use a service key rather than an account ID.
    • 
      
  • Azure does not support untagged on the A-side. Microsoft Azure does not support untagged mode on the A-side.
    • 
      
  • Untagged port allows one cross connect. An untagged port allows only one virtual cross connect and this port already has 2, so untagged cannot be selected.
    • 
    

    
2. Azure link to a busy port: The agent resubmits after fixing the errors

    
The agent's request. Please order a layer 2 link to Microsoft Azure at 500 Mbps, identified with a service key, with untagged traffic on the A-side on a port that already carries 2 virtual cross connects. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Azure does not support untagged on the A-side. Microsoft Azure does not support untagged mode on the A-side.
    • 
      
  • Untagged port allows one cross connect. An untagged port allows only one virtual cross connect and this port already has 2, so untagged cannot be selected.
    • 
    

    
3. Azure link to a busy port: The agent resubmits after fixing the errors

    
The agent's request. Please order a layer 2 link to Microsoft Azure at 500 Mbps, identified with a service key, with Q-in-Q tagging on the A-side on a port that already carries 2 virtual cross connects. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Cloud link at 500 Mbps.
    • 
    

    
4. Burstable Digital Internet: Basic Digital Internet with BGP and extra IP blocks, attached across regions

    
The agent's request. Please order Basic Digital Internet at 2,000 Mbps, burstable, for a port in the Americas and an internet service in Europe, with 3 WAN IP blocks and private BGP with 2 IP blocks. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Digital Internet is limited to the port region. Digital Internet is available only within the same region as the port; a port in one region cannot attach to Digital Internet in another.
    • 
      
  • Basic Internet has no BGP. Basic Internet is a single-IP connection and does not include public or private BGP.
    • 
      
  • Basic Internet has a single IP. Basic Internet is a single-IP connection and does not include multiple IP blocks.
    • 
    

    
5. Burstable Digital Internet: The agent resubmits after fixing the errors

    
The agent's request. Please order Full feature Digital Internet at 2,000 Mbps, burstable, for a port in the Americas and an internet service in the Americas, with 3 WAN IP blocks and private BGP with 2 IP blocks. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Digital Internet at 2000 Mbps with 5 IP blocks in total.
    • 
    

    
6. Public BGP with customer-owned blocks: Full-feature Digital Internet with public BGP and customer-owned IP blocks

    
The agent's request. Please order Full feature Digital Internet at 5,000 Mbps, fixed, for a port in the Americas and an internet service in the Americas, with 4 WAN IP blocks and public BGP with customer-owned IP blocks. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Customer-owned IP blocks need approval. Public BGP with customer-owned IP blocks needs approval from the Digital Realty account team, with the IP ranges and proof of ownership; a person should confirm it.
    • 
      
  • Order summary. Digital Internet at 5000 Mbps with 4 IP blocks in total.
    • 
    

    
7. Public BGP with customer-owned blocks: The agent resubmits after fixing the errors

    
The agent's request. Please order Full feature Digital Internet at 5,000 Mbps, fixed, for a port in the Americas and an internet service in the Americas, with 4 WAN IP blocks and public BGP with customer-owned IP blocks, which the account team has approved. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Digital Internet at 5000 Mbps with 4 IP blocks 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 a virtual connection: a layer 2 link to a cloud, a Digital Internet service or a bare metal server link. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of what the public ServiceFabric User Guide says 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 order a layer 2 link to Microsoft Azure at 750 Mbps, identified with the account ID, with untagged traffic on the A-side on a port that already carries 2 virtual cross connects. It is ready to send.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. A link speed of 750 Mbps is not offered; links and connections support 50, 100, 200, 300, 400 and 500 Mbps and 1, 2, 2.5, 5, 10 and 100 Gbps, where the service provider supports them. Azure, Google Cloud, IBM Cloud and Oracle cloud links use a service key rather than an account ID. Microsoft Azure does not support untagged mode on the A-side. The other one is on screen.
    6. 
      
  6. The validator returned four 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 VLAN limits that depend on the cloud and on what is already on the port, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the identified by to service key and the speed to 500 Mbps.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with two findings, all in one answer. Microsoft Azure does not support untagged mode on the A-side. An untagged port allows only one virtual cross connect and this port already has 2, so untagged cannot be selected.
    12. 
      
  12. Two findings cleared; still blocked on Azure does not support untagged on the A-side and untagged port allows one cross connect.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the A-side VLAN to Q-in-Q.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. Both earlier findings are cleared.
    18. 
      
  18. Four 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.
    19.