CRI monitoring is the operating memory of the disposal system. Without reliable volume, pressure, rate and slurry records, teams cannot distinguish normal variability from deterioration, reconcile waste disposal, or give the subsurface model trustworthy inputs. The goal is not more sensors; it is a traceable data chain from waste generation and slurry batch to the injection event.
This control belongs to a connected operating system. Use the CRI engineering pillar, the integrated surface process and formation capacity and containment together; changing one boundary can move the constraint elsewhere.
Define the minimum data set
A useful record normally includes date/time, batch identity, injected volume, injection rate, surface pressure, slurry density and relevant QA/QC, carrier/flush volumes, well/configuration state, downtime and abnormal events. Add project-specific downhole or temperature data where provided.
| Data group | Minimum basis | Use |
|---|---|---|
| Batch / slurry | ID, density and applicable QA/QC | Links material properties to injection response |
| Volume | Opening, additions/receipts, injected/disposed and closing inventory on one stated basis | Reconciliation and capacity accounting |
| Pressure & rate | Synchronized measurements and units | Normalized operating trends |
| Configuration | Well/path/valve state | Prevents comparing unlike hydraulic states |
| Events | Downtime, alarms, interventions and data gaps | Cause analysis and audit trail |
Volume reconciliation
On one explicitly converted basis, opening inventory + received material + documented additions − injected or externally disposed material − closing inventory = reconciliation difference. Do not add wet-waste volume, carrier-fluid volume, slurry volume and dry-equivalent solids without conversion to a common conserved basis. Large unexplained differences should be investigated rather than hidden in a balancing entry.
Worked mass-balance screen
All four values in this illustrative screen are slurry volume on the same calibrated basis; it is not a dry-solids balance.
If opening slurry inventory is 120 bbl, 780 bbl is prepared during the period, 760 bbl is recorded as injected and closing inventory is 130 bbl, the unreconciled difference is 120 + 780 − 760 − 130 = 10 bbl. That 10 bbl is not automatically a loss; it is a reconciliation difference to compare with tank gauging, meter uncertainty, flush accounting and transfers.
Synchronize time bases
Pressure, rate, batch and QA/QC data must share a usable time reference. If a slurry sample cannot be matched to the injection interval it represents, correlation becomes speculative.
Trend normalized operating points
Where possible, compare pressure at similar rate and slurry condition. Track sustainable processing/injection throughput, downtime causes and repeated interventions. A dashboard should make changes visible, not bury them in averages.
Data quality and audit trail
Document meter status, calibration, manual edits, missing intervals and unit conversions. A precise-looking trend built from inconsistent instruments is false confidence.
From monitoring to action
Define who reviews the data, how often, what constitutes an abnormal trend and when the subsurface/well-integrity team is engaged. Monitoring without decision rules is only archiving.
Choose one reporting basis
State whether volumes are measured slurry barrels, carrier-fluid barrels, wet waste, dry-equivalent solids or another project metric. Different bases answer different questions. Mixing them in one KPI can create impressive but meaningless efficiency percentages.
Meter and tank uncertainty
Tank strapping, level measurement, entrained air, vessel motion, meter calibration and density assumptions can all affect reconciliation. Define an expected uncertainty band based on the actual measurement system. A small mismatch inside that band should not be treated the same as a persistent unexplained trend.
Downtime classification
Separate planned maintenance, drilling-related holds, surface equipment failures, slurry-quality holds and subsurface/injection holds. Total downtime alone does not tell the team where reliability investment belongs. A Pareto of well-defined causes is more actionable.
Batch traceability
Assign a batch or time-window identity that follows material from preparation through injection. Link QA/QC, grinder condition, tank, injected volume and pressure-rate response. This turns isolated laboratory numbers into operating evidence.
Daily review should ask questions
A good daily review asks: did volume reconcile, did pressure-rate behavior shift, were any batches off trend, did sustainable throughput meet waste generation, and are there unresolved alarms or data gaps? The report should end with actions and owners, not only a table of yesterday's numbers.
The best CRI record lets another competent engineer reconstruct what was injected, under what conditions, and how the system responded. That is the standard for useful assurance data.
Common questions
What are the most important CRI monitoring variables?
Injected volume, rate, pressure, slurry/batch properties, configuration and abnormal events are core variables; projects may require additional downhole and subsurface data.
Why reconcile CRI volumes?
Reconciliation checks whether generation, preparation, injection and inventory records form a credible material balance and exposes data gaps.
Does a dashboard replace engineering review?
No. Visualization helps identify trends, but interpretation and escalation still require engineering judgment and project governance.
