Predictika · Telecom infrastructure site orders

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

An AI sales agent prepares a site order for telecom infrastructure services: co-location on a tower, cabin or ground space or a build-to-suit programme, the equipment weight, antennas and power per site, cooling and backup power, the tenants already on the site, the backhaul, the term, small-cell nodes and the total power the order states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of what each site type can carry and how those choices fit together, and returns a verdict, every reason and the total it computed.

Scope: One site order: site type, equipment, power, cooling, tenants, backhaul, term, build-to-suit, edge, small-cell nodes and the stated total power. See everything this validator covers

This validator models tower, cabin and ground-space site orders, not just the scenarios shown below.

  • Site limits — the equipment weight, antennas, power and tenants each site type takes, the antenna height against the tower, and the structural study a heavy tower load needs.
  • Power and options — cooling above 3 kW per site, the uninterrupted power supply that needs a cabin or ground site, and the edge data centre unit that needs ground space.
  • Backhaul, term and programmes — radio backhaul on tall towers, fibre runs and the survey a long run needs, the minimum and standard terms, and build-to-suit programmes on new towers.
  • Scale and totals — small-cell and DAS node counts, the last tenant slot on a site, and the total power stated on the order compared with the sites added up.

Any site order of these types that touches these rules is in scope — not only the scenarios pictured here. Not covered: broadcasting, network services and pricing; this model has no prices. The service set (co-location on towers, cabins and ground, power with cooling and backup power, small cells and DAS, build-to-suit towers, backhaul by fibre or radio and edge data centres) follows public Cellnex descriptions; every limit, threshold and term in this validator is modeled from comparable tower-company offers and is not published by Cellnex.

The AI sales agentBuilds the site order 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
Limits that change with the site typeOnly with care
A tower, a cabin and a ground site each take a different weight, number of antennas, power and tenants, so every rule has to test the site type first.
The site type sets every limit in the same pass as the equipment on the order.
Options that only some sites can takeOnly with care
Backup power needs a cabin or ground site, an edge unit needs ground space and radio backhaul needs a tall tower, each with its own exceptions.
The site type, the options and the tower height are checked together on every call.
Thresholds that start a reviewOnly with workarounds
A last tenant slot, a fibre run over 2,000 metres, a short term, a large small-cell count and a big programme each need a person, so each needs its own rule and message.
Each threshold is part of the model and returns its own approval with the reason.
A stated total that must match the computed oneOnly with workarounds
The total power is the sites times the power per site, so a separate rule must recompute it and compare it with the stated figure.
The stated total is a field of the request and is compared with the computed total on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is completed, so a rep often fixes one error and meets the next.
All findings come back together, so the agent can fix them in a single pass.

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 order; approval findings need a person to sign off; everything else is computed.

1The equipment weighs 801 kg; this site type allows 800 kg per tenant.
2Equipment above half the tower load limit needs a completed structural study; none is recorded.
3The order has 7 antennas; this site type allows 6 per tenant.
4The equipment needs 4 kW per site; this site type supplies 3 kW per tenant.
5Equipment above 3 kW per site needs the cooling service; the order does not include it.
6The uninterrupted power supply is housed in a cabin or ground site; it cannot be added to a tower mount.
7This order takes the last available tenant slot on the site; a person should confirm.
8The site already has 4 tenants; this site type takes at most 4.
9The antennas are requested at 41 m; the tower is 40 m high.
10Radio backhaul is modeled for towers of at least 25 m; this site does not qualify.
11A fibre run of 2,001 m needs a route survey; a person should confirm.
12The fibre run is 10,001 m; fibre-to-the-tower is modeled up to 10,000 m.
13A term of 4 years is below the 5-year minimum.
14A term of 7 years is shorter than the standard 10-year term; a person should confirm.
15Build-to-suit is modeled for new towers only.
16Build-to-suit needs a term of at least 10 years; the order has 8.
17A build-to-suit programme of 60 sites needs a person to confirm delivery capacity.
18An edge data centre unit needs ground space; this site is not ground space.
1951 DAS or small-cell nodes is a large deployment; a person should review the design.
20201 DAS or small-cell nodes is above the 200 modeled for one order.
21The order states 25 kW of total power; the sites add up to 20 kW.

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. A tower order: A tower order with too much equipment, too many antennas, backup power and a wrong total

The agent's request. Please prepare a co-location order for 10 sites on towers, with 900 kg of equipment, 8 antennas and 5 kW of power at each site, the antennas at 48 m on a 40 m tower, with an uninterrupted power supply and a completed structural study, fibre backhaul over 3,500 m, 0 tenants already on the site, for a term of 10 years. The order states 30 kW of total power. It is ready to send.

Verdict: Blocked.

  • Equipment weight over site limit. The equipment weighs 900 kg; this site type allows 800 kg per tenant.
  • Too many antennas. The order has 8 antennas; this site type allows 6 per tenant.
  • Power over site limit. The equipment needs 5 kW per site; this site type supplies 3 kW per tenant.
  • Cooling needed above 3 kW. Equipment above 3 kW per site needs the cooling service; the order does not include it.
  • UPS needs a cabin or ground site. The uninterrupted power supply is housed in a cabin or ground site; it cannot be added to a tower mount.
  • Antenna above tower top. The antennas are requested at 48 m; the tower is 40 m high.
  • Stated power does not match. The order states 30 kW of total power; the sites add up to 50 kW.
  • Long fibre run needs survey. A fibre run of 3,500 m needs a route survey; a person should confirm.

2. A tower order: The agent resubmits after fixing the errors

The agent's request. Please prepare a co-location order for 10 sites on cabins, with 900 kg of equipment, 3 antennas and 4 kW of power at each site, with an uninterrupted power supply and a completed structural study, fibre backhaul over 3,500 m, 0 tenants already on the site, for a term of 10 years. The order states 40 kW of total power. It is ready to send.

Verdict: Blocked.

  • Cooling needed above 3 kW. Equipment above 3 kW per site needs the cooling service; the order does not include it.
  • Long fibre run needs survey. A fibre run of 3,500 m needs a route survey; a person should confirm.

3. A tower order: The agent resubmits after fixing the errors

The agent's request. Please prepare a co-location order for 10 sites on cabins, with 900 kg of equipment, 3 antennas and 4 kW of power at each site, with cooling, an uninterrupted power supply and a completed structural study, fibre backhaul over 1,500 m, 0 tenants already on the site, for a term of 10 years. The order states 40 kW of total power. It is ready to send.

Verdict: Allowed.

  • Order summary. 10 site(s) of the chosen type, 4 kW per site, 40 kW in total, term 10 years.

4. A build-to-suit programme: A build-to-suit programme of 60 sites on cabins with a short term and a wrong total

The agent's request. Please prepare a build-to-suit programme for 60 sites on cabins, with 500 kg of equipment, 4 antennas and 3 kW of power at each site, for a term of 8 years. The order states 150 kW of total power. It is ready to send.

Verdict: Blocked.

  • Build-to-suit is a tower. Build-to-suit is modeled for new towers only.
  • Build-to-suit needs a long term. Build-to-suit needs a term of at least 10 years; the order has 8.
  • Stated power does not match. The order states 150 kW of total power; the sites add up to 180 kW.
  • Large build-to-suit programme. A build-to-suit programme of 60 sites needs a person to confirm delivery capacity.

5. A build-to-suit programme: The agent resubmits after fixing the errors

The agent's request. Please prepare a build-to-suit programme for 20 sites on new towers, with 500 kg of equipment, 4 antennas and 3 kW of power at each site, the antennas at 45 m on a 45 m tower, for a term of 15 years. The order states 60 kW of total power. It is ready to send.

Verdict: Allowed.

  • Order summary. 20 site(s) of the chosen type, 3 kW per site, 60 kW in total, term 15 years.

6. A fibre and small-cell order: A co-location order with a very long fibre run, 250 small-cell nodes and a short term

The agent's request. Please prepare a co-location order for 10 sites on towers, with 300 kg of equipment, 3 antennas and 2 kW of power at each site, the antennas at 35 m on a 40 m tower, fibre backhaul over 12,000 m, 250 small-cell nodes, 1 tenant already on the site, for a term of 4 years. The order states 20 kW of total power. It is ready to send.

Verdict: Blocked.

  • Fibre too far. The fibre run is 12,000 m; fibre-to-the-tower is modeled up to 10,000 m.
  • Term too short. A term of 4 years is below the 5-year minimum.
  • Too many DAS nodes. 250 DAS or small-cell nodes is above the 200 modeled for one order.
  • Large DAS order. 250 DAS or small-cell nodes is a large deployment; a person should review the design.

7. A fibre and small-cell order: The agent resubmits after fixing the errors

The agent's request. Please prepare a co-location order for 10 sites on towers, with 300 kg of equipment, 3 antennas and 2 kW of power at each site, the antennas at 35 m on a 40 m tower, fibre backhaul over 1,500 m, 40 small-cell nodes, 1 tenant already on the site, for a term of 10 years. The order states 20 kW of total power. It is ready to send.

Verdict: Allowed.

  • Order summary. 10 site(s) of the chosen type, 2 kW per site, 20 kW in total, term 10 years.

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 site order for telecom infrastructure services: co-location on a tower, cabin or ground space or a build-to-suit programme, the equipment weight, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of what each site type can carry and how those choices fit together, and returns a verdict, every reason and the total it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please prepare a co-location order for 10 sites on towers, with 900 kg of equipment, 8 antennas and 5 kW of power at each site. The order states 30 kW of total power. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with seven findings and one approval, all in one answer. The equipment weighs 900 kg; this site type allows 800 kg per tenant. The order has 8 antennas; this site type allows 6 per tenant. The equipment needs 5 kW per site; this site type supplies 3 kW per tenant. The other four are on screen.
  6. The validator returned seven 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 order are checked against each other.
  7. What this shows: for limits that change with the site type, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the site type to cabin, the antennas to 3, the power per site to 4 kW and the total power stated on the order to 40 kW. It removes the tower height and antenna height.
  10. It calls the validator again.
  11. Still blocked, with one finding and one approval, all in one answer. Equipment above 3 kW per site needs the cooling service; the order does not include it.
  12. Six findings cleared. Still blocking: cooling needed above 3 kW. One approval also remains for a person: long fibre run needs survey.
  13. The agent resubmits once more.
  14. The revised request. It changes the cooling to yes and the fibre distance to 1,500 m.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. Both earlier findings are cleared.
  18. Eight problems caught in one call, fixed in two passes, and a clean order. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.