Line items and parameters
How one enquiry becomes instruments, and how each value is marked stated, assumed or missing.
Splits one enquiry into line items — one per distinct instrument specification, with tag numbers and quantity — then records every process parameter relevant to that category.
Grouping
Several tags sharing one specification become one line carrying all of them, because that is how the quotation is written (R20). Six LT-101…106 on the same range and fluid are one line with quantity six, not six quotations.
Each line is then enriched with its own fluid properties, so instruments on different fluids never share one lookup.
Each line gets a category: flowmeter, level instrument, level switch, or something Flowtech does not make. The last produces no quotation line, with a reason.
Origin of every value
| Origin | Meaning | Downstream |
|---|---|---|
| Stated | The customer wrote it. Evidence (the wording) is shown | May exclude a product if it breaches a known rating |
| Assumed | We derived or defaulted it | Never satisfies a required parameter (R16). A breach warns, it does not exclude |
| Missing | Required for this category and not stated | The list the sales person takes back to the customer |
Ambient pressure and 40 °C are assumed only when the enquiry states nothing, and never for steam or a stated gas (R17). A length is never kept as a pressure or temperature (R18). A size written in the source that no line captured is flagged in the customer’s own notation (R19).
A failed reading is marked as such, not presented as an enquiry that stated nothing (R21).
What the sales person does
Review each line, chase missing required parameters, and correct by re-processing after the customer answers — the reply lands on the same conversation. Option choices on a quotation whose line identity then changes are withheld (R36).
Related: Processing a case · Product suggestion.