Predictika · Heat and cooling meters

An AI sales agent's heat-meter order, checked before it goes out

An AI sales agent prepares an order for MULTICAL 603 heat and cooling meters: calculator type, flow sensor connection, temperature sensor set, power supply, communication modules and cable runs. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published data sheet and returns a verdict, every reason and the figures it computed.

Scope: Kamstrup MULTICAL 603 heat, cooling and heat/cooling meters: calculator type, flow sensor connection, sensor set, supply, modules and cable runs. See everything this validator covers

This validator models orders for the MULTICAL 603 calculator as described in the public Kamstrup data sheet (rev. J1, September 2022, cross-checked against rev. C1 of October 2017), not just the scenarios shown below.

  • Calculator and sensors — the eight calculator types A to H with their Pt100 or Pt500, 2-wire or 4-wire sensor inputs and one or two flow inputs; the temperature sensor set families; cable run limits for temperature sensors and flow sensors.
  • Flow sensor connection — ULTRAFLOW delivered or prepared (one or two), electronic fast or slow pulses, reed contacts and 24 V active pulses, with the CCC code families the data sheet lists for each.
  • Supply and modules — battery and mains supply modules, the two communication module slots, pulse output settings, cold water leakage limits and V1/V2 leakage limits, and the battery lifetime the data sheet gives.
  • Operating conditions — medium temperature, ambient temperature, wall mounting and the wall bracket, the heat/cooling meter marking note, and the standard display codes.

Any order for these products that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (the data sheets list none, so this validator produces no price build-up or line-item quote), the mixed-fluid variant (calculator type M), other MULTICAL models, ULTRAFLOW flow sensor selection, other accessories and tariff, logger and pulse-input settings, and country-specific approvals. Kamstrup states that further configurations exist and asks customers to contact the company; the model covers the standard options in the data sheet.

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

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 sensor set that does not suit the calculator inputOnly with care
Each of the eight calculator types has its own Pt100 or Pt500, 2-wire or 4-wire input, so the sensor set needs a compatibility table that must be kept in step with the data sheet.
The calculator and the sensor set are in one request and compared on every call.
A CCC code that does not suit the flow sensor connectionOnly with care
The allowed code families depend on the flow connection type, so each connection needs its own list of codes.
The connection and the code family are checked together on every call.
Cable runs and the cable extender boxOnly with workarounds
The limit depends on the calculator input, the cable area and whether the extender box is fitted, so it takes a small calculation rather than a simple field limit.
The limit is computed from the order and compared with the run on every call.
A stated battery life that does not match the data sheetOnly with workarounds
The data sheet gives different lifetimes by battery type and by wall or flow-sensor mounting; the figure the agent states is a free field that needs its own lookup and comparison.
The stated life is part of the request and is compared with the computed lifetime 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.

1Two ULTRAFLOW flow sensors need a calculator with two flow inputs (types E, F or H); the chosen calculator type has one.
2The temperature sensor set on the order does not match the sensor input (Pt100 or Pt500, 2-wire or 4-wire) of the chosen calculator type.
3The 24 V active pulse flow input exists only on the 603-G calculator, and the 603-G takes 24 V active pulses only.
4The CCC code family on the order is not one the data sheet lists for the chosen flow sensor connection type.
5A pulse output setting (Out-C or Out-D) needs a communication module with pulse outputs, and neither module slot has one.
6Cold water leakage limits work on the In-A and In-B pulse inputs, and neither module slot has a module with those inputs.
7V1/V2 leakage limits compare two flow sensors, and the chosen calculator has only one flow input.
8The temperature sensor cable run is 12.0 m; the data sheet allows at most 10.0 m for this calculator input and cable.
9The temperature sensor cable run is 5.0 m; the data sheet allows at most 2.5 m for this calculator input and cable.
10The flow sensor cable run is 25.0 m; the data sheet allows at most 10.0 m for this flow input.
11The medium temperature is 140 degrees C; the limit for this flow sensor connection is 130 degrees C.
12The medium temperature is above 90 degrees C or below the ambient temperature, and the data sheet recommends wall-mounting the calculator; the quote has it mounted on the flow sensor.
13The calculator is rated for indoor installation at 5 to 55 degrees C; the order has 60 degrees C.
14The calculator is to be wall-mounted and the quote has no wall bracket (article 3,026-207.A).
15The quote states 16 years of battery life; the data sheet gives 14 years for the chosen supply and mounting (0 means no battery).
16The quote states 10 years of battery life; the data sheet gives 0 years for the chosen supply and mounting (0 means no battery).
17In some countries a heat/cooling meter (types 3 and 6) may carry only the MID marking by national law; a person should confirm the destination country.
18The display code is not the standard one the data sheet lists for this meter type; the data sheet lists standard configurations only, so confirm with Kamstrup.

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. Flow sensors: Two prepared ULTRAFLOW flow sensors on a 603-D calculator

The agent's request. Please quote the MULTICAL 603-D calculator with two identical ULTRAFLOW prepared, 4-wire pocket sensors with connection head, the CCC code family 8xx and a D-cell battery. The temperature sensor cable run is 2 m. It is ready to send.

Verdict: Blocked.

  • Two flow sensors need a two-input calculator. Two ULTRAFLOW flow sensors need a calculator with two flow inputs (types E, F or H); the chosen calculator type has one.

2. Flow sensors: The agent resubmits after fixing the errors

The agent's request. Please quote the MULTICAL 603-H calculator with two identical ULTRAFLOW prepared, 4-wire pocket sensors with connection head, the CCC code family 8xx and a D-cell battery. The temperature sensor cable run is 2 m. It is ready to send.

Verdict: Allowed.

  • Meter summary. Calculator with 2 flow input(s); temperature sensor cable limit 100.0 m; flow sensor cable limit 10.0 m; data sheet battery life 14 years (0 means no battery).

3. Temperature sensors: A 603-C calculator with 4-wire pocket sensors and a 14 m sensor run

The agent's request. Please quote the MULTICAL 603-C calculator with one ULTRAFLOW delivered, 4-wire pocket sensors with connection head, the CCC code family 4xx and a D-cell battery. The temperature sensor cable run is 14 m. It is ready to send.

Verdict: Blocked.

  • Temperature sensor set does not suit the calculator. The temperature sensor set on the order does not match the sensor input (Pt100 or Pt500, 2-wire or 4-wire) of the chosen calculator type.
  • Temperature sensor cable too long. The temperature sensor cable run is 14.0 m; the data sheet allows at most 10.0 m for this calculator input and cable.

4. Temperature sensors: The agent resubmits after fixing the errors

The agent's request. Please quote the MULTICAL 603-D calculator with one ULTRAFLOW delivered, 4-wire pocket sensors with connection head, the CCC code family 4xx and a D-cell battery. The temperature sensor cable run is 14 m. It is ready to send.

Verdict: Allowed.

  • Meter summary. Calculator with 1 flow input(s); temperature sensor cable limit 100.0 m; flow sensor cable limit 10.0 m; data sheet battery life 14 years (0 means no battery).

5. Pulse flow sensor: A reed-contact flow sensor with an Auto Detect CCC code and a 14 m flow cable

The agent's request. Please quote the MULTICAL 603-C calculator with a slow pulse-with-bounce (reed contact) flow sensor, no temperature sensors, the CCC code family 8xx and a D-cell battery. The flow sensor cable run is 14 m. It is ready to send.

Verdict: Blocked.

  • CCC code does not suit the flow sensor. The CCC code family on the order is not one the data sheet lists for the chosen flow sensor connection type.
  • Flow sensor cable too long. The flow sensor cable run is 14.0 m; the data sheet allows at most 10.0 m for this flow input.

6. Pulse flow sensor: The agent resubmits after fixing the errors

The agent's request. Please quote the MULTICAL 603-C calculator with a slow pulse-with-bounce (reed contact) flow sensor, no temperature sensors, the CCC code family 0xx and a D-cell battery. The flow sensor cable run is 8 m. It is ready to send.

Verdict: Allowed.

  • Meter summary. Calculator with 1 flow input(s); temperature sensor cable limit 10.0 m; flow sensor cable limit 10.0 m; data sheet battery life 14 years (0 means no battery).

7. Output module and mounting: A wall-mounted 603-C with a pulse output setting and a pulse-input module

The agent's request. Please quote the MULTICAL 603-C calculator with one ULTRAFLOW delivered, no temperature sensors, the CCC code family 4xx and a D-cell battery. Communication modules: wired M-Bus with pulse inputs. A pulse output setting (code 80) is configured. The calculator is wall-mounted. The quote states 16 years of battery life. It is ready to send.

Verdict: Blocked.

  • Pulse output needs an output module. A pulse output setting (Out-C or Out-D) needs a communication module with pulse outputs, and neither module slot has one.
  • Wall mounting needs a wall bracket. The calculator is to be wall-mounted and the quote has no wall bracket (article 3,026-207.A).

8. Output module and mounting: The agent resubmits after fixing the errors

The agent's request. Please quote the MULTICAL 603-C calculator with one ULTRAFLOW delivered, no temperature sensors, the CCC code family 4xx and a D-cell battery. Communication modules: wired M-Bus with pulse outputs. A pulse output setting (code 80) is configured. The calculator is wall-mounted with the wall bracket (article 3026-207.A) on the quote. The quote states 16 years of battery life. It is ready to send.

Verdict: Allowed.

  • Meter summary. Calculator with 1 flow input(s); temperature sensor cable limit 10.0 m; flow sensor cable limit 10.0 m; data sheet battery life 16 years (0 means no battery).

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 MULTICAL 603 heat and cooling meters: calculator type, flow sensor connection, temperature sensor set, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published data sheet and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote the MULTICAL 603-C calculator with one ULTRAFLOW delivered, no temperature sensors, the CCC code family 4xx and a D-cell battery. Communication modules: wired M-Bus with pulse inputs. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. A pulse output setting (Out-C or Out-D) needs a communication module with pulse outputs, and neither module slot has one. The calculator is to be wall-mounted and the quote has no wall bracket (article 3,026-207.A).
  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. What this shows: for a stated battery life that does not match the data sheet, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the communication modules to wired M-Bus with pulse outputs and the mounting to wall, bracket on the quote.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. Both earlier findings are cleared.
  13. Two 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.