Basics

Basics of the QMMS system

A bit of theory

A complaint or a proposal for improvement (in general: Q-case) runs more or less always according to the same process: record case -> assign responsible person -> solve case -> close case

And this is how a tool for Q-case processing should look like: step by step you will be guided through the process of resolution, for minor Q-cases there should be a "shortcut", no huge data maintenance in the background for other quality requirements and everyone should have "fun" to work with the tool

Requrements

The requirements of such a tool can be summarized in five points:

  1. The inhibition threshold to open a quality complaint should be as low as possible
  2. There is a clear separation between opening and handling a quality complaint
  3. The system should be as open as possible so that anyone who can contribute to the resolution of the quality case can do so without cumbersome registration or similar
  4. For minor problems, there is a shortened version of the process
  5. Completion of a quality complaint should go through a formal approval process

Even though the requirements have continued to increase over time, the QMMS tool has remained faithful to these ideas


The most important features

  • Easy recording of problems / complaints with only 5 entries
  • Add files, pictures, etc in unlimited numbers
  • Defined problem-solving team
  • Problem analysis and solution based on the 8D structure
  • Automatic reminders of tasks
  • Clear and simple role model
  • Comprehensive reports
  • Multilingualism
  • …and much more