Guest contribution: Communication is key – we have to talk to each other and we have to document our activities!
En 13306: Communication is crucial for maintenance workers. One of the most important exercises is the documentation of our activities. A transparent delivery of all maintenance tasks helps all parties involved to understand exactly what has happened and what needs to be done.
This means that the fault reports documented in our maintenance software need to sweat details in order to achieve sustainable results and improve our work.
As the information we gather needs to be useful for evaluations, it is important to establish a standardized communication for maintenance. This includes standardized error catalogues and categories and fault descriptions, an organizational manual and functional descriptions. Consistent documentation of maintenance activities will enable us to quickly spot recurring problems and possibly even eliminate them in the long run.
Author: Peter Mainka (Source)
Maintenance according to EN 13306
EN 13306 is a standard that specifies the terminology for maintenance. It is important to understand that this is not a guide to a maintenance organization`s set up.
It is the definition of maintenance vocabulary for consistent and organization wide utilization, meaning there are no normative principles set by the standard, but a glossary of definitions that are helpful in the organisation of maintenance and maintenance planning.
It is universal maintenance lingo.
This lingo is particularly important for the structure of our maintenance organization as it will serve as a directory for all terminology concerning objects, properties of objects, failures and events, errors and conditions, types of maintenance and terminology associated with the time-tracking of various maintenance-related activities. This will help to spotlight weaknesses in the company’s own maintenance department by providing various ways of reporting and time tracking.
When measuring downtime and analyzing administrative or logistical delays, a versatile maintenance software is almost inevitable. MaintMaster works out-of-the-box with a database based on the EN 13306. This means that your object types, their order categories and much more are directly marked according to the standard. Hence, you can easily create statistics for time-tracking as defined in the EN 13306.
Of course, the structure of the database can be adapted to your needs so that it’s a perfect fit with your business.
For example, the database distinguishes directly between corrective, preventive and improvement-related maintenance. When creating a new task, the same principle applies – this makes it easier to get statistics about your type of activities later on.
All object categories are also named in accordance with the standard and have associated properties that are relevant to the respective category.
These properties, and their inherit fields and containing values are by default part of a fresh setup of MaintMaster as well. Of course, they can be deleted, deactivated or supplemented with other fields if need be. Data entered in these custom fields is therefore also statistically evaluable.
MaintMaster is a very easy-to-use tool that can be adopted and configured to a variety of purposes, but it should always be clear that MaintMaster is a communication tool in its essence.
MaintMasters purpose is for Maintenance staff and other departments (especially production) to communicate with each other in the most optimal way. It enables them to store and access information in a way that is easy and accessible. The introduction of our new database structure, which in turn is aligned with the maintenance standard, ensures that everyone working with the system uses the same terminology even across companies. This is where we see the true value of good communication.