Predictika · Industrial control panel quotes

An AI sales agent's panel quote, checked before it goes out

An AI sales agent prepares a control-panel quote for a fictional customer: panels with their power supply, cooling, enclosure, communication module and I/O modules, plus variable-frequency drives. Before it goes out, the agent sends it to Predictika’s validator, which checks it against design, hazardous-area and commercial rules, compares the net total the agent states with its own, and returns a verdict with every reason.

Scope: industrial control-panel quotes for a fictional manufacturer: power and cooling, I/O and enclosure fit, hazardous areas and certificates, concession authority, lead time, and the net total the agent states. See everything this validator covers

This validator models the rules for a control-panel quote from a fictional manufacturer (Meridian Controls, MC-4000 panels). It handles any quote built from these parts and terms, not just the scenarios shown below.

  • Panel power and cooling — Power-supply redundancy above 30 A, supply capacity at 80 percent loading, cooling against heat load (more above 40 degrees C ambient).
  • Enclosure, I/O and hazardous areas — I/O modules against enclosure slots; purge system, enclosure rating and certificate in Division 1 and Division 2 areas; certificate against ship-to region.
  • Commercial terms — Panels, I/O volume tiers, VFD drives, warranty, commissioning, price concession authority, lead time against need-by, and the net total the agent states.

It does not cover other Meridian products, custom design work, multi-site projects, or real product data. Meridian Controls, its catalog and its prices are invented for demonstration.

The AI sales agentBuilds the quote from the conversation and says it is ready.
Predictika validatorChecks the quote against the product and contract rules and returns every finding it has.

7 scenarios in workflow pairs · click one to switch

What the agent says

Before sending, the agent must call

Predictika validator Recorded run


      
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 or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator catchesTypical rules-based CPQPredictika
Redundant supply, cooling and load sizingOnly with care
Redundancy above 30 A, cooling type and load sizing are chained conditions, usually a selection rule plus a validation rule per part family, and they can run in the wrong order on a single save.
Each part is data in a catalog; the same rules evaluate every combination in one pass.
Hazardous-area combinationsOnly with care
The purge type, enclosure rating and certificate depend on the area class, so each is a conditional rule on a different object.
The area class is evaluated with every other rule, and all three problems are named together.
Volume tiers, warranty and commissioningOnly with care
A tier that counts I/O across panels, a percent-of-hardware warranty with a minimum and a block commissioning price are separate price rules that must be kept in step on every change.
Counts, tiers and charges are derived across the quote on every call and reconcile to the net total.
Concession authority and lead timeOnly with care
An approval band, a hard maximum and a lead time against need-by are separate validation rules, each needing its own approval routing.
Concession and lead time are derived on each call and returned as items for a person.
The net total the agent statesOnly with workarounds
Comparing a stated figure with a computed one means a separate rule per layout, and price rules rarely run on stated figures.
The stated net total is a field in the request and is checked against the computed net total.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is built, so a problem raised late can hide an earlier one.
Every rule is evaluated at the end of input and all findings come back together.

What this validator catches

Click to expand

Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

RuleEffectWhat it checks
1blockA panel above 30 A needs a redundant power supply, and a redundant supply needs active cooling
2blockThe power supply must cover the panel load at the 80 percent continuous-load limit
3blockThe cooling rating must cover the panel heat load, with 25 percent more above 40 degrees C ambient
4blockThe I/O modules on a panel must fit the slots of the enclosure
5blockA hazardous area needs a purge system (Type X for Division 1), a hazardous-rated enclosure and a hazardous-area certificate
6blockThe certificate must cover the ship-to region
7block, approvalA price concession above the 5 percent sales authority needs approval; above 10 percent blocks
8approvalThe longest lead time on the quote must fit the customer’s need-by date
9computedPrice is panels (supply, cooling, enclosure, communication module, purge system and I/O) plus drives; I/O volume tiers of 5 percent (20 or more modules) and 10 percent (40 or more) apply to I/O only
10computedWarranty is 8 percent of the net hardware with a $500 minimum; commissioning is priced by panel count
11blockThe net total the agent states must match the validator net total within $1