Identify tools and records separately
List the selected instruments and the observations expected from each, with the actual tool identities confirmed at the agreed milestone. Distinguish a tool model from an individual instrument and its relevant records. A channel named temperature does not reveal which tool supplied it. Ask the bidder how the delivered arrangement retains that relationship rather than assume that different source files can later be combined without ambiguity.
Retain run and configuration context
Agree the references needed to distinguish campaigns, runs and relevant instrument configurations. The same tool can produce observations under different assignments, so an instrument serial number alone may not identify the complete record context. Request representative outputs showing the relationships supported by the supplied software. Keep purchaser-assigned identifiers and provider-generated references distinguishable, with responsibility for preparing and maintaining the actual information stated in the offer.
Keep imported channels linked to their source
Where the truck software accepts records from another tool or external measurement package, ask how source identity and original files are retained. An imported column should not silently become a direct truck measurement. Identify any mapping and conversion applied. Procurement should establish a usable integration path without promising universal format compatibility or assuming every instrument can be combined into one live acquisition stream simply because it supplies a familiar quantity.
Connect samples without confusing types of traceability
If the program associates fluid samples with instrument observations, retain sample identity, collection context and responsible external handling information separately. A chain-of-custody record describes sample history; it is not the same claim as metrological traceability of a measurement result. Ask which links the purchased software supports and which remain with the project team or laboratory, avoiding an undefined fully traceable label for several different evidence functions.
Demonstrate a reviewable handover set
Include representative multiple-tool and run records with the agreed source references and mapping information. Ask the intended reviewer to check that each observation can be related to its origin without relying on informal operator memory. State limitations and external file dependencies explicitly. Retain final instrument and configuration records so later replacements or imported datasets can be assessed against the actual identification and output functions supplied with the truck.
Buy understandable relationships rather than a merged spreadsheet alone
Have bidders show how instrument, run, channel and external source references remain available after export. Compare the supported record structure and purchaser responsibilities, not just the ability to display several traces together. The final offer should identify which relationships are created automatically, which require authorized input and which are outside the supplied software. This supports professional evaluation without treating every imported value as a direct measurement, equating sample custody with calibration evidence or promising that identical channel names establish equivalent instrument performance.
Put these items side by side in the bid review
| Purchase item | Question to resolve | Evidence to request |
|---|---|---|
| Instrument | Which tool produced the observation? | Actual identity and source references |
| Context | Which run and configuration apply? | Accepted record mapping |
| External data | What was imported or sample-linked? | Original files and responsibility schedule |
Suggested wording for the quotation request
Define record identity for the proposed well test truck across the attached instruments and runs. Preserve tool, source-file and channel relationships, with imported observations and transformations explicitly identified. State any supported sample-context links separately from measurement calibration evidence. Demonstrate a usable handover set and list purchaser or laboratory responsibilities without assuming that a merged display alone establishes the origin or equivalence of every value.
Select the well test truck against the accepted instrument program and required measurement outputs. Identify the actual tools, line arrangement, depth and load basis, acquired channels and supported working environment. Keep deployment equipment, recording functions, external pressure control and surface flow-test systems under explicit supply boundaries. A calibration certificate supports an identified measurement, not universal truck accuracy or an unrestricted test result. Ask for the evidence and limitations that matter to the intended decision. Retain the selected configuration, interface documents and verification records with the purchase; actual wellsite work requires competent personnel and approved procedures.
For the wider equipment scope, consult the Well Test Truck: External Fluid-Sample Records. Use the RFQ checklist to collect the supporting documents before requesting a configuration-specific quotation.
Buyer questions
Does a shared channel name establish a shared measurement source?
No. Retain the actual instrument and record origin.
Is sample custody the same as metrological traceability?
No. They describe different evidence relationships and should be identified separately.
Background and supplier contact
NIST metrological traceability background offers related background, not certification of the equipment in a quotation. Applicability must be checked for the project and destination.
Explore the well test truck, browse all technical resources, or visit Vance Petroleum for company information. Request a well-test package proposal with identified instruments, measurement tasks, acquisition interfaces and destination requirements.