Predictika · Forklift safety quotes

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

An AI sales agent prepares an order for a fleet of forklifts: the Forklift Gateway and Unity subscription, Speed Manager, Pedestrian Proximity Detection, a video recorder with cameras and an SD card, Forklift Scales and Safety Lights. Before the order goes out, the agent sends it to Predictika, which checks it against a declarative model of what each truck type and each option allows and returns a verdict and every reason.

Scope: Powerfleet On-Site IoT forklift safety kits: Forklift Gateway and Unity, Speed Manager, Pedestrian Proximity Detection, DVR with cameras and SD card, Forklift Scales and Safety Lights, by truck type. See everything this validator covers

This validator models On-Site IoT forklift orders, not just the scenarios shown below.

  • Gateway and Unity — Speed Manager needs a Forklift Gateway, and the gateway needs a Unity subscription.
  • Speed Manager — it needs a fly-by-wire throttle and offers two configurable throttle levels; on an internal-combustion truck a technician confirms the wiring.
  • Proximity detection — one to five alert zones, with a site survey for four or five and a person to confirm when there is no gateway to link breaches to an operator.
  • Video — a recorder takes one to four cameras, and the hours of stored video must fit the SD card.
  • Scales and fleet size — Forklift Scales cannot be fitted to an order picker or pallet jack, and a rollout above 250 trucks goes to a person.

Any On-Site IoT forklift order that touches these rules is in scope — not only the scenarios pictured here. Not covered: Powerfleet On-Road products, asset and off-road IoT and prices. The product names, up to five proximity zones, two Speed Manager throttle levels, fly-by-wire throttles, up to four DVR cameras and the 128 GB SD card limit follow the public Powerfleet On-Site page. All other rules, including the truck-type limits, hours per card and approval thresholds, are modeled from comparable products, not published by Powerfleet. No prices are modeled.

The AI sales agentBuilds the forklift safety order from the conversation with the customer 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
Options that depend on each otherOnly with care
Speed Manager needs the gateway and the gateway needs Unity, so the dependencies must be chained and kept in step.
Every dependency is checked in the same pass, whatever order the options were chosen in.
Limits that depend on the truck typeOnly with workarounds
Scales, Speed Manager wiring and throttle type depend on the truck, so a table of truck types and options is needed and easy to leave incomplete.
The truck type is checked against every option together on each call.
Counts that must stay in rangeOnly with care
Zones, cameras and throttle levels each have their own range, and a count typed too high is often caught only at installation.
Each count is checked against its range and the findings say which one is off.
Storage that must fit the video asked forOnly with workarounds
Hours of video depend on the card size, so a calculation sits beside the rule and must be updated with every new card.
The hours the card holds are computed in the model and compared with the hours requested.
Soft limits that need a personOnly with care
Four or five zones, an internal-combustion truck or a large fleet are not errors but need confirmation, which rules often block or ignore.
These come back as approvals, separate from the blocking findings.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order 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.

1The order asks for 3 throttle speed levels, but Speed Manager offers two configurable levels.
2Speed Manager is triggered by impacts and checklist failures reported through the Forklift Gateway, but the order has no Forklift Gateway.
3Speed Manager requires an electronically controlled (fly-by-wire) throttle, but the truck has a mechanical throttle.
4Speed Manager on an internal-combustion counterbalance truck needs the throttle wiring confirmed by a technician.
55 proximity zones on one truck need a site survey of the cabin view; a person should confirm it.
6The order asks for 6 proximity alert zones, but Pedestrian Proximity Detection supports 1 to 5 zones.
7Without a Forklift Gateway the proximity breaches are not linked to an operator ID; a person should confirm the customer accepts this.
8The order puts 5 cameras on one Digital Video Recorder, which supports 1 to 4 cameras.
9The order lists 2 cameras but no Digital Video Recorder.
10The order asks for 101 hours of stored video, but the chosen SD card holds about 100 hours.
11Three or four cameras on a 32 GB card give very short recording history; a person should confirm the card size.
12Forklift Scales weigh the load on the mast hydraulics and cannot be fitted to an order picker or pallet jack.
13The Forklift Gateway reports its data to the Unity platform, but the order has no Unity subscription.
14The order covers 0 trucks; at least 1 is needed.
15A rollout of 251 trucks needs a deployment plan reviewed by a person.

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. Reach trucks with Speed Manager, proximity and cameras: Reach trucks with Speed Manager, proximity detection and a DVR with cameras

The agent's request. Please quote Powerfleet On-Site IoT for 120 reach trucks, with Speed Manager set to 3 throttle levels, Pedestrian Proximity Detection with 6 alert zones and a DVR with 5 cameras and 80 hours of stored video on a 128 GB SD card. It is ready to send.

Verdict: Blocked.

  • Speed Manager needs a Forklift Gateway. Speed Manager is triggered by impacts and checklist failures reported through the Forklift Gateway, but the order has no Forklift Gateway.
  • More than two throttle speed levels. The order asks for 3 throttle speed levels, but Speed Manager offers two configurable levels.
  • Proximity zones outside 1 to 5. The order asks for 6 proximity alert zones, but Pedestrian Proximity Detection supports 1 to 5 zones.
  • DVR cameras outside 1 to 4. The order puts 5 cameras on one Digital Video Recorder, which supports 1 to 4 cameras.
  • Proximity alerts without operator identity. Without a Forklift Gateway the proximity breaches are not linked to an operator ID; a person should confirm the customer accepts this.

2. Reach trucks with Speed Manager, proximity and cameras: The agent resubmits after fixing the errors

The agent's request. Please quote Powerfleet On-Site IoT for 120 reach trucks, with the Forklift Gateway and a Unity subscription, Speed Manager set to 2 throttle levels, Pedestrian Proximity Detection with 5 alert zones and a DVR with 5 cameras and 80 hours of stored video on a 128 GB SD card. It is ready to send.

Verdict: Blocked.

  • DVR cameras outside 1 to 4. The order puts 5 cameras on one Digital Video Recorder, which supports 1 to 4 cameras.
  • Four or five proximity zones to confirm. 5 proximity zones on one truck need a site survey of the cabin view; a person should confirm it.

3. Reach trucks with Speed Manager, proximity and cameras: The agent resubmits after fixing the errors

The agent's request. Please quote Powerfleet On-Site IoT for 120 reach trucks, with the Forklift Gateway and a Unity subscription, Speed Manager set to 2 throttle levels, Pedestrian Proximity Detection with 3 alert zones and a DVR with 4 cameras and 80 hours of stored video on a 128 GB SD card. It is ready to send.

Verdict: Allowed.

  • Order summary. 120 trucks; a DVR card of this size holds about 100 hours.

4. Order pickers with scales and a small SD card: Order pickers with Forklift Scales and a DVR on a small SD card

The agent's request. Please quote Powerfleet On-Site IoT for 60 order pickers, with the Forklift Gateway and a Unity subscription, a DVR with 3 cameras and 40 hours of stored video on a 32 GB SD card, Forklift Scales and Forklift Safety Lights. It is ready to send.

Verdict: Blocked.

  • Video retention above the card capacity. The order asks for 40 hours of stored video, but the chosen SD card holds about 25 hours.
  • Forklift Scales on a truck without a weighing hydraulic. Forklift Scales weigh the load on the mast hydraulics and cannot be fitted to an order picker or pallet jack.
  • Three or four cameras on a 32 GB card. Three or four cameras on a 32 GB card give very short recording history; a person should confirm the card size.

5. Order pickers with scales and a small SD card: The agent resubmits after fixing the errors

The agent's request. Please quote Powerfleet On-Site IoT for 60 order pickers, with the Forklift Gateway and a Unity subscription, a DVR with 3 cameras and 40 hours of stored video on a 128 GB SD card and Forklift Safety Lights. It is ready to send.

Verdict: Allowed.

  • Order summary. 60 trucks; a DVR card of this size holds about 100 hours.

6. Speed Manager on internal-combustion trucks: Speed Manager on internal-combustion trucks with the Forklift Gateway

The agent's request. Please quote Powerfleet On-Site IoT for 200 internal-combustion counterbalance trucks, with the Forklift Gateway and Speed Manager set to 1 throttle level. It is ready to send.

Verdict: Blocked.

  • Forklift Gateway needs Unity. The Forklift Gateway reports its data to the Unity platform, but the order has no Unity subscription.
  • Speed Manager on an internal-combustion truck. Speed Manager on an internal-combustion counterbalance truck needs the throttle wiring confirmed by a technician.

7. Speed Manager on internal-combustion trucks: The agent resubmits after fixing the errors

The agent's request. Please quote Powerfleet On-Site IoT for 200 internal-combustion counterbalance trucks, with the Forklift Gateway and a Unity subscription and Speed Manager set to 1 throttle level. It is ready to send.

Verdict: Needs approval.

  • Speed Manager on an internal-combustion truck. Speed Manager on an internal-combustion counterbalance truck needs the throttle wiring confirmed by a technician.
  • Order summary. 200 trucks; a DVR card of this size holds about 100 hours.

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 fleet of forklifts: the Forklift Gateway and Unity subscription, Speed Manager, Pedestrian Proximity Detection, and more. Before the order goes out, the agent sends it to Predictika, which checks it against a declarative model of what each truck type and each option allows and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote Powerfleet On-Site IoT for 120 reach trucks, with Speed Manager set to 3 throttle levels, Pedestrian Proximity Detection. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with four findings and one approval, all in one answer. Speed Manager is triggered by impacts and checklist failures reported through the Forklift Gateway, but the order has no Forklift Gateway. The order asks for 3 throttle speed levels, but Speed Manager offers two configurable levels. The order asks for 6 proximity alert zones, but Pedestrian Proximity Detection supports 1 to 5 zones. The other one is on screen.
  6. The validator returned four 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. What this shows: for soft limits that need a person, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the Forklift Gateway to yes, the unity subscription to yes, the throttle levels to 2 and the proximity alert zones to 5.
  10. It calls the validator again.
  11. Still blocked, with one finding and one approval, all in one answer. The order puts 5 cameras on one Digital Video Recorder, which supports 1 to 4 cameras.
  12. Four findings cleared. Still blocking: DVR cameras outside 1 to 4. A new approval needs a person: four or five proximity zones to confirm.
  13. The agent resubmits once more.
  14. The revised request. It changes the proximity alert zones to 3 and the cameras to 4.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. Both earlier findings are cleared.
  18. Five 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.