- 05 Jun 2020
- Brian Wells
- Aircraft MRO
Assuming you have completed the maintenance debrief, expectations have been delivered, ground rules laid out, and clear guidance given for what you anticipate will be a seamless maintenance event on your business aircraft.
The manpower requirements are understood, and now it’s full steam ahead. Although you are unable to maintain on-site representation for the four-week event, a clear and crisp communication process has been established with your point of contact for defect approvals and cost estimates.
At this point, you are confident nothing unexpected will come up…
Great commotion or agitation.
The reality is that there’s no single tried and true method to remotely monitor and manage a maintenance event. Many variables can come into play.
Do you have a long-standing relationship with your chosen MRO? If that is the case, you may have already established a trusted internal contact network and information needs are understood. The following article will depict a scenario where you work with your chosen MRO provider for the first time…
MRO Work-in-Progress Reports
A bi-weekly progress report for larger maintenance, repair and overhaul projects should normally suffice. This will provide a clear indicator for tracking financials and job progression. However, as the paying client, if you deem it appropriate to receive daily updates, you have the right to ask for it.
This is your maintenance event and the financials can swing greatly, even over the course of a day. No amount of information is too much information.
Work-in-Progress (WIP) reports come in many different formats from vendors, and they may include milestone charts, spreadsheets, and PDFs to name a few. Regardless of the format, each report will normally paint the same overall picture and present the key performance indicators outlined below.
Overall Job Progression
The WIP report will include an estimated value or ratio of completed tasks versus work remaining. Red flags should arise if, after week one of this four-week event, the value is less than 25%. A higher value is obviously preferable as history shows it can be problematic to make up time later.
Trending below the expected project completion percentage to meet your out date should trigger the following additional questions:
It should be noted that you, the operator, bear responsibility for providing timely feedback to the MRO. Late responses will have a cause and effect. Accordingly, you should request that any larger defects (e.g., over $2,500) are presented with cost estimates or flat rates and a percentage of task completion, if already started.
Viewing defect trends is similar to the overall job progression process. If you have been quoted $10,000 in labor for a defect and currently sit at $3,000, then your expectation should be that the defect is 30% complete. Anything less than that should raise a red flag and prompt an immediate question to the MRO.
Other considerations for defect approval include the following:
Stay consistent in your communications with the MRO until project completion. A lapse on either end can, and often will, cause delays that carry a financial impact. Request all labor estimates and parts quotes in writing, and create a file and cache all communications related to the event. The odds are that on larger projects you will revert back to that file on many occasions.
More information from www.jetsupport.com