How to Digitize Asset Visibility in MRO Facilities

A technician needs a calibrated torque wrench for Bay 4. The system says it’s in the tool crib. It isn’t. Twenty minutes later, he finds it two hangars over, left on a cart from the previous shift. The aircraft sat idle the entire time.

Multiply that by every shift, every bay, every facility. IATA reported at least $11 billion in aviation supply-chain disruption costs for 2025, citing an order backlog above 18,000 aircraft and an average fleet age of 15.2 years. Oliver Wyman projects global commercial MRO demand near $140 billion in 2026, driven by aging fleets and constrained capacity. More aircraft needing heavy checks, fewer available slots, scarcer rotable parts. The cost of not finding what you already own keeps climbing.

I’ve spent over 15 years in IoT integration, and here’s what I see repeated: facilities buy tags before defining what question the system needs to answer. The result is a dashboard full of dots nobody trusts. Digitizing asset visibility in MRO facilities is not a hardware project. It’s a decision-architecture project where hardware is one layer.

This is the approach that works.

What Asset Visibility Actually Means in MRO

In most industries, “asset visibility” means knowing where something is. In MRO, that’s necessary but nowhere near sufficient.

An aircraft component sitting on a shelf in your storeroom is not “visible” if you can’t confirm its part number, serial, condition code, remaining shelf life, associated release documentation, and authorization for the specific work order requesting it. Location without status is noise. The FAA makes this explicit: AC 119-2A states that an RFID tag’s presence does not, by itself, determine a component’s serviceability.

Real asset visibility in MRO connects five things simultaneously:

• Identity: which specific serialized part, tool, or piece of equipment.
• Location: where it is right now, or where it was last confirmed.
• Custody: who has it, and since when.
• Condition: serviceable, quarantined, awaiting inspection, or unserviceable.
• Authorization: whether it’s cleared for the task at hand, and with which documents.

GS1’s EPCIS framework calls this the “what, when, where, why” model: what asset moved, when it moved, where it went, and why (which work order, which authorization, which custody transfer).

This is where the line between shipment tracking and asset tracking becomes concrete. Shipment tracking ends at delivery. Asset tracking follows the item through receipt, inspection, stocking, issue, installation, removal, repair, return, and reuse. In an MRO facility, the asset’s lifecycle doesn’t start at receiving. It cycles. If your visibility ends when the part hits the shelf, you’re running blind through most of the value chain.

Start With Decisions, Not Tags

The most common failure pattern I see: an MRO director visits a trade show, watches an impressive demo with blinking dots on a hangar map, and launches a procurement process for RFID or UWB hardware. Six months later, the system is installed. Twelve months later, nobody trusts it because it doesn’t connect to the maintenance system, can’t distinguish between serviceable and quarantined stock, and generates more exceptions than it resolves.

Before selecting any technology, answer three questions about your facility:

1. What can’t you find right now, and what does it cost? Measure the baseline. Average time-to-find for tools, parts, and ground equipment. Stockout events per week. Hours burned on cycle counts. AOG delays caused by a part that existed in inventory but couldn’t be located or verified in time.
2. Where does custody break? Map the handoff points where items move between people, departments, or condition codes without a recorded event. Receiving to QC. QC to storeroom. Storeroom to technician. Technician to aircraft. Removal back to bench. Each unrecorded handoff is a visibility gap.
3. Which existing system is the source of truth? If SAP, AMOS, TRAX, Maximo, or another ERP/CMMS holds your part master, work orders, and condition codes, the visibility layer must feed into it. Not alongside it. Building a parallel inventory ledger guarantees conflict.

Once those three questions have honest answers, the technology choice follows naturally. Without them, you’re choosing hardware for problems you haven’t measured.

Picking the Right Technology (or Mix of Technologies)

There is no universal “best” tracking technology for MRO. The right answer depends on what you’re tracking, how precise the location needs to be, and what the physical environment does to radio signals.

A nuance that vendor demos tend to gloss over: “real-time” does not mean the same thing across these technologies. Passive RFID tells you where something was at the last read event. It does not continuously confirm the item is still there. UWB can calculate position updates every few seconds, but only within the coverage of installed anchors. NIST’s research on indoor localization documents how walls, metal structures, and multipath signals degrade positioning accuracy. MRO hangars are among the worst environments for RF: steel frames, aluminum skins, heavy equipment constantly in motion.

Most MRO facilities end up with a hybrid. Barcodes on documents and low-value items. Passive RFID at tool-room gates and storeroom portals. BLE or cellular trackers on ground-support equipment that moves between hangars or across the ramp. UWB only where search-time savings on high-value shared equipment justify the infrastructure.

The engineering question to settle before purchasing: is knowing the correct room or tool crib enough, or must a technician locate the asset at a specific bay? That distinction determines your entire hardware budget.

A Six-Layer Implementation Framework

Based on deployments I’ve watched succeed (and fail), asset visibility in MRO facilities breaks down into six layers. Skip one, and every layer above it becomes unreliable.

Layer 1: Clean your master data

Separate serialized rotable parts from consumables, calibrated tools, customer-owned items, and loaned equipment. Reconcile part-number aliases. Confirm ownership and condition codes in your ERP. If an item is quarantined, the system must not silently make it available for a work order. This isn’t glamorous work. It’s the foundation everything else depends on.

Layer 2: Assign durable identifiers

Match the identifier (label, tag, or tracking device) to the asset’s substrate, exposure to chemicals, temperature range, required read distance, and expected useful life. A tag on a storeroom tote is a different engineering decision than one installed on an aircraft component. For components installed on aircraft, FAA AC 20-162B addresses airworthiness approval for RFID tags and sensors. For tools and ground equipment, the bar is lower, but durability in a hangar environment still matters.

Layer 3: Instrument every custody change

Receiving. Quality inspection. Quarantine. Stocking. Picking. Kitting. Checkout to technician. Installation. Removal. Return to bench. Shipment to vendor. Each is a custody-change event. Use handheld scans where a person must confirm identity or condition. Use fixed readers (portal antennas, gate readers) where predictable traffic makes automation worthwhile. Every event needs a timestamp, reader location, user ID, and an exception queue for contradictory or missing reads.

Layer 4: Connect to your maintenance system

Physical events (tag reads, scans, location updates) must connect to reservations, maintenance tasks, purchasing, calibration schedules, and document repositories. Sichuan Airlines’ RFID deployment integrated reads directly with SAP transactions, eliminating the manual transcription that created discrepancies. If your MRO runs on AMOS or TRAX, the connector logic differs but the principle is identical: one source of truth, not two competing ledgers.

Layer 5: Test failure modes and security

What happens when the RFID system goes offline during a shift change? FAA guidance explicitly calls for fallback to legacy methods when an RFID-dependent process is unavailable. Plan offline queues, verified reconciliation after outages, and access controls. Connected devices in a maintenance hangar are also attack surfaces. NIST’s 8259 series provides baseline cybersecurity capabilities for IoT devices that apply directly here.

Layer 6: Pilot, measure, then scale

Choose one constrained area: a tool crib, a receiving dock, one storeroom section. Count assets. Establish baseline search times. Run the pilot with actual tools, actual shelving, actual traffic patterns, actual shifts. Measure read accuracy on metal shelves, inside cabinets, at doorways during peak movement. Then compare the reduction in searching, counting, and expediting against the full cost of tags, readers, software, integration, battery replacements, and training. Scale only after the numbers hold in your facility’s real conditions.

Real Facilities, Measured Results

Three deployments illustrate different entry points and outcomes. All three are supplier-reported results, not independent audits. They’re useful as directional evidence, not universal benchmarks.

Sichuan Airlines deployed RFID across 60,000 MRO parts and consumables, using on-metal labels, handheld and fixed readers, and SAP integration. Cycle counts dropped from two people working up to eight hours to one person finishing in two to three hours. A full physical inventory fell from as many as 80 days with five or six workers to two weeks. The mechanism wasn’t faster reading alone. It was that read events entered SAP directly, eliminating the manual transcription layer.

Holt Cat managed tens of thousands of tools across 16 Texas service facilities, with individual items valued up to $18,000. Roughly 90% of tools and shelving were metal, making RFID read performance a serious question mark. The team tested tags and reader configurations on-site rather than trusting lab specs. At the Irving facility, the $76,000 initial investment was recovered in under eight months. A later San Antonio deployment reportedly hit payback in four months. The key was automatic checkout that established which technician had which tool, cutting manual tool-room labor and improving equipment sharing.

Lufthansa Technik took a different approach entirely. Instead of tagging every component immediately, the team started by putting RFID labels on the paperwork traveling with removed aircraft parts. Each scan reduced repeated manual data entry as items moved through the repair pipeline. The stated goal was getting removed components to a repair shop within 24 hours. Worth noting: the reported account presents that as a target, not a measured achievement. Pragmatic starting points beat ambitious ones that stall.

The thread connecting all three: value came not from tags alone but from connecting tag events to an existing work or inventory system. Tags without integration produce a faster list of unresolved discrepancies, not actionable visibility.

The Regulatory Layer You Cannot Shortcut

In aviation MRO, digitizing asset visibility runs into a regulatory framework that doesn’t bend for convenience.

FAA AC 119-2A governs operational use of RFID on aircraft. The guidance is clear: an RFID scan alone does not constitute a maintenance signoff. An RFID-enabled process used to accomplish a maintenance task must provide accountability, including evidence of who performed it, when, and the outcome. You cannot replace a required signature with a tag read unless the entire process meets the advisory circular’s requirements.

AC 43-9D, updated April 2026, addresses electronic maintenance records. Scanned records can be made searchable and secure, but the operator remains responsible for ensuring all required information (including signatures) is present and complete. Digitization makes records more accessible, not less rigorous.

Then there’s the provenance gap. In 2025, the UK Serious Fraud Office secured a conviction against AOG Technics for selling aircraft engine parts with falsified documentation. The parts had origin stories that looked legitimate on paper but were entirely fabricated. No RFID system or asset-tracking dashboard would have caught this. A tag can tell you where a part is. It cannot verify that the release certificate traveling with it is genuine.

The practical takeaway: keep location events, maintenance signoffs, and provenance verification as distinct but linked controls. A system that conflates “we can see it on the map” with “it’s authorized for use” is a liability, not an asset.

Why Technician Buy-In Decides Everything

This is the part most implementation guides skip, and it determines whether a deployment succeeds or quietly dies within 18 months.

Technicians don’t resist technology. They resist technology that adds steps without reducing work. And they’re wary of anything that feels like surveillance dressed up as “efficiency.”

Here’s what works in practice:

• Start with the pain they already feel. Every A&P mechanic hates walking across the hangar for a tool that should be in the crib but isn’t. Frame the system as “less walking, less searching, less paperwork.” Not “management wants to know where you are.”
• Give technicians access to the dashboard. If only managers see the asset map, it reads as surveillance. If the tech on the floor can pull up a phone and locate the torque wrench in 10 seconds, it’s a tool they’ll actually use. The difference is who benefits from the visibility.
• Don’t track people through their tools. FAA guidance cautions against placing technicians’ personal information on RFID tags. Beyond compliance, this is a cultural signal: the system tracks assets, not individuals.
• Pilot in the tool room. It’s the highest-frustration, lowest-political-risk area in any hangar. When technicians see the tool room actually work better, they’ll ask when the storeroom gets upgraded. That pull is worth more than any top-down mandate.

Change management is not a line item on the project plan. It’s the majority of the project. A technically flawless system that technicians route around is an expensive decoration.

Digitizing asset visibility in an MRO facility is not a technology project with a go-live date. It’s an operational capability you build in layers, prove in pilots, and expand based on measured results. The facilities that get this right don’t start with the most advanced hardware. They start with the most expensive unanswered question, instrument the handoffs that cause uncertainty, and connect physical events to their maintenance systems.

If your tools and parts become invisible the moment they leave the storeroom shelf, that’s the gap asset tracking closes. We help MRO operations select and deploy the right tracking hardware for their specific environment, from DO-160-approved airfreight trackers to rugged cellular devices for ground-support equipment. If you’re ready to move past the blinking-dots demo, talk to our team.

Frequently Asked Questions

What should we digitize first in an MRO facility?

Start with whatever costs you the most time or money to find. For most facilities, that’s calibrated tools (high search time, FOD risk) or serialized rotable parts (high value, compliance stakes). Measure your current search and count times before buying any hardware. The baseline determines whether the project pays for itself.

Is RFID better than barcoding for MRO?

Not categorically. Barcodes work well for documents, bin labels, and items scanned during a deliberate step. Passive RFID excels at bulk reads (tool-room gates, cycle counts) and items that need identification without direct line of sight. Most MRO facilities benefit from both technologies working together.

Does an RFID scan count as an FAA maintenance signoff?

Not automatically. FAA AC 119-2A requires that an RFID-enabled maintenance process provide accountability: evidence of who performed the task, when, and the outcome. A scan alone is not a substitute for a required signature. The specifics depend on the operator’s approved maintenance program.

How should we calculate ROI for an asset visibility project?

Document your baseline: hours spent searching, cycle-count labor, stockout events, tool losses, expedite costs, and delays traceable to missing verified-serviceable items. Run a pilot and measure the actual reduction. Then subtract the full lifecycle cost of tags, readers, software, integration, battery replacements, and training. Holt Cat’s reported eight-month payback is directional evidence, not a guarantee.

Do we need a real-time location system in the hangar?

Only when the cost of finding an asset between transactions justifies the infrastructure: tags, batteries, anchors, coverage design, and ongoing maintenance. For parts moving through well-defined gates, an RFID portal read or barcode scan may establish sufficient last-known custody at a fraction of the cost.

How do we prevent inaccurate data on the dashboard?

Reconcile system events with physical counts regularly. Display “last confirmed” timestamps rather than implying current position. Flag quarantine and uncertain statuses visibly. Retain a manual fallback procedure for outages. Review exceptions weekly: duplicate IDs, out-of-sequence movements, unreadable tags, and incomplete release documents.