Predictika · SICK microScan3 safety laser scanner orders

An AI sales agent's safety scanner order, checked before it goes out

An AI sales agent prepares an order for a SICK microScan3 safety laser scanner from public SICK data sheets, with a variant, the protective field range, fields, monitoring cases and outputs the cell needs, and the operating conditions. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published data sheets and returns a verdict, every reason and the figures it computed.

Scope: Six SICK microScan3 variants (Core I/O, Core I/O AIDA, Pro I/O and network-only Pro): range, fields, cases, outputs, resolution, environment and system plug. See everything this validator covers

This validator models orders for six microScan3 type codes whose data sheets it was built from (MICS3-AAAZ40AZ1P01, AAAZ40BZ1P01, AAAZ55AZ1, CBAZ55ZA1, CCAZ40AA1 and CCAZ55AA1), not just the scenarios shown below.

  • Performance — the protective field range (4 or 5.5 m), the number of fields and monitoring cases, the local OSSD pairs and the safety outputs via the network each variant lists, and the response time; a stated range that differs from the variant is rejected.
  • Configuration and environment — the resolutions the data sheets list (30, 40, 50, 70, 150 and 200 mm), indoor use only, the operating temperature range of -10 to 50 degrees C, the 24 V DC supply with its 16.8 to 30 V DC range, and SIL 2 as the highest integrity level listed.
  • Functions and system plug — a restart interlock or external device monitoring (EDM) the variant does not list is rejected; a sensor without a system plug needs one on the order, and a plug the customer already owns needs a person to confirm it fits.

Any order for these six variants that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (SICK publishes no list prices, so this validator produces no price build-up or line-item quote), other microScan3 type codes and other SICK scanner families, accessories such as mounting kits, the safety software and its configuration, and service contracts.

The AI sales agentBuilds the scanner 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
A protective field range, fields or outputs the variant cannot provideOnly with care
Each type code has its own figures, so it takes a table or one rule per variant, kept up to date by hand.		The variant and the needs are in one request and compared with the data sheet figures on every call.
A sensor that ships without a system plug and an order with noneOnly with workarounds
Whether a plug is included depends on the type code, and an existing plug is a judgment call; a rules engine needs an attribute per variant and a rule for each case.		The plug is part of the request and checked against the variant on every call, with an approval for a plug the customer already owns.
A restart interlock or EDM the variant does not listOnly with care
Option limits are separate rules that need updating when a data sheet changes.		The needs and the variant are in the same request and compared on every call.
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.

    
1The selected variant is a sensor without a system plug and the order has no system plug, new or existing.
2The order relies on a system plug the customer already owns; a person should confirm it fits the selected sensor.
3The application needs a protective field range of 4.5 m; the selected variant has 4.0 m.
4Fields needed: 9; the selected variant stores 8.
5Monitoring cases needed: 3; the selected variant has 2.
6OSSD pairs needed: 2; the selected variant has 1.
7OSSD pairs needed: 1; the selected variant has 0.
8Safety outputs via the network needed: 9; the selected variant has 8.
9Safety outputs via the network needed: 1; the selected variant has 0.
10The application allows a response time of 80 ms; the selected variant has 95 ms.
11A resolution of 60 mm is not configurable; the data sheets list 30, 40, 50, 70, 150 and 200 mm.
12A resolution of 14 mm is not configurable; the data sheets list 30, 40, 50, 70, 150 and 200 mm.
13The data sheets list the application as indoor; the order is for outdoor use.
14The ambient temperature runs from -20 to 40 degrees C; the operating range is -10 to 50 degrees C.
15The ambient temperature runs from 0 to 55 degrees C; the operating range is -10 to 50 degrees C.
16The supply voltage is 15.0 V DC; the data sheets give 24 V DC with a range of 16.8 to 30 V DC.
17The application needs SIL 3; the data sheets list SIL 2 (IEC 61,508), PL d, category 3.
18The application needs a restart interlock; the data sheet of the selected variant does not list it.
19The application needs external device monitoring (EDM); the data sheet of the selected variant does not list it.
20The quote states a protective field range of 4.0 m; the selected variant has 5.5 m.
21The application needs a protective field range of 5.0 m; the selected variant has 4.0 m.
22Monitoring cases needed: 4; the selected variant has 2.
23The quote states a protective field range of 5.5 m; the selected variant has 4.0 m.

  

  

    
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. Guarding a larger cell: A Core I/O 4 m scanner for a cell that needs 5 m, 4 monitoring cases and 2 OSSD pairs

    
The agent's request. Please quote one SICK microScan3 Core I/O with a 4 m range (MICS3-AAAZ40AZ1P01) for an application that needs a protective field range of 5 m, 6 fields, 4 monitoring cases and 2 OSSD pairs, with a resolution of 50 mm. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Protective field range too short. The application needs a protective field range of 5.0 m; the selected variant has 4.0 m.
    • 
      
  • Too few monitoring cases. Monitoring cases needed: 4; the selected variant has 2.
    • 
      
  • Too few OSSD pairs. OSSD pairs needed: 2; the selected variant has 1.
    • 
      
  • Stated range differs from the variant. The quote states a protective field range of 5.5 m; the selected variant has 4.0 m.
    • 
    

    
2. Guarding a larger cell: The agent resubmits after fixing the errors

    
The agent's request. Please quote one SICK microScan3 Pro I/O with a 5.5 m range (MICS3-CCAZ55AA1) for an application that needs a protective field range of 5 m, 6 fields, 4 monitoring cases and 2 OSSD pairs, with a resolution of 50 mm, with a system plug on the order. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Variant summary. Selected variant, protective field range 5.5 m, fields 128, monitoring cases 128, OSSD pairs 4, response time 70 ms.
    • 
    

    
3. Network-only Pro: A network-only Pro with no system plug, one OSSD pair and external device monitoring

    
The agent's request. Please quote one SICK microScan3 Pro with a 5.5 m range, network outputs only (MICS3-CBAZ55ZA1) for an application that needs a protective field range of 5 m, 20 fields, 10 monitoring cases, 1 OSSD pair and 4 safety outputs via the network, with a resolution of 50 mm, a restart interlock and external device monitoring. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too few OSSD pairs. OSSD pairs needed: 1; the selected variant has 0.
    • 
      
  • No external device monitoring on this variant. The application needs external device monitoring (EDM); the data sheet of the selected variant does not list it.
    • 
      
  • System plug missing. The selected variant is a sensor without a system plug and the order has no system plug, new or existing.
    • 
    

    
4. Network-only Pro: The agent resubmits after fixing the errors

    
The agent's request. Please quote one SICK microScan3 Pro I/O with a 5.5 m range (MICS3-CCAZ55AA1) for an application that needs a protective field range of 5 m, 20 fields, 10 monitoring cases, 1 OSSD pair and 4 safety outputs via the network, with a resolution of 50 mm, a restart interlock and external device monitoring, using a system plug the customer already owns. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Existing system plug to confirm. The order relies on a system plug the customer already owns; a person should confirm it fits the selected sensor.
    • 
      
  • Variant summary. Selected variant, protective field range 5.5 m, fields 128, monitoring cases 128, OSSD pairs 4, response time 70 ms.
    • 
    

    
5. Network-only Pro: The agent resubmits after fixing the errors

    
The agent's request. Please quote one SICK microScan3 Pro I/O with a 5.5 m range (MICS3-CCAZ55AA1) for an application that needs a protective field range of 5 m, 20 fields, 10 monitoring cases, 1 OSSD pair and 4 safety outputs via the network, with a resolution of 50 mm, a restart interlock and external device monitoring, with a system plug on the order. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Variant summary. Selected variant, protective field range 5.5 m, fields 128, monitoring cases 128, OSSD pairs 4, response time 70 ms.
    • 
    

    
6. Outdoor guarding: A Core I/O 5.5 m scanner for outdoor use at a 60 mm resolution

    
The agent's request. Please quote one SICK microScan3 Core I/O with a 5.5 m range (MICS3-AAAZ55AZ1) for an application that needs a protective field range of 5 m, 6 fields, 2 monitoring cases and 1 OSSD pair, with a resolution of 60 mm, used outdoors, with a system plug on the order. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Resolution not offered. A resolution of 60 mm is not configurable; the data sheets list 30, 40, 50, 70, 150 and 200 mm.
    • 
      
  • Indoor application only. The data sheets list the application as indoor; the order is for outdoor use.
    • 
    

    
7. Outdoor guarding: The agent resubmits after fixing the errors

    
The agent's request. Please quote one SICK microScan3 Core I/O with a 5.5 m range (MICS3-AAAZ55AZ1) for an application that needs a protective field range of 5 m, 6 fields, 2 monitoring cases and 1 OSSD pair, with a resolution of 70 mm, with a system plug on the order. The quote states a protective field range of 5.5 m. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Variant summary. Selected variant, protective field range 5.5 m, fields 8, monitoring cases 2, OSSD pairs 1, response time 70 ms.
    • 
    

  

  

    
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 SICK microScan3 safety laser scanner from public SICK data sheets, with a variant. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published data sheets 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 one SICK microScan3 Core I/O. The quote states a protective field range of 5.5 m. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. The application needs a protective field range of 5.0 m; the selected variant has 4.0 m. Monitoring cases needed: 4; the selected variant has 2. OSSD pairs needed: 2; the selected variant has 1. The other one is on screen.
    6. 
      
  6. The validator returned four 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 protective field range, fields or outputs the variant cannot provide, 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 Pro I/O, 5.5 m. It sets the system plug to on the order.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All four earlier findings are cleared.
    13. 
      
  13. Four problems caught in one call, fixed in one pass, 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.
    14.