Composite sampler grab volume is the size of each individual dose a sampler injects into the receiver, and it works together with how often those grabs are taken to determine how full the receiver ends up over a batch. Set the grab too large or the grabs too frequent and the receiver overflows before the batch ends; set them too small and the receiver is barely wetted and the sample is short. Getting a representative, correctly sized composite is mostly a matter of arithmetic between grab size, grab frequency, batch size, and receiver capacity. This page explains that grab-sizing arithmetic.
Composite Sampler Grab Volume in one line: Composite sampler grab volume is the fixed volume of product injected into the receiver on each grab of a flow-proportional composite sampler. Multiplied by the number of grabs a batch will produce, it must fill the receiver to a proper level without overflowing, so grab volume and grabs-per-unit-volume are chosen together against the batch size and receiver capacity.
A flow proportional composite sampler builds one representative sample by injecting many small grabs into a receiver over the course of a batch, pacing those grabs to the metered flow so each unit of product contributes equally. Two settings govern the outcome. The grab volume is how much product each injection delivers, fixed by the sampler's dosing mechanism. The grab frequency, expressed as grabs per unit of throughput, say one grab per some number of barrels, is how often those injections happen. The receiver's final fill is simply the grab volume multiplied by the total number of grabs the batch produces.
The number of grabs a batch produces follows directly from the batch size and the frequency: divide the total metered volume of the batch by the volume between grabs to get how many grabs occur. Multiply that grab count by the grab volume and you have the total sample collected. That total has to land in a sensible window: enough to fill the receiver adequately for the lab to draw a representative portion, but comfortably under the receiver's capacity so it never overflows and loses the tail of the batch. Planning the receiver fill is exactly this multiplication done before the batch, not discovered during it.
Because two levers control one outcome, there is room to trade them off. If grabs are made larger, they can be made less frequent to hit the same fill, and vice versa. But representativeness sets a floor on frequency: too few grabs across a batch, no matter how large, samples the stream too coarsely to be representative of a changing product, so a minimum number of grabs over the batch is wanted regardless of fill. In practice grab frequency is set first to be representative, and grab volume is then chosen so that the resulting number of grabs fills the receiver to the right level.
Sizing starts from what is known: the expected batch volume, the receiver capacity, and a target fill somewhere below full that leaves margin. From the receiver target and a chosen grab frequency you can solve for the grab volume, because the number of grabs is the batch volume divided by the volume between grabs, and the grab volume is the target fill divided by that grab count. Equivalently, if the sampler's grab volume is fixed by its hardware, you solve the other way and set the frequency so that the fixed grab volume times the resulting grab count lands on the target fill.
The arithmetic has to respect real constraints at both ends. There is a minimum number of grabs across a batch below which the composite is no longer representative, which caps how large and infrequent the grabs can be. There is the receiver capacity, which caps the total and forces overflow protection into the plan, especially when the batch runs larger than expected. And there is a smallest reliable grab the mechanism can deliver repeatably, below which grab to grab variation itself becomes a source of error. A good setting sits inside all of these: enough grabs to be representative, small enough grabs and low enough total that the receiver never overflows, and large enough grabs that each dose is consistent.
Variable batch size is the practical complication. A frequency and grab volume tuned for a nominal batch will underfill a short batch and threaten to overflow a long one, because the grab count scales with the volume that actually flows. That is why flow proportional grab count matters more than a fixed grab schedule: pacing grabs to metered volume keeps the sample proportional to throughput, and choosing the grab volume with headroom keeps even an unexpectedly long batch inside the receiver. Where batch sizes vary widely, the safe move is to size for the largest credible batch so the receiver never overflows, and accept a lighter fill on the smaller ones.
When a receiver comes back wrong, the fill level itself is the first clue. An overflowing or brim full receiver at the end of a batch means the grab volume, the frequency, or both were too high for the batch that actually ran, or the batch ran longer than the settings assumed. A barely wetted receiver means the opposite: grabs too small, too infrequent, or a batch shorter than planned, leaving too little sample for the lab and too few grabs to be representative. A receiver that fills inconsistently batch to batch points to grab to grab volume variation in the dosing mechanism. The diagnostic is arithmetic: take the batch volume that actually flowed, the frequency, and the grab volume, multiply out the expected fill, and compare it to what the receiver holds.
The inputs to that arithmetic are all live values a control system already handles: the metered batch volume, the grab count the sampler has taken, and the grabs per unit setting driving it. That means the grab plan is not something that has to be reconciled only after the batch by looking at the receiver; the expected fill can be tracked as the batch proceeds. A sampler falling behind its grab schedule, or a batch running far longer than the receiver was sized for, is knowable before the receiver overflows rather than after.
A cloud SCADA platform such as Merobix reads the metered volume, the sampler's grab count, and the grab pacing from the flow computer and sampler controller, so operators can watch a batch's projected receiver fill in real time across every sampling station. The team can be alerted when a batch is on track to overfill or underfill its receiver, confirm the sampler is keeping grab count proportional to throughput, and see at reconciliation that each composite was collected on the right number of correctly sized grabs. The dosing still happens at the sampler, but the arithmetic that says the sample was correctly sized becomes visible and auditable from one place.
Grab volume is chosen together with grab frequency so that the grab volume times the number of grabs a batch produces fills the receiver to a target level below its capacity. Frequency is usually set first, so there are enough grabs across the batch to be representative, and then grab volume is picked so the resulting grab count lands on the target fill without overflowing the receiver.
Divide the batch's total metered volume by the volume between grabs to get the number of grabs, then multiply that grab count by the grab volume to get the total sample collected. Compare that total to the receiver capacity: it should fill the receiver adequately for the lab while staying comfortably below full so it never overflows and loses the end of the batch.
If grab volume or frequency is too high for the batch, the receiver overflows and the tail of the batch is lost, so the composite no longer represents the whole transfer. If it is too low, the receiver is barely wetted, leaving too little sample for the lab and too few grabs to be representative. Because grab count scales with batch volume, settings tuned for a nominal batch can overflow a long one, which is why sizing for the largest credible batch is the safe approach.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.