Radar Level Acceptance Decision: Pass, Conditional or Reject

Acceptance is an engineering decision, not the absence of an alarm during startup. A radar may be mechanically correct but not yet proven in foam, dust or high temperature; it may measure locally while the PLC scaling or alarm action remains wrong. The decision should compare objective evidence with predefined criteria and classify the result as pass, conditional acceptance or rejection. Conditions need owners, controls and closure tests. This approach allows practical project progress without turning missing evidence or known limitations into undocumented permanent operation.

Define criteria before testing

Set requirements for application envelope, model and materials, geometry, diagnostics, measurement points, output tolerance, alarms, faults and documents before results are known. Identify mandatory and conditional items. Predetermined criteria prevent teams from relaxing limits after a difficult result or rejecting acceptable measurement because of unrealistic precision.

Verify application identity

Confirm medium, temperature, pressure, vapour, foam, dust, range, fill rate and required duty against the approved model and assembly. Record exact antenna, seal, connection and certification. Any assumption changed since purchase should return to technical review rather than be accepted through commissioning alone.

Verify mechanical completion

Measure reference plane, nozzle, antenna projection, alignment, blocking distance and beam clearance. Check pressure boundary, gasket, housing, glands, grounding and access. Attach photographs and close defects that affect safety, certification or measurement before functional approval. Configuration should not compensate for a preventable mechanical deviation.

Verify measurement and diagnostics

Compare distance and level with known references at useful points and representative process states. Review raw echo, signal margin, competing targets and tracking. Record false-echo mapping and lost-echo behavior. Identify conditions not observed. A plausible displayed value without diagnostic context is weak acceptance evidence.

Verify the complete output path

Record current or digital variables, PLC or DCS tag, HMI, historian, units, scaling, quality and timestamps. Test device fault, open circuit, communication loss, stale value, power and recovery. Confirm alarm and interlock pickup, delay, reset and final action. Remove forces and bypasses independently.

Classify the decision

Pass only when mandatory criteria and evidence are complete. Use conditional acceptance when missing evidence has a bounded risk, temporary control, named owner, due date and specific closure test. Reject when safety, certification, application fit or critical performance is not supported. Record who has authority for each disposition.

Close conditions visibly

Maintain an open-item register linked to the instrument tag and operating restrictions. Attach new evidence and formal closure approval. Expired conditions should escalate rather than disappear from reports. Operators must know any temporary limitation that changes alarm, filling or maintenance practice.

Retain and review the basis

Store application data, exact identity, as-built drawings, settings, diagnostics, tests, deviations and approvals. Reopen acceptance after meaningful process, geometry, firmware, output or control changes. Schedule early-service review where commissioning did not cover the full envelope.

Engineering checklist

Set acceptance limits before results.
Confirm the current application envelope.
Measure as-built mechanics.
Review raw diagnostics and known points.
Test faults and final actions.
Give every condition an owner and closure test.

Frequently asked questions

Is conditional acceptance acceptable?

Yes, when risk is bounded and controls, ownership and closure evidence are explicit.

What should force rejection?

Unsupported safety, pressure, certification, application or critical performance conditions.

When is a condition closed?

Only after the specified evidence is reviewed and formally accepted by the responsible owner.

Decision record

Keep a concise approval record that states the operating case, assumptions, accepted limits, responsible owner and evidence reviewed. Attach the relevant drawing, configuration, test results and unresolved deviations. Define what process, mechanical, electrical or software change requires reassessment. This record prevents a technically sound decision from becoming an unsupported setting after staff, equipment or operating conditions change.

Need a project-specific review? Send process data, drawings, photographs and acceptance criteria through our contact page.