2009 SMS Pilot Project (SMSPP) Analysis - FAA
2009 SMS Pilot Project (SMSPP) Analysis - FAA
2009 SMS Pilot Project (SMSPP) Analysis - FAA
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
• Core <strong>SMS</strong> Orientation Presenters - The M<strong>SMS</strong> team learned that having only a few<br />
well versed and knowledgeable presenters to give the <strong>SMS</strong> orientation sessions was more<br />
effective. The few presenters learned from each orientation session and were able to<br />
better answer questions and give examples at the subsequent sessions. The presenters<br />
increased knowledge and proficiency was evident during subsequent orientation sessions.<br />
• Gap <strong>Analysis</strong> Facilitator - Having one “gap analysis expert” explain the GAT and<br />
walk the participant through the steps of a PGA was the most successful. Having an<br />
inexperienced person do it was slow and very ineffective.<br />
• Early <strong>SMS</strong> <strong>Pilot</strong> <strong>Project</strong> Engagement – Launching the <strong>SMS</strong> pilot project for all<br />
participants early in pilot within 4 months vs 16 months would have yielded better data<br />
collection with little effect on field resources. The momentum was drastically slow from<br />
launching one participant every other month and there was incredibly little effect on<br />
office resources. The end result of this slow launch was that the team did not receive the<br />
expected <strong>SMS</strong> data. The <strong>FAA</strong> could have supported a much quicker launch sequence and<br />
the pilot project participants may have progressed into level 3 of maturity. The<br />
Participant Management Team would have had a greater learning experience and been<br />
utilized better with a more rapid launch. The M<strong>SMS</strong> team did not need field support early<br />
in the pilot project because there were no activity for them until the DGA meeting.<br />
• “ICAO <strong>SMS</strong>” Training – Having pilot project participants take a course in ICAO <strong>SMS</strong><br />
would have been beneficial as would have accelerated the gap analysis meeting<br />
discussions. There was a lot of coaching and mentoring by the M<strong>SMS</strong> team to get the<br />
pilot project participants up to speed. Most of the POCs were knowledgeable on <strong>SMS</strong> but<br />
the rest of the pilot project participants’ internal <strong>SMS</strong> team was not.<br />
9-0 M<strong>SMS</strong> Team Recommendations for Rules, Policies, and<br />
Guidance<br />
The recommendations of the M<strong>SMS</strong> team are as follows:<br />
1. An <strong>FAA</strong>-issued <strong>SMS</strong> rule should be applicable to design and manufacturers, defined as<br />
organizations responsible for type design and/or the manufacturing of aircraft. This<br />
proposed scope for the <strong>SMS</strong> rule is directly in line with current ICAO requirements.<br />
2. Conduct oversight of an organization instead of conducting specific <strong>SMS</strong> oversight. To<br />
clarify, the <strong>FAA</strong>’s oversight of an organization’s <strong>SMS</strong> would be in conjunction with any<br />
other management system requirements (e.g., QMS). The oversight method should use<br />
performance-based processes for the <strong>SMS</strong>. Separate audits may be used for compliance<br />
of quality systems, repair stations, etc.<br />
3. Use the D&M <strong>SMS</strong> <strong>Pilot</strong> <strong>Project</strong> Guide as the baseline for an <strong>FAA</strong> Order. This guide<br />
provides (1) general information to the D&M industry on how to begin developing and<br />
implementing an <strong>SMS</strong> with D&M industry and (2) guidance to <strong>FAA</strong> personnel for<br />
41