Predictika · Fixed wireless broadband

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

An AI sales agent puts together a fixed wireless order for a rural broadband operator: the ePMP access points, the subscriber modules, the antennas, the channel width, the regulatory variant and power cord, and the capacity the order says the sectors will serve. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the figures in the public Cambium ePMP 3000 Series and ePMP Force 300 Series datasheets and returns a verdict, every reason and the figures it computed.

Scope: Cambium ePMP 5 GHz sectors: ePMP 3000, ePMP 3000L and MP 3000 MicroPOP access points with Force 300-16, 19, 19R, 25 and CSM subscriber modules. See everything this validator covers

This validator models the published limits and part-number structure of the Cambium ePMP 5 GHz access points and Force 300 subscriber modules, not just the scenarios shown below.

  • Subscribers per sector — up to 120 on the ePMP 3000, 64 on the ePMP 3000L, 32 on the MP 3000 MicroPOP and 12 on a Force 300 CSM licensed as an access point.
  • Channel width — 10, 20, 40 or 80 MHz, with 10 MHz only for the ePMP 3000 together with Force 300-19R subscriber modules.
  • Antennas — the 4x4 MU-MIMO sector antenna for the ePMP 3000, a 2x2 sector or third-party 2x2 antenna for the ePMP 3000L (a 2x2 sector antenna or third-party antenna on a Force 300 CSM access point goes to a person), the integrated omni antenna of the MicroPOP, one antenna per access point, and the optional smart uplink antenna on the ePMP 3000 only.
  • Synchronization and licenses — GPS synchronization (not on the MicroPOP or a CSM access point) and the Force 300 CSM upgrade key, one per access point.
  • Variants, cords and power — which regulatory variants (FCC, IC, EU, India, ROW) are sold with which power cords, the no-PSU part numbers, and the Force 300-25 4-pack.
  • The stated capacity — the capacity the order states must equal what the access points serve.

Any order built from these access points and subscriber modules is in scope — not only the scenarios pictured here. Not covered: prices (the datasheets list none, so this page shows no price build-up), the ePMP 4500, ePMP 1000 and 2000, Force 400 and PMP 450 families, 2.4 GHz and other bands, cnMaestro licenses, and the date of the source datasheets.

The AI sales agentAssembles the 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
Limits that differ by access point modelOnly with workarounds
Each access point has its own subscriber limit, antenna and channel options, so a rules-based CPQ needs a rule set per model.
The model selects its limits inside one model, in any order of choices.
Part numbers that depend on the variantOnly with care
FCC, IC, EU, India and ROW variants come with different power cords and a few part numbers exist only in some variants, so a table of allowed combinations has to be kept in step with the datasheet.
The allowed variant and cord combinations, and the no-PSU rules, are checked on every call.
A radio that changes role with a licenseOnly with workarounds
The Force 300 CSM becomes an access point with a license key, which changes its subscriber limit and removes GPS sync; a quote has to treat one part number as two roles.
The role is a choice in the request and its limits follow from it.
Quantities that must agreeOnly with care
One antenna per access point, one upgrade key per CSM access point and 4-packs that must fit the radios ordered are separate comparisons that all need re-running when a quantity changes.
All of them are evaluated together on every call.
Capacity the order statesOnly with care
The stated capacity is derived from the access points, so a rule has to recompute it and compare.
The stated capacity is a field in the request, compared with the computed figure on every call.
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 third-party antenna is not sold by Cambium; a person should confirm it is a compatible 2x2 antenna.
2The quote has 121 subscriber modules; 1 access point serve at most 120.
3The quote has 65 subscriber modules; 1 access point serve at most 64.
4The quote has 33 subscriber modules; 1 access point serve at most 32.
5The quote has 13 subscriber modules; 1 access point serve at most 12.
6A channel width of 30 MHz is not offered; the access points use 10, 20, 40 or 80 MHz.
710 MHz channels are supported only with the ePMP 3000 access point and Force 300-19R subscriber modules.
8The selected antenna does not fit this access point: the ePMP 3000 takes its 4x4 MU-MIMO sector antenna, the ePMP 3000L a 2x2 sector or third-party 2x2 antenna, the MicroPOP has an integrated omni antenna and a Force 300 CSM access point needs an external antenna.
9The quote has 2 sector antennas for 3 access points; each access point needs one.
10The quote has 0 sector antennas for 3 access points; each access point needs one.
112 sector antennas are quoted, but the selected antenna option does not use a Cambium sector antenna.
12The optional smart uplink beamforming antenna is available only with the ePMP 3000 access point.
13GPS synchronization is not supported on the MP 3000 MicroPOP or on a Force 300 CSM used as an access point.
14The Force 300 CSM is a connectorized radio and the quote has no antenna for it.
15The quote has 0 AP upgrade license keys for 2 Force 300 CSM access points; each needs one.
16The quote has 1 AP upgrade license key for 2 Force 300 CSM access points; each needs one.
173 AP upgrade license keys are quoted, but the Force 300 CSM upgrade key applies only to a Force 300 CSM used as an access point.
18This regulatory variant is not sold with the selected power cord.
19The datasheet lists the 2x2 sector antenna for the ePMP 3000L, not for a Force 300 CSM access point; a person should confirm it can be used with it.
20The radios are quoted without a power supply and the quote names no power source for them.
21The no-PSU part numbers are listed for the ROW variant only.
22The Force 300-25 is not listed without a power supply.

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 three-sector tower: Three ePMP 3000 sectors for 300 subscribers on 10 MHz channels

The agent's request. Please quote 3 ePMP 3000 access points serving 300 Force 300-19 subscriber modules on 10 MHz channels, with the 4x4 MU-MIMO sector antenna (2 antennas). The radios are the FCC variant with the US cord. The order states that the sectors serve 400 subscribers. It is ready to send.

Verdict: Blocked.

  • 10 MHz needs ePMP 3000 and Force 300-19R. 10 MHz channels are supported only with the ePMP 3000 access point and Force 300-19R subscriber modules.
  • Sector antennas do not match access points. The quote has 2 sector antennas for 3 access points; each access point needs one.
  • Stated sector capacity does not match. The quote states a capacity of 400 subscribers; the access points serve at most 360.

2. A three-sector tower: The agent resubmits after fixing the errors

The agent's request. Please quote 3 ePMP 3000 access points serving 300 Force 300-19R subscriber modules on 10 MHz channels, with the 4x4 MU-MIMO sector antenna (3 antennas). The radios are the FCC variant with the US cord. The order states that the sectors serve 360 subscribers. It is ready to send.

Verdict: Allowed.

  • Sector summary. Each access point serves up to 120 subscribers, so 3 access points serve up to 360.

3. A two-sector tower: Two ePMP 3000L sectors for 120 connectorized subscriber modules

The agent's request. Please quote 2 ePMP 3000L access points serving 120 Force 300 CSM subscriber modules on 40 MHz channels, with the 2x2 sector antenna (2 antennas). The radios are the ROW variant with the ANZ cord. Add the smart uplink beamforming antenna. The subscriber modules are the connectorized model. The order states that the sectors serve 150 subscribers. It is ready to send.

Verdict: Blocked.

  • Smart uplink antenna needs the ePMP 3000. The optional smart uplink beamforming antenna is available only with the ePMP 3000 access point.
  • Force 300 CSM needs its own antenna. The Force 300 CSM is a connectorized radio and the quote has no antenna for it.
  • Stated sector capacity does not match. The quote states a capacity of 150 subscribers; the access points serve at most 128.

4. A two-sector tower: The agent resubmits after fixing the errors

The agent's request. Please quote 2 ePMP 3000L access points serving 120 Force 300 CSM subscriber modules on 40 MHz channels, with the 2x2 sector antenna (2 antennas). The radios are the ROW variant with the ANZ cord. The subscriber modules come with their own antennas. The order states that the sectors serve 128 subscribers. It is ready to send.

Verdict: Allowed.

  • Sector summary. Each access point serves up to 64 subscribers, so 2 access points serve up to 128.

5. A hill-top village: Two MicroPOPs for an 80-home village with GPS sync

The agent's request. Please quote 2 MP 3000 MicroPOP access points serving 80 Force 300-16 subscriber modules on 20 MHz channels, with the integrated omni antenna. The radios are the FCC variant with the US cord. GPS synchronization is wanted. The order states that the sectors serve 80 subscribers. It is ready to send.

Verdict: Blocked.

  • This access point cannot GPS-sync. GPS synchronization is not supported on the MP 3000 MicroPOP or on a Force 300 CSM used as an access point.
  • More subscribers than the sectors serve. The quote has 80 subscriber modules; 2 access points serve at most 64.
  • Stated sector capacity does not match. The quote states a capacity of 80 subscribers; the access points serve at most 64.

6. A hill-top village: The agent resubmits after fixing the errors

The agent's request. Please quote 2 ePMP 3000L access points serving 80 Force 300-16 subscriber modules on 20 MHz channels, with a third-party 2x2 antenna. The radios are the FCC variant with the US cord. GPS synchronization is wanted. The order states that the sectors serve 128 subscribers. It is ready to send.

Verdict: Needs approval.

  • Third-party antenna to confirm. A third-party antenna is not sold by Cambium; a person should confirm it is a compatible 2x2 antenna.
  • Sector summary. Each access point serves up to 64 subscribers, so 2 access points serve up to 128.

7. A hill-top village: The agent resubmits after fixing the errors

The agent's request. Please quote 2 ePMP 3000L access points serving 80 Force 300-16 subscriber modules on 20 MHz channels, with the 2x2 sector antenna (2 antennas). The radios are the FCC variant with the US cord. GPS synchronization is wanted. The order states that the sectors serve 128 subscribers. It is ready to send.

Verdict: Allowed.

  • Sector summary. Each access point serves up to 64 subscribers, so 2 access points serve up to 128.

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 puts together a fixed wireless order for a rural broadband operator: the ePMP access points, the subscriber modules, the antennas, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the figures in the public Cambium ePMP 3000 Series and ePMP Force 300 Series datasheets and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote 2 MP 3000 MicroPOP access points serving 80 Force 300-16 subscriber modules on 20 MHz channels, with the integrated omni antenna. The radios are the FCC variant with the US cord. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings, all in one answer. GPS synchronization is not supported on the MP 3000 MicroPOP or on a Force 300 CSM used as an access point. The quote has 80 subscriber modules; 2 access points serve at most 64. The quote states a capacity of 80 subscribers; the access points serve at most 64.
  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. What this shows: for limits that differ by access point model, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the access points to 2 ePMP 3000L, the antenna to A third-party 2x2 antenna and the capacity as stated in the order to 128 subscribers.
  10. It calls the validator again.
  11. Not blocked, but held for a person.
  12. The three blocking findings are cleared; one approval remains for a person: third-party antenna to confirm.
  13. The agent resubmits once more.
  14. The revised request. It changes the antenna to The 2x2 sector antenna and the sector antennas quoted to 2.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The earlier finding is cleared, and the validator's figure matches the quote.
  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.