Duty Officer Log - Aviation SMS Software Modules for Airlines & Airports

My Safety Modules

What Duty Officer Log Module Is Designed For

Duty Officer Log Module

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:

  • Understanding the quality of your organizations customer service;
  • Understanding the quality of your services’ amenities; and
  • Establishing SMS relevant trends in airport operations.

Examples of non-safety occurrences that should be logged are things like:

  • A broken pipe in the bathroom;
  • A lone, unaccompanied piece of luggage;
  • A confrontation with a passenger; and
  • Any other type of irregular incident.

    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:

  • Documentation important, non-safety occurrences;
  • Listing and classifying data trends for such occurrences;
  • Describing these occurrences; and
  • Organizing all important irregularities.

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:

  • An airport does not track the number of lone baggage that forgotten/left by customers in the airport;
  • This lack of oversight could quickly become a gateway for nefarious airport activity; but
  • When management does notice a negative trend in lone baggage irregularities, they can quickly take measures to correct it and close the gateway to non-safe operations.

    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:

  • Safety management can create control measures to lone-baggage does not become a safety concern; and
  • Safety management can try to understand why lone baggage is a problem, and take measures to improve quality of operations so that this is no longer a problem.

There are many similar situations for airport SMS programs and airline SMS programs that benefit greatly from improving QSMS operations

Features of Logging Occurrences in Duty Officer Log Module

Occurrences and irregularities are easily logged with the Duty Officer Log module. It’s as simple as:

  • Giving the occurrence a title;
  • Describing the occurrence;
  • Selecting up to three classifications for the type of occurrence;
  • Choose whether or not you want to submit the occurrence as an issue in the Issue Manager module;
  • Notify any third parties if applicable; and
  • Add any attachments.

Once these logs are created, management can:

  • Review all logs and details of the log;
  • Edit any log;
  • Generate a report for each log or all logs;
  • Add comments to the log, such as status comments or notes; and
  • Organize logs by classification.

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.