In day to day operations, aviation service providers experience any number of occurrences that need to be logged, but not necessarily managed as a safety concern. These types of non-safety occurrences are important for:
Examples of non-safety occurrences that should be logged are things like:
The last bullet point is important. Everything occurrence doesn’t need to be logged, but an irregularity that is noticeable enough that the officer on duty should be aware of it is an occurrence that should be documented.
The Duty Officer Log module is useful in this regard for:
Duty Officer Log Important for QSMS
You might be wondering, “How are non-safety occurrences relevant to SMS?”
There are a couple of answers to this question. The first answer is that unmanaged irregularities can quickly become safety issues.
For example, consider the following situation:
The second answer is that the Duty Officer Module, like the Security Checklist Manager, is a great tool for quality management and safety management. This kind of module bridges the gap between QMS and SMS, and allows your personal to practice both activities at the same time, i.e. quality-safety management system.
For example, consider the same example as above with lone baggage:
There are many similar situations for airport SMS programs and airline SMS programs that benefit greatly from improving QSMS operations
Occurrences and irregularities are easily logged with the Duty Officer Log module. It’s as simple as:
Once these logs are created, management can:
Used in conjunction with a module like the Security Officer Checklist, the Duty Officer Log module provides a powerful way for you to integrate QMS and SMS operations.