Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Radar bid evaluation becomes unreliable when two prices appear to cover the same tank but the offers contain different assumptions. One may include the required seal and commissioning support while another prices a standard assembly with those items unresolved. Read the exceptions before ranking the totals.
Build the Radar Bid Evaluation Around Required Evidence
Use the issued tank specification as the common basis. Record each offered configuration and classify its response as confirmed, alternative, excluded or awaiting clarification. Silence is not confirmation. Ask for an explicit answer where a missing item affects fit, chemical exposure, signal integration or acceptance.
| Item | Compare | Open point |
|---|---|---|
| Assembly | Offered connection, materials and pressure-temperature duty. | Does the quoted construction meet the specified operating conditions? |
| Signal | Electronics, power and receiving-system documents. | Are required functions supplied together or listed as separate alternatives? |
| Testing | Factory records, site work and witness responsibilities. | Who demonstrates the installed measurement and under which conditions? |
| Exclusions | Adapters, cables, access work and commissioning support. | What must another party supply before the instrument can operate? |
An MV-RD12 proposal should identify its actual construction rather than reproduce the whole product option list. A list containing HART and RS485 does not establish that both are delivered in the quoted unit. Compare the terminal drawing and order description, not just a catalogue heading.
Resolve an Alternative Without Losing the Original Requirement
A technically different offer may be acceptable, but the project owner must understand what changes. For example, a different output can require a receiver modification or extra power. Add those consequences to the comparison before calling the alternative less expensive.
Keep technical acceptance separate from commercial preference. Record who approves each deviation and what evidence supports it. Where evidence is pending, leave the item open; assigning a favourable numerical score does not resolve a missing material approval or incompatible connection.
Close the Evaluation With a Reconciled Scope
Ask the selected supplier to issue a final clarification incorporating accepted changes. Check that the purchase description, drawings and test commitments refer to the same revision. Conflicting email promises and quotation notes should be reconciled before dispatch rather than left for the installation team.
Q1. Should every deviation cause rejection?
No. Some alternatives meet the actual duty through a different arrangement. Assess their consequences and obtain the responsible approval. Rejecting or accepting them purely on wording can both produce a poor decision.
Q2. How should an unpriced installation dependency be handled?
Identify its owner and obtain a scope or allowance based on real work. Keep uncertainty visible in the commercial comparison. Do not assume excluded installation work costs nothing because the instrument price is complete.
Summary
Compare fully understood scopes, not superficially similar product names. Send the outstanding technical exceptions for a clarified METRAVON radar offer and retain the resolved configuration with the order so the delivered equipment can be checked against it.
