Concrete batching aggregate bin volume
Sand, gravel, and aggregate bays have uneven surfaces, partitions, loader traffic, and changing refill cycles that make single-point level data weak.
Confirm the site problem, the Volivue approach, and the expected operating benefit before final selection.
Procurement and dispatch teams cannot plan accurately when each aggregate bay is checked manually or only after production issues appear.
Use compact fixed 3D scanning nodes or V7300 Mini packages above bins, map each bay boundary, and calculate volume on a scheduled cycle.
The plant gains bay-level stock visibility, refill timing, and CSV/API data for production planning.
Small, fast-changing aggregate bays defeat single-point level readings
Concrete batching plants store sand, crushed stone, and recycled aggregate in open bays separated by partition walls. Loaders cut into the piles many times per hour, refill trucks tip new material against the back wall, and washing or spray systems add surface moisture. The result is a set of small, fast-changing piles where a single level point or a glance from the loader cab routinely misjudges usable stock.
Fixed 3D scanning suits multi-bay plants that buy aggregate by the truckload and need per-bay volume for dispatch and procurement. A compact Volivue V7300 Mini package covers a typical bay from one mounting point. For tall sealed cement or fly-ash silos at the same plant, a Volivue 80GHz radar level transmitter on the silo top is the better-matched instrument.
One compact node per bay, scheduled around loader traffic
Each bay gets a compact scan node mounted on the roof beam or canopy above the pile, positioned so the partition walls do not shadow the back corners. The bay boundary model records wall lines and floor reference once during commissioning, after which volume is computed against that fixed geometry. Scan cycles are scheduled into gaps between loader passes so moving machines never contaminate the surface model.
Per-bay volume, refill alerts, and trend history publish from the Volivue platform as CSV files or API calls that batching software and procurement spreadsheets can consume directly. Sites typically wire scan nodes over Ethernet to the plant office or use 4G where trenching is impractical. Commissioning is bay by bay, so a plant can start with critical sand bays and extend coverage later.
Planning inputs for a multi-bay batching plant rollout
- Count the bays to cover, and measure partition wall height and spacing against planned mounting points.
- Confirm canopy or roof beam positions that clear the loader swing path and the maximum pile height.
- Agree scan timing around loader work windows so surface models are captured between machine passes.
- List each aggregate type with its bulk density so per-bay volume can feed tonnage-based ordering.
Do loaders working in the bay corrupt the volume measurement?
A scan captured while a loader sits in the bay would include the machine, so the system schedules scans into gaps between passes and filters transient objects. Bays with near-continuous traffic are reviewed for a faster scan cycle or an extra mounting position rather than promising clean data through constant movement.
How many scan nodes does a typical bay need?
Most single bays in batching plants are covered from one compact node when the mounting point is high enough and partitions do not shadow the corners. Wide bays, L-shaped bays, or low canopies may need a second node. The layout review answers this from your bay drawings before any hardware is quoted.
Six checks decide whether the project needs V260, V7300 Mini, or a multi-scanner package.
Site survey and drawings
Collect shed or bin dimensions, pile height, roof structure, mounting points, vehicle routes, power, network, dust, and safety limits.
Scanner layout design
Define scanner count, field of view, blind zones, mounting height, scan schedule, and maintenance access.
Base model and zones
Build floor reference, boundary polygons, zone naming, empty reference, and reporting units before final volume output.
Algorithm and density workflow
Validate point-cloud cleaning, volume calculation, density assumptions, and estimated mass reporting against site checks.
Integration and handover
Map dashboard fields, CSV/API/OPC outputs, report schedule, alarm rules, user roles, and acceptance checks.
Documentation package
Prepare layout notes, point lists, report field definitions, density assumptions, role settings, acceptance records, and maintenance notes for later scenario pages.
Questions that decide scanner layout, volume confidence, integration, and project scope.
Is this a LiDAR system or a 3D radar system?
Volivue positions the page as a fixed 3D scanning product family. The project may use V260 3D stockpile scanners, V7300 Mini 3D radar scanners, or fixed LiDAR nodes depending on range, dust, mounting, and site layout.
Can one scanner cover a whole warehouse?
Only in compact scenes with clear line of sight. Long coal sheds, domes, aggregate bays, and large yards usually need scanner layout review and may need multiple scanning positions.
Does the system directly measure weight?
No. It measures pile shape and calculates volume. Estimated mass needs density assumptions, sampling data, or a customer density table documented in the project.
How accurate is the volume?
Accuracy depends on survey quality, base model, blind zones, dust, material surface, scanner position, and validation method. Volivue confirms a project target after reviewing the site.
Can it work in dusty coal sheds?
It can be reviewed for dusty sheds, but dust intensity, scan distance, cleaning plan, mounting protection, and data filtering must be checked before committing to coverage.
Can it export data to ERP or MES?
Yes. Scope can include dashboard reports, CSV, Web API, OPC, Modbus TCP, MQTT, database export, or ERP/MES handoff.
What should we send for quotation?
Send shed or bin drawings, photos, pile height, material, dust condition, power and network availability, current inventory method, required reports, and target integration interface.
What documents are usually included for handover?
The handover package can include scanner layout notes, point lists, interface maps, report templates, density assumptions, user roles, acceptance records, and maintenance or cleaning notes by scope.
Send pile geometry, site photos, material, dust level, and target reports.
Share drawings, photos, pile height, material, dust condition, mounting locations, power and network options, update cycle, and desired dashboard or ERP/MES outputs.