|
 |
 |
 |
 |
|


|
|
 |
 |
 |
Whether part of aviation MRO or other critical component maintenance programs, parts maintenance and repair
are crucial to ensuring the proper function of complex vehicles, equipment and machinery. Airline and other
major vehicle parts and components undergo constant wear and tear during operations and require detailed
routine maintenance. The tools themselves, which are used to maintain such parts and components, also need
proper servicing.
To ensure optimal function and safety of critical parts and components, accurate and timely tracking of
component lifecycle and maintenance history is vital to any maintenance and repair operation. However,
the tracking and record keeping of each component can be a challenge particularly when it is shared or
distributed across a supply chain. Hence the need for a maintenance and repair tracking system that can live with the
component, no matter where it is, is critical.
|
|
|
In order to properly service vehicles and components, companies need information about individual parts
such as the hours in use, maintenance history and inspection data. Collecting and logging this data for
each part can be manually intensive, error prone and paper-based. In situations where parts are maintained by
multiple parties and potentially in different locations, the need for readily accessible maintenance history
may make it necessary to keep the information with the part.
Some components are made up of other parts. Keeping an accurate manifest of component parts that make up
a more complex system ensures proper servicing and function.
Key components require that its birth record is readily accessible to ensure authenticity and for traceability,
as in the case of recalls. Having the right information with the part also helps in lifecycle management so that you
know if the part is near the end of its life, and therefore a replacement is needed.
Aviation MRO
Automotive
Heavy Machinery
Watercraft
Extended memory passive and battery-assisted passive RFID technology enable tracking solutions in the aviation industry.
With the FAA approval of the use of passive UHF RFID tags on individual airplane parts for commercial aircraft, it opened up a
number of potential RFID-based applications for airlines, air-freight carriers, aircraft maintenance and repair centers,
and airplane manufacturers. It is particularly important for airline parts maintenance tracking. Extended-memory passive
and battery-assisted passive RFID maintenance and repair technologies from Intelleflex have proven to be particularly
useful for their unique combination of the best features of passive (low cost) and active (high performance) RFID
solutions.
Shortly after the FAA approved the use of passive UHF RFID tags on individual airplane parts, Boeing announced plans to
incorporate RFID tags on high dollar value items, line replaceable units (LRUs), limited life parts that need to be
frequently inspected, repaired and replaced and on-board emergency equipment. Boeing selected the Intelleflex extended memory C1G2
chip for maintenance and repair management solutions.
In addition to storing unique identification on the RFID tag, Boeing will store flight time, maintenance and inspection
data. Logging a part's flight hours, maintenance and repair histories directly on the RFID tag will reduce the airlines'
costs of tracking and maintaining service history on parts. Using RFID for maintenance and repair will also reduce the
cycle time to solve in-service problems by improving the accuracy of information exchanged between customers and suppliers. Giving mechanics the ability to reference and update a part's maintenance history will more quickly and easily facilitate
accurate configuration control and repair history, reduced warranty claim processing costs, accurate and efficient spare
parts pooling and easier identification of rogue parts. Storing electronic maintenance records on the RFID maintenance and
repair tags will also reduce airlines' reliance on paper records and ease future compliance with FAA documentation
requirements.
|
|
|
| |
|