The task of the canias ERP Maintenance (MNT) module is to ensure that facilities and technical systems operate with target functional sufficiency or to reactivate them when they are out of service.
Maintenance Management (MNT) with canias ERP
The canias ERP Maintenance (MNT) module in addition to preventing system interruptions and extending machine operating times, the module allows maintenance work to be carried out efficiently, secures workflows and contributes to the improvement of occupational safety. The graphic describes the location of the Maintenance (MNT) module in the general system and its connections with other function fields.
In periodic or regular maintenance, scheduled and preventive maintenance efforts are used to protect functional integrity of technical systems.
Systems and devices that are currently used to carry out proper maintenance work must be created as maintenance objects in the ERP system. For this reason, maintenance methods are defined for each maintenance object and necessary work steps are defined in the canias ERP Routes and Work Center Management module. In addition, machine type (e.g. packing unit) and periodic maintenance interval (e.g. weekly, monthly or annually) is entered in the canias ERP Basic Core Data module, whereas the serial number of the system is entered in the canias ERP Maintenance (MNT) module. These entries enable users to create maintenance plans according to data defined in the system for each serial number. The planning operation can be performed by a user or automatically at regular intervals.
The planning process is carried out automatically according to type and interval of periodic check and each is recorded as a maintenance plan. Maintenance plans can be followed up under the Maintenance Module.
If the user wants to apply the created maintenance plans, he may approve the relevant maintenance plan and convert them to maintenance orders. The created maintenance orders are followed up and applied with the Maintenance (MNT) module application. If the relevant maintenance plans are not approved, the necessary maintenance work is re-proposed in the next planning process.
Repair in Case of Breakdown
In case of repairs after breakdowns, onetime temporary breakdown messages and short-term repair works to recover a technical functionality are recorded in the system.
In the event of unexpected downtimes, general substitute systems must be activated; this may require overtime work and thus increase costs. For this reason, the company must be quick to react to such non-periodic maintenance.
For example, when a breakdown is reported by telephone, the breakdown must be recorded in the system immediately. From the breakdown message created, a maintenance order is created on the basis of recorded general information in relation to the maintenance of that system. After the order is created, information is obtained about the time period and spare parts needed for maintenance.
After a maintenance order is realized (independently of periodic maintenance or unforeseen breakdown), a confirmation is given to the canias ERP Maintenance module for the measure applied. The system for which the measure is applied, the time when it is applied and any spare parts used are thus recorded in the system.
Supply of Spare Parts
All spare parts that may be considered for a system are recorded in the canias ERP Bill of Materials module. The components used are automatically excluded from inventory at the time of approval through canias ERP Inventory Management module. It is also possible to exclude the parts from the usable inventory manually.
Missing spare parts in relation to a maintenance/ repair order have to be supplied. Therefore, an automatic or manual purchase transaction is started in the canias ERP Purchase module. When ordered parts are delivered, these are recorded as receipt of goods and thus as usable stock in the canias ERP Inventory module and can be used for necessary maintenance.