Predictika · Flender B3 bevel helical gear unit selection check

A sales assistant's gear unit quote, checked against the Flender catalog before it goes to the customer

A sales assistant puts together a quote for a Flender B3 bevel helical gear unit and says it is ready to send. Before it goes out, the assistant sends it to Predictika's validator, which checks the required rating, peak torque, thermal capacity, cooling and lubrication against the catalog tables together and reports every problem in one pass.

Scope: Selection of B3 horizontal bevel helical gear units, sizes 4 to 28, against the public Flender MD 20.1 (2018) catalog, chapter 3: nominal power rating, peak torque, thermal capacity, cooling and lubrication. No prices: the catalog lists none. See everything this validator covers

This validator checks any B3 gear unit selection against the catalog tables, not just the scenarios shown below.

  • Required rating — the driven machine power times the application, load-hours, prime-mover and ambient factors, compared with the nominal rating of the selected size, ratio and input speed.
  • Peak torque — peaks per hour, alternating or steady load, and the peak torque the unit may carry.
  • Thermal capacity — the catalog thermal capacity for the cooling chosen (none, fan, coil or both), oil type, ambient temperature and altitude.
  • Lubrication — ratings that are only available with forced lubrication, and the approval needed when forced lubrication is ordered.
  • Table limits — sizes, ratios and speeds that are not in the tables, ratings listed on request only, and stated figures that do not match the calculation.

Any B3 selection that touches these rules is in scope, not only the scenarios pictured here. Not checked: other gear unit types, vertical mounting, shaft and coupling loads, and prices (the catalog lists none). The validator reflects the catalog edition named above.

The sales assistantCollects the order lines from the customer and says the gear unit quote is ready to send.
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 sales assistant says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: sales assistant (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where a rules-based product configurator gets this wrong

Click to expand

Our assessment of what a typical rules-based configurator or quoting tool (one rule per field, each limit checked on its own) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtA rules-based product configuratorPredictika
A rating that depends on many factors at onceOnly with care
The required rating multiplies several catalog factors that each depend on the application, hours and prime mover, so every combination needs its own rule.
The factors and the rating table are in one model and the required rating is computed on every call.
Thermal capacity that depends on the cooling chosenOnly with workarounds
Switching from no cooling to fan cooling changes the catalog thermal capacity for the unit, and a checklist treats cooling and thermal capacity as unrelated fields.
Cooling, oil, ambient temperature and altitude are in the same request, so the thermal result follows every change.
A rating that is allowed only with a special optionOnly with care
Shaded catalog cells need forced lubrication, and forced lubrication in turn needs a person to confirm the thermal check, so one rule hides behind another.
The shaded-cell rule and the approval rule are checked together, and a recorded approval is part of the request.
A fix that changes the next checkOnly with care
Moving to a larger size or a different prime mover changes the rating, the thermal capacity and the stated figures together.
Every check is re-evaluated together on each call, whatever order the choices arrive in.
Every problem returned in one answerOnly with workarounds
Form checks usually stop at the first failing field, so a salesperson fixes one error and meets the next.
All findings come back together.

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 required nominal rating (P2 x f1 x f2) must not exceed the nominal rating P2N of the selected unit.
2The thermal capacity PG with the chosen cooling must be at least the thermal power needed (P2 x Kth); otherwise choose stronger cooling or a larger unit.
3A rating the catalog marks as shaded requires forced lubrication for horizontal gear units, so dip lubrication is blocked there.
4When forced lubrication is ordered, the catalog thermal capacities assume dip lubrication, so the thermal check must be confirmed with Flender (approval).
5The peak torque must stay within the limit for the unit, depending on peaks per hour and whether the load is steady or alternating.
6The size, ratio and input speed must be in the catalog tables, and a rating shown as a dash or listed on request only cannot be quoted.
7A stated nominal rating or required rating that does not match the calculation is blocked.
8The ambient temperature must be a catalog step and the altitude must be inside the catalog range.
9The installation must be a large hall, otherwise the thermal figures need approval.

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. Belt conveyor drive on a size 9 unit: A belt conveyor drive with no cooling

The agent's request. Please check this quote for Harlan Aggregates: a Flender B3 size 9 gear unit, ratio 56, 1,500 rpm, for a 71 kW belt conveyor running 12 hours a day with seven 720 Nm peaks an hour at 40 C, with no cooling. The unit rating is 100 kW and the required rating is 92.3 kW. It is ready to send.

Verdict: Blocked.

  • Thermal capacity too low. With this cooling the thermal capacity PG is 59.4 kW, below the 63.9 kW needed (P2 x Kth); choose stronger cooling or a larger unit.
  • Selection summary. Required nominal rating 92.3 kW, selected unit P2N 100.0 kW; thermal capacity PG 59.4 kW against 63.9 kW needed.

2. Belt conveyor drive on a size 9 unit: The agent resubmits after fixing the errors

The agent's request. Fan cooling has been added to the same order for Harlan Aggregates. Everything else is unchanged. Please check it again.

Verdict: Allowed.

  • Selection summary. Required nominal rating 92.3 kW, selected unit P2N 100.0 kW; thermal capacity PG 126.75 kW against 63.9 kW needed.

3. Heavy belt conveyor on a size 13 unit: A 900 kW conveyor on a size 13 unit with dip lubrication

The agent's request. Please check this quote for Delmar Bulk Terminals: a Flender B3 size 13 gear unit, ratio 12.5, 1,800 rpm, for a 900 kW belt conveyor running 12 hours a day at 40 C with fan and coil cooling and dip lubrication. The unit rating is 1,198 kW and the required rating is 1,170 kW. It is ready to send.

Verdict: Blocked.

  • Forced lubrication required. The catalog marks this rating (shaded cell) as requiring forced lubrication for horizontal gear units, and the order says dip lubrication.
  • Selection summary. Required nominal rating 1170.0 kW, selected unit P2N 1198.0 kW; thermal capacity PG 873.48 kW against 810.0 kW needed.

4. Heavy belt conveyor on a size 13 unit: The agent resubmits after fixing the errors

The agent's request. The order for Delmar Bulk Terminals now specifies forced lubrication. Everything else is unchanged. Please check it again.

Verdict: Needs approval.

  • Forced lubrication needs approval. Forced lubrication is ordered; the catalog thermal capacities assume dip lubrication, so confirm the thermal check with Flender.
  • Selection summary. Required nominal rating 1170.0 kW, selected unit P2N 1198.0 kW; thermal capacity PG 873.48 kW against 810.0 kW needed.

5. Heavy belt conveyor on a size 13 unit: A person has approved the forced lubrication

The agent's request. A Flender application engineer has confirmed the thermal check for the forced lubrication, and the approval is recorded on the order. Please check it once more and release the quote.

Verdict: Needs approval.

  • Forced lubrication needs approval. Forced lubrication is ordered; the catalog thermal capacities assume dip lubrication, so confirm the thermal check with Flender.
  • Selection summary. Required nominal rating 1170.0 kW, selected unit P2N 1198.0 kW; thermal capacity PG 873.48 kW against 810.0 kW needed.

6. Engine drive on a size 9 unit: A piston engine drive with 1 to 3 cylinders

The agent's request. Please check this quote for Ridgeway Pump Works: a Flender B3 size 9 gear unit, ratio 56, 1,500 rpm, driven by a 1 to 3 cylinder piston engine for a 71 kW belt conveyor, with fan cooling. The unit rating is 100 kW and the required rating is 138.4 kW. It is ready to send.

Verdict: Blocked.

  • Rating too low for the load. The required nominal rating is 138.45 kW (P2 x f1 x f2) and this B3 unit has a P2N of only 100.0 kW.
  • Selection summary. Required nominal rating 138.45 kW, selected unit P2N 100.0 kW; thermal capacity PG 126.75 kW against 63.9 kW needed.

7. Engine drive on a size 9 unit: The agent resubmits after fixing the errors

The agent's request. The order for Ridgeway Pump Works now uses a size 10 unit with a 4 to 6 cylinder piston engine. The unit rating is 123 kW and the required rating is 115.4 kW. Please check it again.

Verdict: Allowed.

  • Selection summary. Required nominal rating 115.375 kW, selected unit P2N 123.0 kW; thermal capacity PG 141.75 kW against 63.9 kW needed.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. A sales assistant puts together a quote for a Flender B3 bevel helical gear unit and says it is ready to send. Before it goes out, the assistant sends it to Predictika's validator, which checks the required rating, peak torque, thermal capacity, cooling and lubrication against the catalog tables together and reports every problem in one pass.
  2. I will start with the first request by the agent.
  3. The agent says. Please check this quote for Delmar Bulk Terminals: a Flender B3 size 13 gear unit, ratio 12.5, 1,800 rpm, for a 900 kW belt conveyor running 12 hours a day at 40 C. The unit rating is 1,198 kW and the required rating is 1,170 kW. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with one finding, all in one answer. The catalog marks this rating (shaded cell) as requiring forced lubrication for horizontal gear units, and the order says dip lubrication.
  6. The validator returned one blocking finding 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 rating that is allowed only with a special option, a rules-based product configurator is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the lubrication to forced.
  10. It calls the validator again.
  11. Not blocked, but held for a person.
  12. The one blocking finding is cleared; one approval remains for a person: forced lubrication needs approval.
  13. The agent resubmits once more.
  14. The revised request. It sets the approval recorded to yes.
  15. It calls the validator once more.
  16. The required approval is recorded, so the validator accepts the release.
  17. The required approval is recorded, so the validator accepts the quote.
  18. One problem caught in one call, fixed in two passes, and the corrected quote now goes to a person for approval. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.