FRU means field-replaceable unit. It is an assembly intended to be replaced at the equipment location by appropriately trained service personnel, rather than repaired down to individual components in the field. The term describes a service strategy—not a guarantee that replacement is simple, safe, or plug-and-play.
Key takeaways
- An FRU is a manufacturer-defined service unit.
- One FRU may contain boards, sensors, firmware, calibration data, and mechanical parts.
- Part number, revision, configuration, and follow-up procedures still determine whether replacement is appropriate.
01
Why FRUs exist
Field service balances downtime, repeatability, training, tooling, and risk. Swapping a verified assembly can restore function faster than diagnosing a board to component level. The removed unit may then be repaired in a controlled depot with specialized fixtures and test coverage.
Manufacturers choose FRU boundaries differently. A computer may be one FRU on one platform but be separated into power supply, storage, GPU, and motherboard FRUs on another. A detector module may be replaceable individually or only as part of a larger detector assembly.
02
FRU number versus numbers on the FRU
A label can carry several identifiers. The number used to manufacture an internal board may differ from the number used to order the complete service assembly. A serial number identifies one instance; a revision identifies a design state; a spare or FRU number identifies the service item. Treating every printed number as an orderable part number is a common sourcing error.
03
What replacement may require
FRU replacement can require software configuration, option transfer, firmware alignment, calibration, pairing, serialization, safety testing, or a specific startup sequence. Mounting hardware and consumables may be separate. The correct service document identifies prerequisites and return-to-use tests.
04
A practical example
Consider an acquisition computer. The visible chassis may match a candidate, but the correct FRU could include a validated hardware configuration, image, licenses, interface cards, and platform-specific firmware. A generic computer with similar specifications may not communicate correctly or may place the device outside its supported configuration.
Related terminology
Terms with a published definition link directly to the glossary.