Search

KR-20260063582-A - SYSTEM FOR EQUIPMENT MANAGEMENT AND METHOD THEREOF

KR20260063582AKR 20260063582 AKR20260063582 AKR 20260063582AKR-20260063582-A

Abstract

A system according to one embodiment may include an interface for obtaining basic information including operation history information and maintenance depot entry/exit history information of equipment to be maintained, and a server for calculating operation time information of equipment to be maintained based on operation history information and generating a preventive maintenance schedule for equipment to be maintained based on the calculated operation time information and maintenance depot entry/exit history information.

Inventors

  • 이양지
  • 김용현

Assignees

  • 에이치디한국조선해양 주식회사
  • 에이치디현대중공업 주식회사
  • 에이치디현대삼호 주식회사

Dates

Publication Date
20260507
Application Date
20241030

Claims (9)

  1. An interface for obtaining basic information including operation history information and maintenance depot entry/exit history information of equipment subject to maintenance; and Based on the above operation history information, the operation time information of the above maintenance target equipment is calculated, and the calculated operation time information and An equipment management system comprising a server that generates a preventive maintenance schedule for the equipment subject to maintenance based on the above maintenance depot entry and exit history information.
  2. In paragraph 1, The above interface is, An equipment management system that obtains information on the entry and exit history of the equipment subject to maintenance from an RFID (Radio-Frequency Identification) reader installed in the maintenance depot.
  3. In paragraph 1, The above interface is, An equipment management system that obtains operation history information of the equipment to be maintained from an OBD (On Board Diagnostics) installed on the equipment to be maintained.
  4. In paragraph 1, The above operation history information includes engine operation information of the above maintenance target equipment, and The above server is, An equipment management system that calculates the operating time information by summing the time the engine was operated from the engine operation information.
  5. In paragraph 1, The above maintenance depot entry and exit history information includes information on the last maintenance depot exit time of the above maintenance target equipment, and The above server is, An equipment management system that generates a new preventive maintenance schedule when the operating time from the time of the last maintenance depot departure exceeds a preset first time or fails to exceed a preset second time.
  6. In paragraph 1, The above server is, An equipment management system that further generates the above preventive maintenance schedule for unit parts constituting the above maintenance target equipment.
  7. In paragraph 1, The above interface is, An equipment management system that provides display information, including the above preventive maintenance schedule, to a user's display device.
  8. In Paragraph 7, The above-mentioned display information further includes one or more of maintenance item information or previous maintenance date information, in an equipment management system.
  9. In Paragraph 7, The above display information further includes alarm information, and An equipment management system comprising one or more of the above alarm information, such that the alarm information includes a first alarm information indicating that it is the day of the above preventive maintenance schedule, a second alarm information indicating a change in the above preventive maintenance schedule, or a third alarm information requesting the immediate entry of the above maintenance target equipment into the above maintenance depot.

Description

System for Equipment Management and Method Thereof The embodiments disclosed in this document relate to an equipment management system and a method thereof. Heavy equipment used to transport various structures at work sites is managed through preventive and reactive maintenance. Preventive maintenance is mandatory maintenance carried out on designated dates based on established periodic schedules. Reactive maintenance is performed on equipment that has broken down. Heavy equipment brought into the maintenance depot for repair is inspected and repaired by technicians, and once the maintenance is completed, the equipment is released from the depot. Traditionally, the records of heavy equipment entering and leaving the maintenance depot were managed manually, leading to frequent errors and causing disruptions in the formulation of future maintenance plans due to poor management of these records. Meanwhile, although heavy equipment undergoes preventive maintenance at regular intervals, the conventional method of establishing such preventive maintenance schedules does not reflect the actual operating time of the heavy equipment. There was a problem in that heavy equipment that had not been operated at all was serviced again simply because a certain period had been reached, resulting in an excessive waste of time and money. FIG. 1 is a block diagram showing the configuration of an equipment management system according to one embodiment disclosed in this document. FIG. 2a is a drawing showing display information displayed on a user's display device according to one embodiment disclosed in this document. FIG. 2b is a drawing showing first alarm information displayed on a user's display device on the day of a preventive maintenance schedule according to one embodiment disclosed in this document. FIG. 2c is a drawing showing second alarm information displayed on a user's display device when a preventive maintenance schedule is changed according to one embodiment disclosed in this document. FIG. 2d is a drawing showing third alarm information displayed on a user's display device when a failure occurs in equipment subject to maintenance according to one embodiment disclosed in this document and immediate receipt is requested. FIG. 3 is a flowchart showing an equipment management method according to one embodiment disclosed in this document. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Some embodiments disclosed in this document are described in detail below with reference to exemplary drawings. It should be noted that in assigning reference numerals to the components of each drawing, the same components are given the same reference numeral whenever possible, even if they are shown in different drawings. Furthermore, in describing the embodiments disclosed in this document, detailed descriptions of related known configurations or functions are omitted if it is determined that such detailed descriptions would hinder understanding of the embodiments disclosed in this document. In particular, various embodiments of this document are described with reference to the accompanying drawings. However, this is not intended to limit the technology described in this document to specific embodiments, and it should be understood that it includes various modifications, equivalents, and/or alternatives to the embodiments of this document. In relation to the description of the drawings, similar reference numerals may be used for similar components. In describing the components of the embodiments disclosed in this document, terms such as first, second, A, B, (a), (b), etc., may be used. These terms are used merely to distinguish the components from other components and do not limit the nature, order, or sequence of the components. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the embodiments disclosed in this document pertain. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this application. For example, expressions such as “first,” “second,” “first,” or “second” used in this document may modify various components regardless of order and/or importance, and are used merely to distinguish one component from another and do not limit the components. For example, the first user device and the second user device may represent different user devices regardless of order or importance. For example, without departing from the scope of rights set forth in this document, the first component may be named the second component, and similarly, the second component may be renamed the first component. In this docum