Predictika · Wind turbine orders

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

An AI sales agent prepares an order for a wind farm built on the ENERCON E-175 EP5 turbine, with the variant, hub height, site wind class, site temperature and wind limits, grid frequency, optional features and the farm capacity it states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the technical data ENERCON publishes and returns a verdict, every reason and the figures it computed.

Scope: ENERCON E-175 EP5 turbine orders (E1 at 6,000 kW and E2 at 7,000 kW): hub height and site wind class, Yield Optimized Mode, site temperature and extreme-wind limits, grid frequency and farm capacity. See everything this validator covers

This validator models orders for the ENERCON E-175 EP5 onshore turbine in its two listed variants, not just the scenarios shown below.

  • Variants and hub heights — the E1 (6,000 kW) is listed at 112, 132 and 162 m and the E2 (7,000 kW) at 112, 132, 162 and 175 m; IEC S is listed for the higher hub heights and IEC IIA for 112 m only (on the E2, 112 m is listed under IEC IIA only).
  • Yield Optimized Mode — listed on the E1 data sheet (6,300 kW); not listed for the E2. A person confirms the grid connection for the higher output.
  • Site limits — design temperature (the E1 to 20 degrees below zero, the E2 to 30 degrees below zero, both to 40 degrees C), 3-second extreme gust up to 59.5 m/s at hub height, and 50 Hz or 60 Hz grids.
  • Farm capacity — the number of turbines multiplied by the rating of the variant and mode, compared with the capacity the order states.

Any E-175 EP5 order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (ENERCON publishes no turbine price list, so this validator produces no price build-up or line-item quote), the E-160 EP5, E-138 EP3 and other models, tower types, noise-optimised operating modes, service agreements and project-specific site assessment. The approval for Yield Optimized Mode is a guideline set by this model, not an ENERCON rule.

The AI sales agentBuilds the turbine 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.

8 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
A hub height that exists only for the other variantOnly with care
A per-variant list of hub heights that must be written and maintained for each product version.		The variant and the hub height are in one request and checked on every call.
A site class that is listed only for one hub heightOnly with workarounds
The link between site class, hub height and variant is a three-way dependency that tends to need layered rules or lookup tables.		Variant, hub height and site class are compared together on every call, in any order.
A site colder or windier than the listed limitsOnly with care
Each limit differs by variant, so each needs its own validation rule and maintenance.		The site figures and the variant limits are compared on every call.
A farm capacity that disagrees with turbines times ratingOnly with workarounds
The rating changes with the variant and mode, so checking a stated total against it takes extra formulas that interact with the rest.		The stated capacity is a field in the request and is compared with the computed one.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a rep 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 hub height of 175 m is not listed for the selected E-175 EP5 variant; the E1 is listed at 112, 132 and 162 m and the E2 at 112, 132, 162 and 175 m.
2A hub height of 140 m is not listed for the selected E-175 EP5 variant; the E1 is listed at 112, 132 and 162 m and the E2 at 112, 132, 162 and 175 m.
3The E2 data sheet lists the 112 m hub height under IEC IIA only, not under IEC S.
4The data sheet lists IEC IIA only for the 112 m hub height; the quote has a site of that class with a 132 m hub.
5Yield Optimized Mode raises each E1 turbine from 6,000 kW to 6,300 kW; a person should confirm the grid connection can take the higher output.
6Yield Optimized Mode (6,300 kW) is listed on the E1 data sheet only; the E2 is listed with noise-optimised operation.
7The site design temperature is 21 degrees C below zero; the selected variant is listed to 20 degrees below zero.
8The site design temperature is 31 degrees C below zero; the selected variant is listed to 30 degrees below zero.
9The site design temperature is 41 degrees C; the data sheet lists operation up to 40 degrees C.
10The site 3-second extreme gust is 60.0 m/s at hub height; the data sheet lists 59.5 m/s.
11The E-175 EP5 is listed for 50 Hz and 60 Hz grids; the quote has 55 Hz.
12The quote states a farm capacity of 80,000 kW, but 12 turbines at 7,000 kW each come to 84,000 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. Cold and windy site: E1 turbines at a very cold, very windy site

    
The agent's request. Please quote 24 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 132 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 28 degrees C below zero to 35 degrees C and a 3-second extreme gust of 62.0 m/s at hub height, with ice detection and de-icing. The order states a farm capacity of 144,000 kW. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Site colder than the turbine range. The site design temperature is 28 degrees C below zero; the selected variant is listed to 20 degrees below zero.
    • 
      
  • Extreme wind above the design value. The site 3-second extreme gust is 62.0 m/s at hub height; the data sheet lists 59.5 m/s.
    • 
    

    
2. Cold and windy site: The agent resubmits after fixing the errors

    
The agent's request. Please quote 24 ENERCON E-175 EP5 E2 (7,000 kW) turbines on a 132 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 28 degrees C below zero to 35 degrees C and a 3-second extreme gust of 62.0 m/s at hub height, with ice detection and de-icing. The order states a farm capacity of 168,000 kW. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Extreme wind above the design value. The site 3-second extreme gust is 62.0 m/s at hub height; the data sheet lists 59.5 m/s.
    • 
    

    
3. Cold and windy site: The agent resubmits after fixing the errors

    
The agent's request. Please quote 24 ENERCON E-175 EP5 E2 (7,000 kW) turbines on a 132 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 28 degrees C below zero to 35 degrees C and a 3-second extreme gust of 58.0 m/s at hub height, with ice detection and de-icing. The order states a farm capacity of 168,000 kW. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 24 turbines at 7,000 kW each, 168,000 kW in all, with a hub height of 132 m.
    • 
    

    
4. Hub height and site class: E1 turbines on a 175 m hub at an IEC IIA site

    
The agent's request. Please quote 30 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 175 m hub for an IEC IIA site, on a 50 Hz grid, with a design temperature range from 15 degrees C below zero to 35 degrees C and a 3-second extreme gust of 50.0 m/s at hub height, with shadow shutdown and bat protection. The order states a farm capacity of 180,000 kW. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Hub height not offered for this variant. A hub height of 175 m is not listed for the selected E-175 EP5 variant; the E1 is listed at 112, 132 and 162 m and the E2 at 112, 132, 162 and 175 m.
    • 
      
  • IEC IIA site class only at 112 m. The data sheet lists IEC IIA only for the 112 m hub height; the quote has a site of that class with a 175 m hub.
    • 
    

    
5. Hub height and site class: The agent resubmits after fixing the errors

    
The agent's request. Please quote 30 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 112 m hub for an IEC IIA site, on a 50 Hz grid, with a design temperature range from 15 degrees C below zero to 35 degrees C and a 3-second extreme gust of 50.0 m/s at hub height, with shadow shutdown and bat protection. The order states a farm capacity of 180,000 kW. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 30 turbines at 6,000 kW each, 180,000 kW in all, with a hub height of 112 m.
    • 
    

    
6. Yield Optimized Mode: E2 turbines with Yield Optimized Mode

    
The agent's request. Please quote 20 ENERCON E-175 EP5 E2 (7,000 kW) turbines on a 162 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 15 degrees C below zero to 35 degrees C and a 3-second extreme gust of 50.0 m/s at hub height, with Yield Optimized Mode and beacon management. The order states a farm capacity of 140,000 kW. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Yield Optimized Mode not listed for the E2. Yield Optimized Mode (6,300 kW) is listed on the E1 data sheet only; the E2 is listed with noise-optimised operation.
    • 
    

    
7. Yield Optimized Mode: The agent resubmits after fixing the errors

    
The agent's request. Please quote 20 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 132 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 15 degrees C below zero to 35 degrees C and a 3-second extreme gust of 50.0 m/s at hub height, with Yield Optimized Mode and beacon management. The order states a farm capacity of 126,000 kW. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Output above nominal in Yield Optimized Mode. Yield Optimized Mode raises each E1 turbine from 6,000 kW to 6,300 kW; a person should confirm the grid connection can take the higher output.
    • 
      
  • Order summary. 20 turbines at 6,300 kW each, 126,000 kW in all, with a hub height of 132 m.
    • 
    

    
8. Yield Optimized Mode: The agent resubmits after fixing the errors

    
The agent's request. Please quote 20 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 132 m hub for an IEC S site, on a 50 Hz grid, with a design temperature range from 15 degrees C below zero to 35 degrees C and a 3-second extreme gust of 50.0 m/s at hub height, with beacon management. The order states a farm capacity of 120,000 kW. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 20 turbines at 6,000 kW each, 120,000 kW in all, with a hub height of 132 m.
    • 
    

  

  

    
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 wind farm built on the ENERCON E-175 EP5 turbine, with the variant. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the technical data ENERCON publishes 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 quote 24 ENERCON E-175 EP5 E1 (6,000 kW) turbines on a 132 m hub for an IEC S site. The order states a farm capacity of 144,000 kW. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. The site design temperature is 28 degrees C below zero; the selected variant is listed to 20 degrees below zero. The site 3-second extreme gust is 62.0 m/s at hub height; the data sheet lists 59.5 m/s.
    6. 
      
  6. The validator returned two 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 a site colder or windier than the listed limits, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the variant to E2 (7,000 kW) and the stated farm capacity as to 168,000 kW.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The site 3-second extreme gust is 62.0 m/s at hub height; the data sheet lists 59.5 m/s.
    12. 
      
  12. One finding cleared; still blocked on extreme wind above the design value.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the site 3-second extreme gust to 58 m/s.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the quote.
    18. 
      
  18. Two 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.