Predictika · Sealed linear encoders for machine tools

An AI sales agent's linear encoder quote, checked before it goes out

An AI sales agent prepares a quote for a HEIDENHAIN sealed linear encoder: the model, the control interface, the measuring length, the cable, the traversing speed and acceleration, and any functional safety requirement. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the selection data HEIDENHAIN publishes in its linear encoder brochure and returns a verdict, every reason and the figures it computed.

Scope: HEIDENHAIN sealed linear encoders LC 4x5, LC 1x5, LC 2x1, LF 485 and 185, LS 4x7 and 1x7, and LB 382: published measuring lengths, interfaces, cable length, speed, acceleration, vibration, shock, temperature and functional safety data. See everything this validator covers

This validator models a quote for one linear encoder at a time, based on the public HEIDENHAIN brochure Linear Encoders for Numerically Controlled Machine Tools (ID 571470-2C, June 2019), not just the scenarios shown below.

  • Selection — the measuring length must be one the selected model offers (each model family has its own list of lengths), the control interface must match the encoder, absolute encoders cannot have distance-coded reference marks, and the slimline encoders above a published length need a mounting spar or clamping elements.
  • Operating limits — cable length, traversing speed, acceleration, vibration, shock, ambient temperature, and IP64 protection, which the brochure publishes only with sealing air. TTL encoders get a traversing speed from their interpolation and scanning frequency, and only TTL encoders can be given those two values.
  • Functional safety — only the LC 1x5 and LC 4x5 encoders with EnDat or DRIVE-CLiQ carry the published SIL 2 / PL d data; the required PFH and the installation altitude are compared with the published values, and the mounting spar fault exclusion has an acceleration limit.
  • Needs approval — combinations the brochure does not cover: vibration where no rating is published for the mounting, clamping elements on a safety application, and a high-dynamics application on a slimline encoder without a spar.

Any quote for these encoders that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (HEIDENHAIN publishes no list prices, so there is no price build-up), other HEIDENHAIN encoder families and exposed encoders, mounting accessories and cables, and the machine itself. The limits are the published maxima; a real application can need a smaller envelope, which HEIDENHAIN confirms.

The AI sales agentBuilds the encoder 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 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
Measuring lengths that differ by model familyOnly with care
Each family has its own list of lengths, so a list per family has to be kept in step with the brochure, and a length that is not on the list must stop the quote.
The length is checked against the list of the selected model on every call.
Safety data that only some encoders and interfaces carryOnly with care
Functional safety applies to a few models with two interface types, with their own PFH and altitude limits, so a rule per model, interface and limit is needed.
The safety rating, PFH and altitude are looked up from the selected model and compared on every call.
Mounting rules that depend on length, acceleration and applicationOnly with workarounds
A spar is needed above a length, the safety fault exclusion has an acceleration limit, and clamping elements are not covered. Rules that fire in sequence show one issue at a time.
Each rule is evaluated together, and the cases the brochure does not cover go to a person for approval.
A rating the brochure does not publishOnly with workarounds
Vibration for some mountings is not published; a missing fact must not be silently treated as a pass or a block.
A fact that is not published becomes an approval finding rather than a pass or a block.
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.

1A measuring length of 650 mm is not offered for the selected encoder.
2A measuring length of 1,340 mm on this slimline encoder needs a mounting spar (or clamping elements on the LC 4x5); the quote has neither.
3A measuring length of 2,140 mm is not offered for the selected encoder.
4Clamping elements are published only for the LC 4x5 slimline encoders.
5The MSL 41 mounting spar is for the slimline encoders (LC 4x5, LF 485, LS 4x7); this is a full-size encoder.
6The quote needs an accuracy grade of 2 micrometers; the best grade published for the selected encoder at this measuring length is 3 micrometers.
7The quote needs an accuracy grade of 3 micrometers; the best grade published for the selected encoder at this measuring length is 5 micrometers.
8The interface of the control does not match the interface of the selected encoder.
9The cable run is 51 m; the selected encoder is published for at most 50 m.
10The cable run is 31 m; the selected encoder is published for at most 30 m.
11The traversing speed is 181 m/min; the selected encoder is published for at most 180 m/min.
12The acceleration in the measuring direction is 101 m/s2; the selected encoder is published for at most 100 m/s2.
13The traversing speed is 61 m/min; the selected encoder is published for at most 60 m/min.
14The acceleration in the measuring direction is 61 m/s2; the selected encoder is published for at most 60 m/s2.
15A TTL encoder needs one of the published combinations of integrated interpolation (5-fold, 10-fold, 20-fold) and scanning frequency; the quote has none.
16The traversing speed is 31 m/min; the selected encoder is published for at most 30 m/min.
17Integrated interpolation and a scanning frequency can be selected only on the TTL encoders (LS 477, LS 177).
18The vibration is 150 m/s2 (55 Hz to 2,000 Hz); the selected encoder with this mounting is published for at most 100 m/s2.
19The vibration is 101 m/s2 (55 Hz to 2,000 Hz); the selected encoder with this mounting is published for at most 100 m/s2.
20The brochure publishes no vibration rating for this mounting; a person should confirm 100 m/s2.
21The shock is 400 m/s2 (11 ms); the selected encoder is published for at most 300 m/s2.
22The ambient temperature range of -5 to 55 °C is outside the published operating range of 0 to 50 °C.
23IP64 protection is published only with sealing air from a DA 400 compressed air unit; the quote has no sealing air.
24The application needs a functional safety encoder (SIL 2, PL d); the selected encoder is not one of the LC 1x5 and LC 4x5 encoders with EnDat or DRIVE-CLiQ.

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. Slimline absolute encoder: LC 415 on a 1,340 mm length with the wrong interface and no spar

The agent's request. Please quote the HEIDENHAIN LC 415 linear encoder with 1,340 mm measuring length for a control with Fanuc serial (05) interface, with no mounting spar or clamping elements. The cable is 60 m, the traversing speed 120 m/min and the acceleration 80 m/s2. It is ready to send.

Verdict: Blocked.

  • Mounting spar required. A measuring length of 1,340 mm on this slimline encoder needs a mounting spar (or clamping elements on the LC 4x5); the quote has neither.
  • Interface does not match the control. The interface of the control does not match the interface of the selected encoder.

2. Slimline absolute encoder: The agent resubmits after fixing the errors

The agent's request. Please quote the HEIDENHAIN LC 495F linear encoder with 1,340 mm measuring length for a control with Fanuc serial (05) interface, with a mounting spar. The cable is 45 m, the traversing speed 120 m/min and the acceleration 80 m/s2. It is ready to send.

Verdict: Allowed.

  • Encoder limits. Model LC495F with 1,340 mm measuring length; published limits: 50 m cable, 180 m/min traversing speed, 100 m/s2 acceleration.

3. Functional safety axis: Safety application on an encoder without the safety rating

The agent's request. Please quote the HEIDENHAIN LC 485 linear encoder with 1,020 mm measuring length for a control with EnDat 02 interface, with no mounting spar or clamping elements. The cable is 40 m, the traversing speed 90 m/min and the acceleration 50 m/s2. It is a functional safety application at 800 m altitude. It is ready to send.

Verdict: Blocked.

  • Encoder not qualified for functional safety. The application needs a functional safety encoder (SIL 2, PL d); the selected encoder is not one of the LC 1x5 and LC 4x5 encoders with EnDat or DRIVE-CLiQ.

4. Functional safety axis: The agent resubmits after fixing the errors

The agent's request. Please quote the HEIDENHAIN LC 415 linear encoder with 1,020 mm measuring length for a control with EnDat 2.2 interface, with clamping elements. The cable is 40 m, the traversing speed 90 m/min and the acceleration 50 m/s2. It is a functional safety application at 800 m altitude that needs a PFH of at most 15 per 10 to the 9 hours. It is ready to send.

Verdict: Needs approval.

  • Safety with clamping elements. The brochure lists the fault exclusion for the housing mounting and the spar, not for clamping elements; a person should confirm the safety design.
  • Encoder limits. Model LC415 with 1,020 mm measuring length; published limits: 100 m cable, 180 m/min traversing speed, 100 m/s2 acceleration.

5. Functional safety axis: The agent resubmits after fixing the errors

The agent's request. Please quote the HEIDENHAIN LC 415 linear encoder with 1,020 mm measuring length for a control with EnDat 2.2 interface, with no mounting spar or clamping elements. The cable is 40 m, the traversing speed 90 m/min and the acceleration 50 m/s2. It is a functional safety application at 800 m altitude that needs a PFH of at most 15 per 10 to the 9 hours. It is ready to send.

Verdict: Allowed.

  • Encoder limits. Model LC415 with 1,020 mm measuring length; published limits: 100 m cable, 180 m/min traversing speed, 100 m/s2 acceleration.

6. TTL encoder: TTL encoder faster than its interpolation allows

The agent's request. Please quote the HEIDENHAIN LS 477 linear encoder with 720 mm measuring length for a control with TTL interface, with no mounting spar or clamping elements. The cable is 30 m, the traversing speed 90 m/min and the acceleration 60 m/s2. The interpolation is 10-fold at a scanning frequency of 25 kHz. It is ready to send.

Verdict: Blocked.

  • Traversing speed over the limit. The traversing speed is 90 m/min; the selected encoder is published for at most 30 m/min.

7. TTL encoder: The agent resubmits after fixing the errors

The agent's request. Please quote the HEIDENHAIN LS 477 linear encoder with 720 mm measuring length for a control with TTL interface, with no mounting spar or clamping elements. The cable is 30 m, the traversing speed 90 m/min and the acceleration 60 m/s2. The interpolation is 10-fold at a scanning frequency of 100 kHz. It is ready to send.

Verdict: Allowed.

  • Encoder limits. Model LS477 with 720 mm measuring length; published limits: 100 m cable, 120 m/min traversing speed, 100 m/s2 acceleration.

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 a quote for a HEIDENHAIN sealed linear encoder: the model, the control interface, the measuring length, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the selection data HEIDENHAIN publishes in its linear encoder brochure 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 HEIDENHAIN LC 415 linear encoder with 1,340 mm measuring length for a control with Fanuc serial (05) interface, with no mounting spar or clamping elements. The cable is 60 m, the traversing speed 120 m/min and the acceleration 80 m/s2. 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 measuring length of 1,340 mm on this slimline encoder needs a mounting spar (or clamping elements on the LC 4x5); the quote has neither. The interface of the control does not match the interface of the selected encoder.
  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 safety data that only some encoders and interfaces carry, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the encoder model to LC 495F, the cable length to 45 m and the mounting to a mounting spar.
  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.