USE CASE · MATERIAL FLOW AI

Material flow optimisation AI
for industrial conveyors.

A LiDAR + camera pair on the belt continuously classifies and measures the bulk material crossing the conveyor — ore grade, contamination, blend ratio. Feeds the blending model, prevents off-spec batches, gives the control room a real material balance instead of an inferred one. Custom-built on top of OWL EYE® Volume Flow.

10–50 Hz classification sampling rate
85–95 % typical classification accuracy
0.5–5 m/s belt-speed range
Volume Flow builds on the OWL EYE® sensor
USE CASE  ·  Material flow classification · LiDAR + camera on the belt

A real material balance, not an inferred one.

Material flow AI is a perception pipeline that runs on top of a conveyor-belt scanner (LiDAR + camera) to continuously classify and analyse the material crossing the belt — ore grade, contamination type, blend ratio — and feeds the result into your blending model, your control room, your material balance.

The pain is simple. A belt scale gives you mass per unit time. A volume scanner — like our OWL EYE® Volume Flow — gives you volume and density. Neither tells you what is on the belt. And in cement, sugar, fertiliser, recycling, ore processing and grain handling, that is exactly the question that drives blending, off-spec prevention and contract billing. The control room ends up inferring composition from feeder set-points and lab samples that arrive hours after the shift is over.

Our approach starts at the belt cross-section. A 2D LiDAR profiles the geometry of the material flow, a colour camera captures surface signature, and reflectivity at the belt adds a third channel. A per-section classification model — trained on your material categories (ore grades, contamination types, blend components, off-spec patterns) — labels every scan. Results aggregate into per-minute, per-shift and per-day flow reports, and the same stream drives real-time alarms when contamination spikes or the blend drifts off target.

This is not an off-the-shelf SaaS. Every plant has its own feed sources, its own blend recipe and its own control-room stack. We treat every engagement as a discovery + fixed-scope build, descending from our hub service Industrial Perception AI. Often layered on top of an existing OWL EYE® Volume Flow or Stockpile installation — same sensor, additional software layer.

„A belt scale tells you how much. A volume scanner tells you how big. Neither tells you what — and 'what' is what drives the blend."

Built on the same perception stack that powers OWL EYE® Volume Flow and Stockpile in production at industrial sites today.

Three stages

From belt to blender — three stages of the pipeline.

1 · Sensor at the belt

A 2D LiDAR for geometry plus a colour camera for material signature, mounted over the belt or at a transfer point. Often the same sensor pair already installed for OWL EYE® Volume Flow — one mechanical install, two pipelines. IP65+ housings, dust-tolerant optics, runs through the full shift in mill, mine and recycling-plant conditions.

2 · Per-section classification

The classifier model labels every belt cross-section against your material categories — ore grades, contamination types, blend components, off-spec patterns. Models retrained on your labelled data, not on a public benchmark. Aggregated to per-second, per-minute, per-shift and per-day flow records ready for the control room and the historian.

3 · Blend feedback + alarms

Classification results write into the blending PLC, the historian and the ERP material balance — OPC UA, MQTT, REST. The blender sees real composition instead of feeder set-points. Contamination spikes and off-spec mixes trigger control-room alarms before the bad batch reaches the silo or the customer.

Pipeline architecture · #how-it-works

How the pipeline works — concretely.

We keep the architecture boring on purpose. Three loosely coupled stages, each one independently testable, each one swappable when the sensor stack or the recipe changes. Built on the same stack we use across all our perception work: PCL, Open3D, OpenCV, PyTorch.

01

Belt cross-section capture

The 2D LiDAR profiles the belt at 10–50 Hz, producing overlapping cross-sections of the material flow. The colour camera adds a synchronised, lens-calibrated frame of the same patch of belt. Belt-speed input from the existing encoder ties geometry to mass and aligns frames into a continuous longitudinal record. Raw data writes to local storage with a per-section UUID for audit trail and re-labelling.

02

Per-section classification + aggregation

The point cross-section goes through ground removal, voxel down-sampling and a PointNet-style classifier trained on your material categories. The colour frame goes through a CNN trained on the same labels. Outputs fuse into one per-section prediction — typically 85–95 % classification accuracy on production data, depending on how clean your material categories actually are — then aggregate to per-second, per-minute, per-shift and per-day rollups.

03

Blender / control-room write-back

Per-second output: class label and confidence, mass per category, contamination flags. Writes into the blending PLC, the DCS, the historian and the ERP material balance over OPC UA, MQTT or REST — whatever the plant already runs. The blending model now reads real composition instead of inferring it from feeder set-points and delayed lab samples.

All three stages run on an industrial PC at the belt cabinet. No cloud dependency, no external API, no licence dial-home. The code is yours at handover.

What you get

Three deliverables — from the same pipeline.

Per-section classification stream

Every belt scan gets a structured record: class label, confidence, estimated mass per category, contamination flags, audit image. Published continuously over OPC UA or MQTT, archived to the historian, and ready for cross-link with belt-scale and feeder records.

Aggregated flow report

Material composition rolled up per minute, per shift and per day — comparable across feeders, belts and product lines. Same temporal model we use on stockpile monitoring — applied to belt flow. Drops straight into the production-quality dashboard and the contract-billing record.

Real-time contamination + off-spec alarms

When contamination spikes or the blend drifts off target, the system raises a control-room alarm before the bad batch reaches the silo, the rail wagon or the customer. Routed into the existing DCS alarm list — no new operator screen to learn, no parallel dashboard to ignore.

Why custom

Why a custom build — not an off-the-shelf product.

Every plant has its own feed sources, its own blend recipe and its own control-room stack. A generic classifier solves the generic case; your case is not the generic case.

Material-specific classification

Your blend, your contamination definitions, your off-spec patterns. We calibrate the classifier on your material under your lighting and dust conditions, and we re-calibrate when the feed source or recipe changes. A cement raw-mix classifier and a copper-ore-grade classifier share the same architecture and nothing else.

Builds on OWL EYE® Volume Flow

If you already run OWL EYE® Volume Flow on the belt, the AI layer reuses the same sensor — one mechanical install, two pipelines. Volume and mass continue to flow into the belt-scale and inventory record; classification flows into the blender and the contamination alarm. No second portal, no second cabinet.

Plant-specific blender + ERP integration

We integrate with your blending PLC, your historian, your ERP material balance — OPC UA, MQTT, REST, analog outputs all supported. No generic "let's send you a CSV every hour". The blender reads classification at control-loop rates; the ERP reads aggregated composition per shift; the historian keeps the per-section record for audit.

IP ownership + clean handover

You own the source code, the model weights and the labelled dataset at handover. We document the system, train your team, and walk away clean. No black box, no monthly per-tonne licence, no service contract you can't exit. See our FAQs on IP and engagement model for the standard terms.

FAQ

Questions about material flow AI.

The engagement-model questions we hear from every plant considering a custom perception build on top of OWL EYE® Volume Flow. Need something more specific to your belt? Ask us.

Industrial Perception AI

What does custom perception AI software cost? +
We don't publish list prices because every project is scoped against your data and your decision logic — but we work to three predictable tiers. Discovery & Assessment — a 1–3 day workshop, on-site or remote, fixed price in the low-four-figure range. You receive a written feasibility note, a recommended next step and (if applicable) a fixed-price quote for the follow-on project. Useful even if you don't then go ahead — many customers use the note to evaluate two or three vendors. Custom Pipeline / Tool — a 4–12 week project delivering a working perception pipeline (parser + algorithm + dashboard or OPC UA integration). Fixed scope, fixed price, you own the code at handover. Typical project size is in the mid-five to low-six-figure range depending on data volume, sensor count and integration depth. Long-term Partnership — a monthly retainer for ongoing development and on-call support. Sized to the team capacity you need (typically 0.5–2 FTE equivalent). Quarterly road-mapping included. All three tiers include source code, written documentation and a clean handover — no licence dependence on us. See our Industrial Perception AI service for the full engagement model.
How long does it take to build a custom perception pipeline? +
From signed contract to a working tool in production, expect 4–12 weeks for a standard custom-pipeline engagement. The spread is driven by three factors. Data readiness. If you already have labelled data or representative recordings, we start training in week 1. If we need to set up data collection, add a sensor, or label from scratch, the front end adds 1–3 weeks. Integration depth. A standalone dashboard with REST output is the fastest path — typically 4–6 weeks. OPC UA integration into a running control system, with interlocks, factory-acceptance tests and a customer change-management process, is closer to 8–12 weeks. Sensor count and site complexity. One LiDAR + one camera in a clean indoor environment is faster than a six-sensor outdoor portal with dust, snow and dynamic lighting. We scope the difference up-front in the Discovery workshop. For a faster first signal we recommend the Discovery & Assessment tier — 1–3 days, fixed price, written feasibility note within a week. See Industrial Perception AI for the full model.
Who owns the code and IP we pay you to build? +
You do. Our standard contract transfers full ownership of the project-specific code, model weights, training data (where the data is yours) and documentation to you on final acceptance. We don't keep a back-door licence and we don't lock you into a maintenance contract. What we retain is our pre-existing toolbox — reusable libraries, calibration utilities, generic data parsers, the OWL EYE® core — which we license to you, royalty-free, for use on the delivered tool. This is the same boundary that any reputable engineering firm draws: we bring the toolbox, you keep the deliverable. If you want a different IP arrangement — for example a joint patent on a novel algorithm, or a co-developed model that we both reuse with consent — we structure that explicitly in the project contract. Tell us up-front in the Discovery workshop. Full engagement details on our Industrial Perception AI page.
Can you use our existing cameras and LiDAR sensors? +
Yes — in most cases. Our toolchain is sensor-agnostic on the data layer. If your sensors deliver a standard format (PCD, LAS, E57 for point clouds; RTSP, GigE Vision, USB3 Vision for cameras) we can ingest them in a day. We've worked with Riegl, Livox, Faro, Hesai, Velodyne, Ouster, Basler, FLIR, Allied Vision and IDS cameras. We'll tell you honestly when the existing hardware isn't the right tool. Common cases where we recommend a replacement: - The existing LiDAR is too narrow (FoV or range) to cover the area you want classified — usually solved by repositioning before buying anything new. - The camera is auto-exposing on a high-contrast scene (sun + shadow at a gate), which breaks classification reliability — solved by switching to a manual-exposure industrial camera with HDR sensor. - The existing sensor's vendor lock-in (proprietary stream format, no documented SDK) makes integration cost more than a Livox replacement. We don't earn a margin on reselling hardware to you. If you do want us to source new sensors, we do that through our normal Hardware & products channel at list price. See Industrial Perception AI for how we scope it.

Send us a scan from your belt.

A few sample point clouds, a few camera frames, a description of your material categories — we come back within two business days with a written feasibility note and a fixed-price scope for the discovery workshop. Often layered on top of an existing OWL EYE® Volume Flow installation. Part of our Industrial Perception AI service.

info@sachtleben-technology.com +49 7831 969 22-190
Send us a message

Tell us about your conveyor belt.

Sensor setup, sample point clouds, your material categories, your blender interface — anything you have. We come back within two business days with an honest first assessment and a fixed-price scope for the Discovery workshop.

Company address (optional)Firmenadresse (optional)Adres firmy (opcjonalnie)Indirizzo azienda (opzionale)Adresse de la société (facultatif)Dirección de la empresa (opcional)Endereço da empresa (opcional)
Direct line Direktwahl Telefon bezpośredni Linea diretta Ligne directe Línea directa Linha direta
Mon — Fri · 08:00 – 17:00 CET Mo — Fr · 08:00 – 17:00 Uhr Pn — Pt · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Vie · 08:00 – 17:00 CET Seg — Sex · 08:00 – 17:00 CET
Email E-Mail E-mail Email E-mail Correo electrónico E-mail
Response within one business day. Antwort innerhalb eines Werktages. Odpowiedź w ciągu jednego dnia roboczego. Risposta entro un giorno lavorativo. Réponse sous un jour ouvré. Respuesta en un día laborable. Resposta em um dia útil.
Headquarters Unternehmenssitz Siedziba główna Sede principale Siège social Sede central Sede
Sachtleben Technology GmbH
Tresdorf 6
24238 Mucheln
Germany Deutschland Niemcy Germania Allemagne Alemania Alemanha
Last updated: