Predictika · Legrand data center rack PDUs

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

An AI sales agent drafts a quote for rack PDUs in a data center: Raritan PX4 and Server Technology PRO4X units, in EU (IEC 60309) and North American (NEMA) versions, with sensors, quoted in euros. Before the quote goes out, the agent sends it to Predictika, which checks it against a declarative model, compares the total the agent states with the one it computes, and returns every finding together with the line-item quote.

Scope: Legrand data center rack PDUs: Raritan PX4 and Server Technology PRO4X, EU and North American versions. See everything this validator covers

This validator is built for one thing: configuring and quoting Legrand data center rack PDUs (Raritan PX4 and Server Technology PRO4X). It does not know Legrand's other electrical or data-infrastructure product lines; only the rack PDU configuration and commercial rules below.

  • Regional and electrical fit — eight PDU models: EU IEC 60309 and NA NEMA (L6-30, L21-30) inlet-metered, outlet-metered and outlet-switched units, matched to the site region and the branch circuit plug, phase and amperage.
  • Load and outlet sizing — A+B redundancy needing PDUs in pairs, per-PDU load against the 80 percent derated rating, sign-off when headroom is under 10 percent, and C13 and C19 outlet counts against the connected devices.
  • Feature requirements — remote reboot needing outlet switching, per-outlet chargeback needing outlet-level metering, and PDU length against rack height.
  • Commercial terms — sensors, custom color with a 50-PDU minimum, supply-planning approval for 500 or more PDUs, volume tiers at 20, 50 and 100 PDUs, discount authority (with deal registration), lead time against the customer's need date, and the total the agent states.

Within that scope the validator handles any combination of these PDU models, circuits, redundancy designs and feature requirements, not just the seven scenarios shown on this page. It is an illustrative model built from public Legrand product information; prices, limits and policy values are fictional, and it does not use Legrand's internal rules.

The AI sales agentBuilds the Legrand PDU quote 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 4 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

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  

    
What this means
Run the validator to see the outcome
The explanation appears here once the validator returns.

    

  

  

    
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 PDU whose plug, phase and amperage match the branch circuitOnly with care
A compatibility table by region and circuit, which has to be extended for every new PDU model and is easy to leave incomplete.		Region and circuit are checked from the PDU's own attributes on every call.
Load per PDU under A+B redundancyOnly with workarounds
With A+B the load on one feed is the rack load shared by half the PDUs, and the derated rating differs per model. It takes helper formula fields on the quote line for each redundancy design.		The share, the derated rating and the outlet counts are computed from the order and checked together.
Remote reboot or chargeback needing the right PDUOnly with care
The requirement belongs to attributes of the chosen model (switched, outlet-metered), not to an option that can be added, so it only works if every model is tagged and every rule is kept in step.		Switching and metering are attributes of each PDU model and are checked whenever the feature is requested.
A stated total that does not match the computed priceOnly with care
A validation rule can compare a stated total with a calculated field, but only if the stated total is a field on the quote, which it rarely is.		The stated total is compared with the computed one at every step of processing the quote.

  

  

    
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.

    
1PDU model is not for the site region.
2PDU plug, phase or amperage does not match the branch circuit.
3A+B redundancy with an odd number of PDUs per rack.
4Load per PDU above the derated rating of the PDU.
5Not enough C13 or C19 outlets on the PDU.
6PDU too long for the rack height.
7Remote reboot requested on a PDU that is not outlet-switched.
8Per-outlet chargeback requested on a PDU without outlet metering.
9Custom color on fewer than 50 PDUs.
10Lead time longer than the customer can wait.
11Extra discount above the maximum for the deal.
12The agent's stated total does not match the computed total.
13Load above 90 percent of the PDU rating: capacity-planning sign-off needed.
14500 or more PDUs: supply-planning commitment needed.
15Extra discount above what a rep may give alone: needs approval.

  

  








'