FloTrace reads the passes off your logging tool and builds the survey. It picks up the curves, calibrates the spinner from your calibration passes, calls each valve open or closed, works the rates out in Mscf/D, and lays out the log presentation, gradient plots and summary tables.
The write-up comes with it. You check it, put your name on it, and send it.
No re-typing depths into a spreadsheet. No rebuilding the same chart for the hundredth time.
What it does with your files
You drop in the files
Down passes, up passes, stationary stops, surface recorders, ASCII gauge exports. Curves are recognised on arrival — DEPT, CCL, CFM, ILS, PRES, TEMP, ADEN, GR — whatever the tool called them, and whatever order they came in.
The spinner gets calibrated
Most interpretation normalises: fastest zone is 100%, everything else a share of it. FloTrace fits the calibration passes your crew already shoots — rps against cable speed — and solves the tool constant and the bearing-friction threshold. That is the difference between a percentage and a rate.
Valves get called
Every mandrel kicks the spinner whether or not the valve is passing gas. What decides it is whether the trend returns afterwards or settles on a new one. And where the flowmeter sat inside its own deadband, the valve is reported unresolved rather than guessed — which tells you what the next run needs to carry.
Rates come out in Mscf/D
Each zone converts at its own pressure and temperature, so a deep valve yields far more surface gas per downhole cubic foot than a shallow one. On a well we tested, the calibrated total landed within 0.4% of the casing meter — from the tool’s own passes, nothing scaled to match.
The report comes out
Log presentation, gradient plots, valve summary, zone contributions, ops log, well diagram — and the introduction, observations and interpretation, drafted from the computed table and never from figures it was not given. Your analyst edits and signs it before anything leaves.
The report is chosen from what the file actually carries — a caliper log produces a casing inspection, a log with QWZI and QWZT produces an injection profile, a flowmeter and valve depths produce a GLV survey.
White label throughout — your logo, your colours, your disclaimer. The operator sees your report. They never see us.
Files land, curves are read, rates are computed and the PDF goes out — without exporting into a second package and back. The delivered file is archived against the job, so an interpretation questioned six months later can be reproduced exactly as it was sent.
A valve the flowmeter could not resolve, a calibration shot in moving fluid, a downhole total that disagrees with the allocated surface split — all said out loud. A number quoted with false confidence is the one that costs you a customer.
There is no sign-up button on purpose. Workspaces are opened by hand, and we would rather work one of your own surveys first — ideally one where you already know the answer, so you can see where we agree with you and where we do not.