Industrial automation spare parts, urgent sourcing, and global supply support.

A velocity sensor and a proximity probe may both appear in a vibration spare list, but they serve different measurement chains. Choosing the wrong one can leave a monitor without the expected input, range, mounting, or output behavior. The model-checking question is not “does it measure vibration?” but “what signal does this machine channel require?”

ZYPLC readers need to distinguish sensor types before an outage. A short product description can hide the difference between velocity, displacement, proximity, proximitor, transmitter, and monitor hardware. The spare record should make that difference explicit.

Identify the measurement role

Record whether the channel measures velocity, displacement, shaft position, casing vibration, speed, alarm, or trip. Add mounting, connector, power, output, range, environmental requirements, and the monitor receiving the signal.

The live Bently Nevada 330500-01-02 velocity sensor is a product match for a velocity-channel RFQ. The 330980-51-05 proximitor reference shows why related vibration hardware must be named by its function.

Photograph the sensor label, connector, mounting, cable, junction box, monitor input, and machine location. Include the safe dimensional and environmental evidence needed for the quote.

Do not substitute by connector or brand

A similar connector or manufacturer name does not prove range, sensitivity, output, mounting, power, or monitor compatibility. Compare the complete signal chain before accepting a substitute.

If the channel supports an alarm or trip, state that role and the required functional test. Bench continuity or a visual check cannot prove the plant protection path.

Ask suppliers to distinguish exact sensor, possible substitute, repair, and calibration or test support. Keep missing evidence open rather than hiding it in a generic quote.

Acceptance should prove the trend and alarm

After installation, verify mounting, power, signal, scaling, range, trend, alarm, and any required trip behavior. Compare the result with an approved reference or baseline.

Record whether the item was inspected, bench-tested, calibrated, or field-accepted.

Save the sensor label, channel role, cable pairing, calibration record, settings, and final test. The next RFQ should start with the measurement function.

Build the RFQ around the installed function

A useful spare request begins with the installed function, not only a familiar brand name. State what the device does, where it sits, what it connects to, and what failure would stop or blind the process. Then add the exact label, revision, connector view, power information, accessory scope, condition requirement, destination, and required date. This gives procurement and engineering the same starting point.

Separate an exact replacement from a possible substitute, repair exchange, bench item, and migration candidate. These options may all be commercially useful, but they do not carry the same approval burden. An exact spare may support a short outage window. A substitute may need wiring changes, parameter review, software work, or a production trial before it can be counted as recovery stock.

The product references in this article are live catalog examples, not permission to skip engineering checks. Compare the product page with the installed label and the plant record. If a suffix, connector, voltage, protocol, firmware family, or mechanical interface differs, keep the item conditional until the responsible engineer closes that gap.

Receiving inspection should repeat the evidence used for the RFQ. Photograph the received label, packaging, connectors, terminals, mounting features, and included accessories. Record what was checked and what remains unknown. A clean-looking item is not automatically a field-ready spare, and an item that powers up is not automatically accepted by the control or protection function.

Keep the approved catalog and RFQ reference with the maintenance record, but do not let a catalog title replace the installed evidence. The useful record is the combination of model, function, interface, condition, test requirement, and decision owner.

Review the spare before the maintenance window, not only after a failure. Confirm that the item is still physically present, that packaging and accessories are intact, that the backup or test procedure is available, and that the responsible engineer is still named.

When a substitute is considered, write down the exact gap it is intended to close and the evidence needed to approve it. This may include a drawing comparison, firmware review, bench test, dimensional check, protection test, communication test, or production trial.

The final decision should be visible to stores, procurement, maintenance, and operations. Use plain status labels such as exact replacement, approved substitute, repair exchange, bench-only, or engineering review required.

FAQ

What is the difference between a velocity sensor and a proximity probe?

They measure different physical quantities and belong to different signal chains, mounting methods, and monitor inputs.

What must match on a 330500-01-02 spare?

Match measurement role, range, output, mounting, cable, power, environment, and receiving monitor.

Can a proximitor replace a velocity sensor?

No. The installed channel and engineering design must identify the correct sensor type.

What proves the sensor is accepted?

Mounting, signal, scaling, trend, alarm, and any required trip or baseline checks.

Send ZYPLC the sensor label, channel role, cable and mounting photos, monitor input, and deadline. We can help distinguish the correct vibration spare before purchase.

Before approval, record what the supplier cannot determine from a catalog page. Unknown firmware, missing drawings, unclear terminal scope, incomplete accessories, and untested condition should remain open items. This keeps the quote honest and gives engineering a short review list before the maintenance window.

A useful record also states what the supplier cannot determine from a catalog page. Unknown firmware, missing drawings, unclear terminal scope, incomplete accessories, and untested condition should be written as open items so the quote remains honest and the plant has a short list of questions to close before the equipment is needed.