Safety reporting metrics are among the best indicators to judge the performance of any aviation safety management system (SMS). This is such a very powerfully poignant statement. Let that sink in:
"Safety reporting metrics are among the best indicators to judge the performance of any aviation safety management system (SMS)."
When an inspector or an SMS consultant reviews your safety reporting numbers, they can draw some amazing inferences, including:
For most immature SMS implementations, safety goals, and objectives almost always target safety reporting numbers. Similarly, many immature SMS implementations store reported safety issues in spreadsheets. Spreadsheets can't communicate the status of organizational safety goals in real time. Furthermore, spreadsheets have inherent security considerations that reduce their utility in a larger organization.
Sure, spreadsheets have their uses. However, storing safety report data should be reserved for a database and not a spreadsheet unless you are in a very small company and you are not under EASA jurisdiction.
An SMS database can securely store and retrieve data to display to a wider audience, which can then securely monitor organizational safety goals and objectives. An SMS database powers safety charts in real time and can display data based on the user's permissions.
In this article, we discuss a small safety chart that allows the accountable executive and upper management to monitor safety reporting numbers. This chart is important to the accountable executive.
For every SMS implementation, the accountable executive is responsible for ensuring the SMS is working properly across the entire organization. A chart, such as the one to the right, provides managers with a quick glimpse as to whether sufficient safety reporting activity is occurring. If not, the accountable executive should be asking
Take a look at the chart on the right. What can you see? Are these good numbers? It depends on:
The aviation safety chart “# Reported Issues” is a great measure of how active an aviation SMS safety reporting culture is for the current month or year. With a dashboard chart similar to the one above, aviation safety management teams can quickly see the total number of reported issues within a selected month or another time period.
The chart from this article comes from an aviation SMS database's dashboard. This chart is one of approximately 45 other dashboard charts that can be configured in SMS Pro. The purpose of the article is not to showcase this particular chart or SMS Pro, but to explain how it works. If you have another SMS database, you can build a similar chart. If you are an SMS Pro user, this article explains the purpose of this dashboard chart.
If done properly, a chart designed like the one above can evaluate the current period with another similarly sized period. If you are building a similar chart, you may wish to include other time periods instead of simply the month or year, as displayed in this safety chart.
Other time periods can be used to display the sum of reported safety issues, such as:
As one can easily anticipate, these reported safety issues originate from aviation service providers' safety reporting systems. Such information gives aviation safety management teams the ability to set benchmarks for how many reported issues to expect and set safety goals within a given time period.
Safety managers benefit by comparing the reported number of issues vs goals within that time period and see if the reporting trend in that time period is helping or hurting the overall yearly reporting goals.
Let's take an example of an airline with 500 employees. In our example, we are now approaching the end of the month and have had 36 reported safety issues. The most our company has ever reported within a given month is 52 safety concerns.
For this airline, I can surmise that this company has a healthy reporting culture; however, this month's numbers are low. What is a healthy reporting culture? A good rule of thumb is that for every 100 employees, a healthy reporting culture will have ten reports per month. In the example above, 50 reports is a very good month of safety reporting. 36 reports may be an anomaly that we cannot explain until we have additional information.
In the case above, this "number of reported issues chart" sets the highest dial number as the maximum number of reported issues within a selected time period. In our example, we can see that the upper limit of the dial is set to 52, as 52 was the previous maximum number of safety issues reported within a single month.
Representing data this way reveals several things about an aviation SMS' performance:
Tracking where this dial consistently is allows emerging aviation SMS to see how well they are achieving their safety goal of continuous improvement. In the same vein, mature SMS can monitor the ongoing consistency of their reporting culture and take necessary actions whenever substandard safety reporting numbers appear.
The most important negative display safety management teams would remain alert for is reporting numbers that fall far below the maximum number for any selected period. Such a display should raise some rather important questions from senior management, like:
Of course, sometimes there may be good answers for changes or decreased numbers, but regardless, it warrants further investigation.
Safety managers must also be alert for other anomalies. Data may be skewed due to events, such as:
This data, which is stored in an aviation safety database program, will always be filtered by the number of reported safety issues whose reported date falls within the user-specified time period (start date and end date). The aviation SMS software will automatically display the number based on the user's selected configuration.
For manual aviation SMS data management strategies, such as those stored in an Excel spreadsheet, managers will simply have to tediously sort and file the reported issue numbers and the highest number of reported issues in that time period. Of course, the report will not be in real-time, which is the advantage of using a professional aviation safety database program.
One of the primary responsibilities that aviation SMS oversight agencies put on service providers and carriers is that they demonstrate continuous improvement. Senior management and the safety team must regularly review organizational safety performance in order to monitor performance. Management can then determine whether there is any indication of improvement. When there is no indication of SMS improvement, the accountable executive must direct actions necessary to address the substandard safety performance.
A central piece of demonstrating continuous improvement lies with reporting numbers. Showing the following charted data for hazard reporting fulfills this responsibility:
It’s this kind of data that becomes the most powerful tool for safety managers to demonstrate SMS effectiveness to:
Without a doubt, this is the kind of data that auditors love to see. Safety reporting numbers indicate whether the company is monitoring operations and remains vigilant for manifesting hazards. The lack of good safety reporting numbers requires that management develop a plan to address the substandard safety reporting activities. What should you look at? I'd focus initially on:
The number of reported safety issues is something that concerns all process owners and senior managers within the company. After all, SMS involves the entire company and not just the safety team. Therefore, the affected parties are common:
The number of reported safety issues is a direct reflection of safety reporting culture – and culture is something that happens at an organization-wide level. If an SMS performance isn't reaching a targeted benchmark, then everyone needs to be aware of how he or she can improve the safety reporting culture. If reporting numbers are good, then everyone should be encouraged to keep up the good work.
Aviation SMS dashboard charts can display complex ideas using a single chart. Dashboards typically have many related charts to display. One chart by itself may not provide a complete picture of the SMS' performance. Complementary charts help managers see the bigger picture. In SMS Pro, for example, users can drag and drop multiple charts on the screen to create a story that is more representative of SMS activity.
Another aviation safety chart that pairs well with this article's highlighted chart would be an "Issue Comparison By Month" chart or another similar chart that compares the current time period to the previous time period. From the chart at the right, we can see hazard reporting metrics for the current month super-imposed over the previous month's safety reporting activity.
Complementary charts, such as the one at the right, display more specific, incremental representations of reported issue activity.
SMS Pro has several other SMS performance monitoring charts to help safety teams and accountable executives keep on top of the SMS. To learn more about these charts, please watch these short demo videos.
If your SMS needs help to monitor performance, we can help. Sign up for a live SMS Pro demo.
Last updated in October 2024.