Predictika · Machine vision camera, lens and cable quotes

An AI sales agent's machine vision camera quote, checked before it goes out

An AI sales agent prepares a quote for a JAI Go-X Series camera: the model, output bit depth, frame rate, a C-mount lens, the working distance and the cable run to the host. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published camera and lens tables and returns a verdict, every reason and the figures it computed.

Scope: JAI Go-X Series cameras (33 models, four interfaces) with the C-mount lenses JAI lists for them. See everything this validator covers

This validator models the 33 Go-X camera models in JAI's Camera Selection Guide and the 41 C-mount lenses JAI recommends for them in its lens brochure, not just the scenarios shown below.

  • Camera and output — the model must offer the requested output bit depth (8, 10 or 12 bits; the GOX-6409 is listed at 8 bits only) and frame rate, and the stated interface and resolution on the quote must match the model.
  • Interface throughput — above 8-bit output the validator checks that the pixels per second the quote needs fit within the effective data throughput JAI lists for the camera's interface (GigE Vision 1G, 5G, USB3 Vision or CoaXPress CXP-6).
  • Lens — the lens must be one JAI lists for that camera model, and the working distance must lie within the lens's listed working-distance range.
  • Cable run — the run must not exceed the maximum cable length JAI lists for the interface; for USB3 Vision, JAI gives 3 to 5 m, so runs of 4 or 5 m are flagged for a person to confirm.

Any quote for a Go-X camera with these lenses that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (neither JAI document gives prices, so this validator produces no price build-up or line-item quote), other JAI camera series, accessories, and models or lenses introduced after the guide (version 14) and lens brochure (October 2025, v8).

The AI sales agentBuilds the camera 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
Lens choices that depend on the exact camera modelOnly with care
A product rule per camera model listing its lenses. It works, but each of the 33 models is another list to keep correct as lenses change.		The lens is checked against the list for the selected model on every call, and the finding says so.
Working distance limits that differ by lensOnly with care
Each lens has its own minimum and, for some, maximum distance, so the rules multiply with the lens catalog.		The limits are looked up from the selected lens each time and each finding names the limit that applies.
Frame rate and bit depth against the interfaceOnly with workarounds
The data the camera produces is pixels times frame rate times bit depth, compared with what the interface can carry; this takes cross-field calculation rules.		The data rate is computed from the model, bit depth and frame rate on every call and compared with the interface limit.
A cable-length limit that depends on the interfaceOnly with workarounds
The limit comes from the interface of the chosen camera, and USB3 has a range rather than a single figure, so a rule has to read another rule's result.		Every choice is in one request, so the conflict is found whichever order the choices arrive in.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote 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 quote asks for 10-bit output, but this camera model is listed with up to 8-bit output.
29-bit output is not offered; the Go-X cameras are listed with 8, 10 and 12-bit output.
316-bit output is not offered; the Go-X cameras are listed with 8, 10 and 12-bit output.
4The quote asks for 12-bit output, but this camera model is listed with up to 8-bit output.
5The quote needs 30 frames per second, but this camera model is listed at 18 fps at full resolution.
6At 12-bit and 30 fps this camera needs at least 286.8 MB/s, more than the 115 MB/s effective throughput listed for its interface.
7The working distance of 50 mm is closer than the 100 mm minimum of this lens.
8A cable run of 150 m is longer than the 100 m maximum listed for this camera interface.
9The interface stated on the quote is not the interface of the camera model on it.
10The quote states 5.0 megapixels, but this camera model is listed at 6.3 megapixels.
11The lens on the quote is not among the lenses JAI lists for this camera model.
12The quote needs 30 frames per second, but this camera model is listed at 22 fps at full resolution.
13At 12-bit and 22 fps this camera needs at least 165.5 MB/s, more than the 115 MB/s effective throughput listed for its interface.
14At 12-bit and 74 fps this camera needs at least 556.6 MB/s, more than the 400 MB/s effective throughput listed for its interface.
15The working distance of 500 mm is farther than the 400 mm maximum of this lens.
16The working distance of 60 mm is closer than the 70 mm minimum of this lens.
17The working distance of 700 mm is closer than the 800 mm minimum of this lens.
18The working distance of 99 mm is closer than the 100 mm minimum of this lens.
19The working distance of 401 mm is farther than the 400 mm maximum of this lens.
20A cable run of 101 m is longer than the 100 m maximum listed for this camera interface.
21The selection guide gives the USB3 Vision cable length as 3 to 5 m; a run of 4 m depends on the cable used, so a person should confirm it.
22The selection guide gives the USB3 Vision cable length as 3 to 5 m; a run of 5 m depends on the cable used, so a person should confirm it.
23A cable run of 6 m is longer than the 5 m maximum listed for this camera interface.
24A cable run of 36 m is longer than the 35 m maximum listed for this camera interface.
25The quote states 3.2 megapixels, but this camera model is listed at 5.0 megapixels.
26The quote states 5.0 megapixels, but this camera model is listed at 5.1 megapixels.
27At 12-bit and 27 fps this camera needs at least 824.5 MB/s, more than the 560 MB/s effective throughput listed for its interface.
28The quote needs 80 frames per second, but this camera model is listed at 74 fps at full resolution.

  

  

    
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. 24.5 MP at 12-bit: A 24.5 MP camera on 1 GigE at 12-bit, 10 fps, with a lens JAI does not list for it

    
The agent's request. Please quote a GOX-24505-PGE camera with a JCH-C23-1628D lens, 12-bit output at 10 frames per second, working distance 500 mm and a 10 m cable run. The quote states GigE Vision 1G and 24.5 megapixels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Frame rate above the model listing. The quote needs 10 frames per second, but this camera model is listed at 4 fps at full resolution.
    • 
      
  • Interface cannot carry the data. At 12-bit and 10 fps this camera needs at least 368.3 MB/s, more than the 115 MB/s effective throughput listed for its interface.
    • 
      
  • Lens not recommended for the camera. The lens on the quote is not among the lenses JAI lists for this camera model.
    • 
    

    
2. 24.5 MP at 12-bit: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GOX-24505-5GE camera with a JMO-C11-3518XR lens, 12-bit output at 10 frames per second, working distance 500 mm and a 10 m cable run. The quote states GigE Vision 5G and 24.5 megapixels. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Camera. This camera is listed at 22 fps at full resolution on an interface with 560 MB/s effective throughput.
    • 
    

    
3. Camera 12 m from the PC: A USB3 camera on a 12 m cable with a lens used too close

    
The agent's request. Please quote a GOX-5102-USB camera with a JCH-C23-2528D lens, 8-bit output at 60 frames per second, working distance 80 mm and a 12 m cable run. The quote states USB3 Vision and 5.0 megapixels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Working distance below the lens minimum. The working distance of 80 mm is closer than the 100 mm minimum of this lens.
    • 
      
  • Cable run above the interface limit. A cable run of 12 m is longer than the 5 m maximum listed for this camera interface.
    • 
    

    
4. Camera 12 m from the PC: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GOX-5105-CXP camera with a JCH-C118-1620C lens, 8-bit output at 60 frames per second, working distance 250 mm and a 12 m cable run. The quote states CoaXPress CXP-6 and 5.1 megapixels. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Camera. This camera is listed at 112 fps at full resolution on an interface with 625 MB/s effective throughput.
    • 
    

    
5. USB3 camera at a bench: A USB3 camera quoted above its frame rate on a 4 m cable

    
The agent's request. Please quote a GOX-8901-USB camera with a JCH-C1-3514A lens, 8-bit output at 40 frames per second, working distance 150 mm and a 4 m cable run. The quote states USB3 Vision and 8.9 megapixels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Frame rate above the model listing. The quote needs 40 frames per second, but this camera model is listed at 32 fps at full resolution.
    • 
      
  • USB3 cable length to confirm. The selection guide gives the USB3 Vision cable length as 3 to 5 m; a run of 4 m depends on the cable used, so a person should confirm it.
    • 
    

    
6. USB3 camera at a bench: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GOX-8901-USB camera with a JCH-C1-3514A lens, 8-bit output at 30 frames per second, working distance 150 mm and a 4 m cable run. The quote states USB3 Vision and 8.9 megapixels. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • USB3 cable length to confirm. The selection guide gives the USB3 Vision cable length as 3 to 5 m; a run of 4 m depends on the cable used, so a person should confirm it.
    • 
      
  • Camera. This camera is listed at 32 fps at full resolution on an interface with 400 MB/s effective throughput.
    • 
    

    
7. USB3 camera at a bench: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GOX-8901-USB camera with a JCH-C1-3514A lens, 8-bit output at 30 frames per second, working distance 150 mm and a 3 m cable run. The quote states USB3 Vision and 8.9 megapixels. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Camera. This camera is listed at 32 fps at full resolution on an interface with 400 MB/s effective throughput.
    • 
    

  

  

    
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 JAI Go-X Series camera: the model, output bit depth, frame rate, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published camera and lens tables 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 a GOX-24505-PGE camera with a JCH-C23-1628D lens, 12-bit output at 10 frames per second, working distance 500 mm and a 10 m cable run. The quote states GigE Vision 1G and 24.5 megapixels. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings, all in one answer. The quote needs 10 frames per second, but this camera model is listed at 4 fps at full resolution. At 12-bit and 10 fps this camera needs at least 368.3 MB/s, more than the 115 MB/s effective throughput listed for its interface. The lens on the quote is not among the lenses JAI lists for this camera model.
    6. 
      
  6. The validator returned three 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 lens choices that depend on the exact camera model, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the camera model to GOX-24505-5GE, the lens to JMO-C11-3518XR and the stated interface to GigE Vision 5G.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All three earlier findings are cleared.
    13. 
      
  13. Three 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.