Predictika · Machine safety controllers

An AI sales agent's PNOZmulti 2 system, checked before it goes out

An AI sales agent assembles a PNOZmulti 2 configurable safe small controller system for a machine builder: a base unit, expansion modules to its right and left, standard modules, fieldbus and communication modules, and connected PITreader and Visu Panel devices, with the total number of expansion modules it states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the system-expansion limits in the public Pilz operating manual and returns a verdict, every reason and the figures it computed.

Scope: PNOZmulti 2 systems built from the PNOZ m B0, B0.1, B1, B1 Burner and C0 base units: expansion modules to the right and left, standard modules, fieldbus, communication and EtherCAT FSoE modules, and connected devices. See everything this validator covers

This validator models the system expansion of one PNOZmulti 2 system at a time, based on the limits in the public Pilz operating manual "System expansion" (1002217-EN-20), not just the scenarios shown below.

  • Right-hand modules — the number of expansion modules to the right of each base unit (6 on the B0, 1 on the B0.1, 12 on the B1 and B1 Burner, none on the C0), which modules each base unit lists (analogue input, motion monitoring, 2DOR output and standard modules), and the limit of 8 in total for the 4DI4DOR, 4DI4DORD and 2MM modules on a B1.
  • Left-hand modules — up to 4 link or SafetyNET modules to the left of a base unit (3 on a B1 that carries an EtherCAT FSoE module), SafetyNET only where the manual lists it, and at most one fieldbus module and one communication module where the manual lists them. A B1 takes a fieldbus module or an EtherCAT FSoE module, not both.
  • Standard modules and firmware — the PNOZ m ES 16DI and ES 14DO standard modules are listed only for the B1 and B1 Burner, up to 6 of each, and units with firmware up to version 1.8 go to a person because the manual gives different limits for them.
  • Connected devices and the stated count — up to 4 PITreader systems and 4 Visu Panels on a B1 or B1 Burner, and the total number of expansion modules the quote states, which must equal the configuration.

Any PNOZmulti 2 system that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (none are modeled), the PNOZmulti Configurator's placement of modules, reaction times and safety calculations, other PNOZmulti families, and module positions beyond the counts above.

The AI sales agentBuilds the system 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
Right-hand limits that differ by base unit (6, 1, 12 and none)Only with care
The allowed count and the modules each base unit lists differ per base unit, so a rules-based CPQ needs a rule or table row per base unit and per module type.		The base unit and every module count arrive in one request and are compared with the limits for that base unit on every call.
A shared limit of 8 across three module types on a B1Only with workarounds
The limit applies to the sum of the 4DI4DOR, 4DI4DORD and 2MM modules, not to each type, and a second grouping (2DOR with 2MM) is listed in the same table.		Both sums are computed on every call and compared with the limit.
Left-hand limits that change when an EtherCAT FSoE module is presentOnly with care
The left-hand limit falls from 4 to 3 on a B1 only when an FSoE module is chosen, and the fieldbus and FSoE choices exclude each other.		The limit is chosen from the current choices and checked together with the fieldbus and FSoE rules.
The module count the quote statesOnly with care
The stated total has to be recomputed from every module field and compared.		The stated count is a field in the request, compared with the computed one 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.

    
17 expansion modules planned to the right of the base unit; the selected base unit allows 6.
22 expansion modules planned to the right of the base unit; the selected base unit allows 1.
3The manual does not list the PNOZ m EF 2DOR output module for the selected base unit.
4The manual does not list the PNOZ m EF 4AI analogue input module for the selected base unit.
5The manual does not list motion monitoring modules (PNOZ m EF 1MM, 1MM2DO, 2MM) for the selected base unit.
613 expansion modules planned to the right of the base unit; the selected base unit allows 12.
79 modules of type PNOZ m EF 4DI4DOR, 4DI4DORD and 2MM are planned; the manual limits them to 8 in total.
89 modules of type PNOZ m EF 2DOR and 2MM are planned; the table lists 8 in total with the 2MM.
9The manual lists at most 6 PNOZ m ES 16DI and at most 6 PNOZ m ES 14DO modules; the planned standard modules exceed that.
10The manual lists the standard modules PNOZ m ES 16DI and PNOZ m ES 14DO only for the PNOZ m B1 and B1 Burner.
11The base unit has firmware up to version 1.8; the manual gives different standard-module limits for such units, so a person should confirm the planned standard modules.
121 expansion module planned to the right of the base unit; the selected base unit allows 0.
131 fieldbus module is planned; the selected base unit allows 0.
145 link or SafetyNET modules are planned to the left of the base unit; the selected base unit allows 4 in this arrangement.
154 link or SafetyNET modules are planned to the left of the base unit; the selected base unit allows 3 in this arrangement.
16A fieldbus module and a PNOZ m EF EtherCAT FSoE module are both planned; the manual lists the one or the other to the left of a PNOZ m B1.
171 PNOZ m EF EtherCAT FSoE module is planned; the selected base unit allows 0.
181 PNOZ m EF SafetyNET module is planned; the selected base unit allows 0.
191 communication module (PNOZ m ES ETH or RS232) are planned; the selected base unit allows 0.
202 fieldbus modules are planned; the selected base unit allows 1.

  

  

    
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. Right-hand modules and base unit: Nine right-hand modules on a PNOZ m B0 with SafetyNET, a fieldbus and a communication module

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B0 base unit, with 4 PNOZ m EF 16DI modules, 3 PNOZ m EF 8DI4DO modules and 2 PNOZ m EF 4DI4DOR modules to the right, and 1 PNOZ m EF Multi Link module, 1 PNOZ m EF SafetyNET module, 1 fieldbus module and 1 communication module to the left. The quote states 13 expansion modules in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many right-hand modules. 9 expansion modules planned to the right of the base unit; the selected base unit allows 6.
    • 
    

    
2. Right-hand modules and base unit: The agent resubmits after fixing the errors

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B1 base unit, with 4 PNOZ m EF 16DI modules, 3 PNOZ m EF 8DI4DO modules and 2 PNOZ m EF 4DI4DOR modules to the right, and 1 PNOZ m EF Multi Link module, 1 PNOZ m EF SafetyNET module and 1 fieldbus module to the left. The quote states 12 expansion modules in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • System summary. Base unit allows 12 right-hand modules; 9 planned; 2 link or SafetyNET modules planned to the left; 12 expansion modules in total.
    • 
    

    
3. Connected devices and base unit: A PNOZ m B0.1 with two right-hand modules and a PITreader

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B0.1 base unit, with 1 PNOZ m EF 16DI module and 1 PNOZ m EF 8DI4DO module to the right, and 1 fieldbus module and 1 communication module to the left, with 1 PITreader system connected. The quote states 4 expansion modules in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many right-hand modules. 2 expansion modules planned to the right of the base unit; the selected base unit allows 1.
    • 
      
  • Too many PITreaders. 1 PITreader system is planned; the selected base unit allows 0.
    • 
    

    
4. Connected devices and base unit: The agent resubmits after fixing the errors

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B1 Burner base unit, with 1 PNOZ m EF 16DI module and 1 PNOZ m EF 8DI4DO module to the right, and 1 fieldbus module to the left, with 1 PITreader system connected. The quote states 3 expansion modules in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • System summary. Base unit allows 12 right-hand modules; 2 planned; 0 link or SafetyNET modules planned to the left; 3 expansion modules in total.
    • 
    

    
5. Relay outputs, left-hand modules and firmware: A PNOZ m B1 with 13 right-hand modules, four left-hand modules and standard modules on older firmware

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B1 base unit, with 3 PNOZ m EF 16DI modules, 5 PNOZ m EF 4DI4DOR modules, 2 PNOZ m EF 4DI4DORD modules, 3 PNOZ m EF 2MM modules, 2 PNOZ m ES 16DI modules and 1 PNOZ m ES 14DO module to the right, and 2 PNOZ m EF Multi Link modules, 2 PNOZ m EF PDP Link modules and 1 PNOZ m EF EtherCAT FSoE module to the left, with 2 PITreader systems connected. The base unit firmware is version 1.8 or older. The quote states 21 expansion modules in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many right-hand modules. 13 expansion modules planned to the right of the base unit; the selected base unit allows 12.
    • 
      
  • Too many relay-output and 2-axis modules on a B1. 10 modules of type PNOZ m EF 4DI4DOR, 4DI4DORD and 2MM are planned; the manual limits them to 8 in total.
    • 
      
  • Too many left-hand expansion modules. 4 link or SafetyNET modules are planned to the left of the base unit; the selected base unit allows 3 in this arrangement.
    • 
      
  • Older firmware with standard modules. The base unit has firmware up to version 1.8; the manual gives different standard-module limits for such units, so a person should confirm the planned standard modules.
    • 
    

    
6. Relay outputs, left-hand modules and firmware: The agent resubmits after fixing the errors

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B1 base unit, with 3 PNOZ m EF 16DI modules, 3 PNOZ m EF 4DI4DOR modules, 2 PNOZ m EF 4DI4DORD modules, 3 PNOZ m EF 2MM modules, 2 PNOZ m ES 16DI modules and 1 PNOZ m ES 14DO module to the right, and 1 PNOZ m EF Multi Link module, 1 PNOZ m EF PDP Link module and 1 PNOZ m EF EtherCAT FSoE module to the left, with 2 PITreader systems connected. The base unit firmware is version 1.8 or older. The quote states 17 expansion modules in total. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Older firmware with standard modules. The base unit has firmware up to version 1.8; the manual gives different standard-module limits for such units, so a person should confirm the planned standard modules.
    • 
      
  • System summary. Base unit allows 12 right-hand modules; 11 planned; 2 link or SafetyNET modules planned to the left; 17 expansion modules in total.
    • 
    

    
7. Relay outputs, left-hand modules and firmware: The agent resubmits after fixing the errors

    
The agent's request. Please quote a PNOZmulti 2 system on a PNOZ m B1 base unit, with 3 PNOZ m EF 16DI modules, 3 PNOZ m EF 4DI4DOR modules, 2 PNOZ m EF 4DI4DORD modules, 3 PNOZ m EF 2MM modules, 2 PNOZ m ES 16DI modules and 1 PNOZ m ES 14DO module to the right, and 1 PNOZ m EF Multi Link module, 1 PNOZ m EF PDP Link module and 1 PNOZ m EF EtherCAT FSoE module to the left, with 2 PITreader systems connected. The base unit firmware is newer than version 1.8. The quote states 17 expansion modules in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • System summary. Base unit allows 12 right-hand modules; 11 planned; 2 link or SafetyNET modules planned to the left; 17 expansion modules in total.
    • 
    

  

  

    
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 assembles a PNOZmulti 2 configurable safe small controller system for a machine builder: a base unit, expansion modules to its right and left, standard modules, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the system-expansion limits in the public Pilz operating manual 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 a PNOZmulti 2 system on a PNOZ m B1 base unit, with 3 PNOZ m EF 16DI modules. The base unit firmware is version 1.8 or older. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings and one approval, all in one answer. 13 expansion modules planned to the right of the base unit; the selected base unit allows 12. 10 modules of type PNOZ m EF 4DI4DOR, 4DI4DORD and 2MM are planned; the manual limits them to 8 in total. 4 link or SafetyNET modules are planned to the left of the base unit; the selected base unit allows 3 in this arrangement.
    6. 
      
  6. The validator returned three 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 quote are checked against each other.
    7. 
      
  7. What this shows: for left-hand limits that change when an EtherCAT FSoE module is present, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the PNOZ m EF 4DI4DOR to 3, the PNOZ m EF Multi Link to 1, the PNOZ m EF PDP Link to 1 and the stated expansion modules as to 17.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The three blocking findings are cleared; one approval remains for a person: older firmware with standard modules.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the base unit firmware up to version 1.8 to no.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared.
    18. 
      
  18. Four 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.
    19.