Skip to main content
All integrations
Vision + Inspection

Pleora eBUS + Ignite Lean

Available now

Pleora eBUS connects GigE Vision cameras. Bridge results into builds.

REST API Webhooks

How the Connection Works

Pleora eBUS
REST APIWebhooks
Ignite Lean
Into Ignite Lean
  • Camera streams + inspection results
Back to Pleora eBUS
  • Capture triggers

How It Works

  1. 1Pleora publishes data via REST.
  2. 2Ignite Lean attaches to builds.
  3. 3Capture triggers fire on operator events.

Recommended Workflows

How Pleora eBUS works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Pleora eBUS routes it (which work group, which device, which rule) is configured to your IT setup.

Inline inspection raises an NC instantly
Trigger A vision system flags a fail
  1. 1Pleora eBUS posts the fail result + defect image to Ignite Lean.
  2. 2Ignite Lean attaches it to the build and opens an NC.
  3. 3The line gates downstream steps until the NC clears.
Quality is enforced at the camera, not just after the fact.
Active recipe pushes to the camera
Trigger A build of a new product starts
  1. 1Ignite Lean pushes the active recipe / inspection model to Pleora eBUS.
  2. 2The camera switches to the right configuration automatically.
  3. 3Operators never select a recipe by hand.
No mis-set cameras, no false fails.

Connect Pleora eBUS today

This works now through our REST API, outbound webhooks, and Excel/CSV. Start with the API reference, or talk to us about a guided setup.

API ReferenceTalk to Us