JP2002091527A - Operating state management system of production equipment - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an operating state management system of production equipment capable of properly collecting, storing information regarding an operating state of production equipment and outputting total data for the purpose of analysis for enhancement of operating efficiency. SOLUTION: A production management system server 14 is provided with an operation master data base 14a in which collection information to collect the information regarding the operating state of the production equipment and information regarding an operation information collection menu picture are stored, and an operation log data base 14b storing the operation information collected via a process management system client 20. The process management system client 20 is provided with a local operation master data base 20a to be copied from the operation master data base 14a and an event data base 20b storing the operation information collected based on an operation information collection menu, and collects the operation information stored in the event data base 20b in the operation log data base 14b and creates the required piece of total data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a photographic film, etc.
Regarding the production equipment operation status management system applied in manufacturing factories that produce various industrial products, in particular, to properly collect information on the operation status of production equipment, accumulate it in a database, and analyze it to improve operation efficiency The present invention relates to a production facility operation status management system capable of outputting aggregated data.

[0002]

2. Description of the Related Art Computer processing has been performed in various fields due to the recent development of information processing apparatuses and information processing techniques, and computer systems for controlling processes and controlling production of production facilities in factories are well known.

In general, in order to improve the productivity of a production facility such as a factory, it is necessary to accurately grasp the operation status, analyze points requiring improvement, and increase the operation rate of the production facility. Is done. By the way, production equipment is stopped due to failure of the equipment, stop due to inspection work, stop due to production plan, stop due to worker break, stop due to delay in work in the previous process, stop due to delay in work setup by worker, raw material It often stops due to various factors, such as a stop due to a supply delay, which lowers the operation efficiency of production equipment.

[0004] Therefore, in order to cope with such a situation and improve the operation efficiency of the production equipment, the operation state of the production equipment, that is, the cause of the stoppage of the production equipment, the stop time, and the failure location due to the failure, It is necessary to collect information such as the cause of the failure and analyze points to be improved.

Hitherto, collection and analysis of information on the operation status of such production equipment has been mainly performed manually. That is, when the production equipment stops, the operator (operator) of the production equipment sequentially records the cause of the stop, the start time of the stop, the operation start time of the production equipment after the recovery of the stop cause, and the like on a predetermined sheet of paper, and the like. The report was submitted to the production management department as a daily report or weekly report.

[0006] The production management department classifies the causes of production equipment stoppage based on the daily report and weekly report, tabulates the frequency of occurrence and stoppage time for each stoppage cause, analyzes points to be improved, and improves the production equipment. , Production plans and so on.

By the way, when collecting information on the operation status of the production equipment, a failure of the production equipment is automatically transmitted to the production management computer by means of various sensors and warning displays provided in the production equipment. Although measures have been taken to collect failure information, there is currently no system that collects information on the causes of production equipment shutdown other than failures comprehensively without manual intervention.

[0008]

Therefore, in the above-mentioned conventional operation management of production equipment, since the operation information is mainly collected manually, the cause of the production equipment stop or the stop time is erroneously recorded or recorded. There has been a problem that information becomes inaccurate, such as leakage. In addition, since the workers in the production management department calculate the operation status and calculate the failure probability based on this record, it takes a lot of time for processing and lacks the accuracy and reliability of analysis. Existed.

SUMMARY OF THE INVENTION The present invention has been made in order to solve such a problem, and it is an object of the present invention to appropriately collect and accumulate accurate information on the operation status of a production facility in a database to improve the operation efficiency. It is an object of the present invention to provide a production equipment operation status management system capable of outputting aggregate data.

[0010]

In order to achieve the above object, a production equipment operation status management system according to the present invention comprises:
A plurality of production equipments arranged on a production line, a plurality of process control clients for controlling the production equipment, a production management server connected to the process control clients via a network, and processing production management operations, and a production management server System clients.

[0011] The production management server collects information via an operation master database which stores collected information for collecting information on the operation status of the production equipment, information on the screen of the operation information collection menu, and a process management client. An operation log database that stores the operation information that has been collected, the process management client includes a local operation master database that is copied from the operation master database, and an event database that stores the operation information that is collected based on the operation information collection menu. It has.

The process management client displays an operation information collection menu screen based on the information accumulated in the local operation master database, and the operation information input by the operator according to the operation information collection menu screen is stored in the event database. Stored.

The production management server collects the operation information accumulated in the event database of each process management client in the operation log database, and the production management client can create required aggregate data.

At this time, the collected information stored in the operation master database has a hierarchical structure for each event, and the screen of the operation information collection menu is configured based on the hierarchically collected information. Therefore, the operator can easily and accurately input the operation information simply by performing operations in accordance with the screen of the operation information collection menu that is sequentially displayed.

Further, the production equipment operation status management system according to the present invention is an operation master database that stores hierarchical collection information for collecting operation information of production equipment and information relating to an operation information collection menu screen. When,
An event database for storing the operation information; and an aggregation master database for creating aggregation data from the operation information accumulated in the event database, wherein the operation information collection is performed according to the hierarchically collected information. A menu screen can be set, the operation information can be collected based on the set screen, and total data can be created from the collected operation information.

This system is applied to production equipment having various configurations, and is capable of creating, from efficient and functionally collected operation information, aggregate data capable of accurately grasping the operation status of the production equipment.

[0017]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A production facility operation status management system according to the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a block diagram showing a schematic configuration of a production facility operation status management system 10 according to the present invention.

The production equipment operation status management system 10 according to the present invention comprises a production management server 14, a process control client 20, a production equipment 40 such as a cutting machine, and a production equipment 40 connected to a network via a network communication path 16. It is composed of a management client 30.

The production management system server 14 collects information in which information items for collecting information on the operation status of the production equipment 40 are set, and the process control system client 20.
Master database 14a (hereinafter referred to as a main master), which is a database in which input form information and the like relating to an operation information collection menu screen to be displayed on the screen are set.
And an operation log database 14b, which is a database for storing the collected operation information, a total master database 14e for totalizing the stored operation information in a desired form and creating total data, and a main operation master 14a. According to the collected information, the process control system client 20
And collects the operation information collected in the operation log database 14b, and a processing program 14c for creating total data.

When the system is started, the process control system client 20 starts the main operation master 14 of the production management system server 14.
An operation master database 20a (hereinafter, referred to as a local operation master), which is a database created by copying the contents of a, and operation information collected from the subordinate production equipment 40 in accordance with the items set in the local operation master 20a. Database 20b, which is a database to be processed, and a processing program 20c for performing the processing.
It is composed of

The production facility 40 includes a sensor 40a such as a mechanical or optical sensor for detecting the operation status of each part, and a machine for setting operating conditions and the like of the production facility 40 by a process control client 20 or an operator. Control panel 4
0b, and an information control panel 40c. The production management client 30 includes an operation log database 1 of the production management server
4b is provided, and a processing program 30a is provided for processing the required operation information from the operation log database 14b and collecting and outputting the required operation information.

The production equipment operation status management system 10 according to the present invention is configured as outlined above.
The function and operation will be described below. FIG. 2 is a diagram schematically showing the function and operation flow of the production equipment operation status management system 10.

The main operation master 14a, as described above,
In order to collect information on the operation status of the production equipment 40,
This is a database in which collection information in which information items to be collected from each production facility 40 are set, and input form information and the like relating to an operation information collection menu screen to be displayed on the process control system client 20 are set. The items, input form information, and the like have a hierarchical structure in the order of large classification, middle classification, and small classification. The main operation master 14a is copied to the local operation master 20a of the process control system client 20 when the system is started.

The process control system client 20 displays an operation information collection menu screen on the CRT 20d based on the information copied to the local operation master 20a, and the operator A operates the input device 20e according to the displayed operation information collection menu screen. Input of the operation information collection of the production equipment 40 from.

The operation information of the production equipment collected in response to the operator's input includes an event name, an event start time, an event end time, main cause information, and the like. The operation information is stored in the event database 20b, and the production management is performed at a predetermined timing. It is sent to the operation log database 14b of the system server 14.

The operator A of the production facility 40 collects information such as start, end, management stop, breakdown stop, break, setup, operation status input, etc., according to the initial screen of the operation information collection menu displayed on the CRT 20d of the process control system client 20. By selecting a classification and performing a predetermined operation and input from the input device 20e in accordance with the operation information collection menu screen hierarchically displayed in accordance with the selection result, detailed information on the operation state is created.

For example, a failure of the production facility 40
0a, the machine control panel 40b, the information control panel 4
The failed part is displayed at 0c or the like, and the process control system client 20 is notified of the failure stop. In accordance with the notification, the process control system client 20 displays an operation information collection menu screen corresponding to the failure stop on the CRT 20d. On the other hand, the operator A recognizes that the production facility 40 has stopped due to a failure, confirms a failed portion, and the like, and then creates details of the operation status according to the operation information collection menu screen. Details of the operation for each of these collection categories will be described later.

When the operator A requests the operation log to be modified, the production management person B
Of the operation log database can be referred to and corrected by the CRT 14d and the input device 14e. Also,
If necessary, the production management client 30
T30d, the operation master database 14a can be corrected by the input device 30e, and the production management server 1
Operation status data for referring to the operation information accumulated in the operation log database of No. 4, outputting various types of tabulations, lists, charts, etc., and modifying production plans and considering measures to improve the operation efficiency of production equipment. Can be provided.

FIG. 3 is a diagram showing an initial screen of the operation information collection menu. This initial screen includes a start button 1, a close button 2, a management stop button 3, a failure stop button 4, a break button 5, a setup button 6, and an operation status button 7, and is stored in the operation master database (local) 20a. This is a screen form displayed according to the tabulation classification, and is used when the production line is started up.
Is displayed on the screen of the CRT 20d. Operator A
From this initial screen, the current state of the equipment operation state is selected, and the corresponding button is operated.

The start button 1 is for recording the start of the start of the equipment, compares the latest start time and the end time of the operation log of the target production equipment 40, and can be operated when the end time is later. (High-brightness display), otherwise, operation is disabled (low-brightness display). When the start button 1 is operated, the screen shifts to a start time input screen.

The closing button 2 is for recording the closing of the facility, and can be operated when the starting button 1 is operable.
When the start button 1 is inoperable, the operation becomes inoperable. When the end button 2 is operated, the screen changes to an end time input screen.

The management stop button 3 is for recording the contents of the work at the time of the management stop, and is operable when the start button 1 is operable, and is disabled when the start button 1 is not operable. When the management stop button 3 is operated, a management stop major category item is searched from the operation master database (local) 20a, and a transition is made to a major category selection screen. During management suspension, the button name is changed to "management end".

The failure stop button 4 records the cause of the failure stop. The failure stop button 4 is operable when the start button 1 is operable, and is inoperable when the start button 1 is not operable. When the failure stop button 4 is operated, a major category item of the corresponding facility is searched from the operation master database (local) 20a, and a transition is made to a major category selection screen.

The break button 5 is for recording a break. The break button 5 is operable when the start button 1 is operable, and is inoperable when the start button 1 is not operable. When the break button 5 is operated, a break category is searched from the operation master database (local) 20a, and a transition is made to a large category selection screen. During a break, you can change the button name to Break Cancel and cancel the break. In the case of a break cancellation, the recording of the break is canceled.

The setup button 6 records the contents of the setup work. The setup button 6 is operable when the start button 1 is operable, and is inoperable when the start button 1 is not operable. When this setup button 6 is operated, the setup classification is searched from the operation master database (local) 20a, and the screen is transited to a large category selection screen.

The operation status button 7 is used for referring to the operation status, and is always operable. When the operation status button 7 is operated, the event database 20
b, and retrieves the determined valid data stored in b.
A list is displayed on the screen of 0d.

FIGS. 4 to 7 are screen transition diagrams of the operation information collection menu screen at the start of work. On the initial screen (FIG. 4), the previous (most recent) closing date and time is searched from the event database 20b and displayed. When the start button 1 is operated from the initial screen (FIG. 4) by the operator A, the screen changes to a start time input screen (FIG. 5). For the start date, the date of the calendar of the process control client 20 is applied. For the start time, the start time of day shift is displayed as a default value. If the time needs to be changed, operate the increase / decrease button to set the desired time. A selection operation is performed and the start button 1 is operated.

When the start button 1 is operated, the start item is searched from the operation master database 20a, and the screen shifts to a start classification screen (FIG. 6). Operate the start work button. When the start work button is operated, the screen branches to the input operation of management stop on the screen (FIG. 7), and the input operation is performed. When the start work is not required, the return button is operated.

FIGS. 8 to 11 are screen transition diagrams of the operation information collection menu screen in the case of closing. On the initial screen (FIG. 8), the starting date and time is searched from the event database 20b and displayed. When the end button 2 is operated from the initial screen (FIG. 8) by the operator A, the screen changes to an end time input screen (FIG. 9). For the end date, the date of the calendar of the process control client 20 is applied. For the end time, the end time of day shift is displayed as a default value. If the time needs to be changed, operate the increase / decrease button to set the desired time. A selection operation is performed, and the end button 10 is operated.

When the end button 10 is operated, it is confirmed whether or not the management stop has been input in the event database 20b. If the stop has not been input, the screen shifts to the management stop major classification screen (FIG. 10). If the end is recorded. Thus, the initial screen becomes the screen before the start of work. When the management suspension has been input, the user operates a closing work button from the screen (FIG. 10) to enter a closing work such as an inspection at the end of working. When the closing work button is operated, the screen branches to the input operation of the management stop on the screen (FIG. 11), and the input operation is performed. When the finishing work is not required, the return button is operated.

FIGS. 12 to 17 are screen transition diagrams of the operation information collection menu screen when the management is stopped. When the management stop button 3 is operated on the initial screen (FIG. 12), the management stop category is searched from the operation master database 20a, and a transition is made to a large category selection screen (FIG. 13).
When a predetermined event, for example, a planned suspension is selected from this screen, the screen similarly transits to a middle category selection screen (FIG. 14),
In addition, when a predetermined selection button is operated on this screen, the screen further transits to a small classification selection screen (FIG. 15).

When the sub-category selection is completed, the screen transits to the input confirmation screen (FIG. 16), and when the enter button is operated, the display returns to the initial screen (FIG. 17), the display of the selected planned pause flashes, and the management is stopped. In addition to displaying that there is, the display of the management stop button 3 is changed to “management end”. In this state, the operator A can operate the management stop button 3 to end the management stop.

FIGS. 18 to 22 are screen transition diagrams of the operation information collection menu screen in the case of automatically collecting operation information on stoppage due to equipment failure. The failure point of the production equipment
Since the information is transmitted to the process control client 20 by the sensor 40a, an item indicating a failure location of the corresponding equipment is searched from the operation master database 20a, and a middle category selection screen (FIG. 18) is displayed in a pop-up.

The operator A confirms a corresponding portion of the production facility 40 and selects a failure event from this screen. For example, when the vacuum pressure is abnormal, when this button is operated, the sub-category item is searched, and the screen transits to the sub-category selection screen (FIG. 19).
The operator A selects the main cause of the failure from the confirmed events and operates the corresponding button to determine the cause. For example, when the main cause of the failure is a pressure sensor failure, the corresponding button is operated. By this operation, information such as the name of the equipment for failure stop, the failure location, the main cause of the failure, the start time of the failure stop, and the like are determined (FIG. 21), and are stored in the event database 20b.

At this time, on the initial screen (FIG. 20), the item selected on the small category selection screen (FIG. 19), that is, the pressure sensor abnormality is displayed as a message. On the other hand, if the return button is selected in the middle category selection screen (18) if the fault location is other than the displayed item, the screen transitions to the large category selection screen (FIG. 20), and this large category selection screen (FIG. 20) ), A transition is made to the intermediate category selection screen corresponding to the selected failure point, and the operator A can select the corresponding item from the screen that has transitioned.

FIGS. 23 to 27 are screen transition diagrams of the operation information collection menu screen when the operation information on the stop due to the equipment failure is collected by the operator's operation. When the management stop button 3 is operated on the initial screen (FIG. 23),
The classification of the failure stop is searched from the operation master database 20a, and a transition is made to a large classification selection screen (FIG. 24). The operator A confirms the failure location of the production equipment 40 and selects a corresponding event. For example, if the drilling position is defective, when this button is operated, the middle category item is searched and the screen is changed to the middle category selection screen (FIG. 25), and the operator A operates the corresponding button from the confirmed event. For example, if the middle classification item is LAST length failure, when this button is operated, the small classification item is searched and transited to the small classification selection screen (FIG. 26), and then the operator A selects the main cause of the failure and applies it. Operate the button to perform. For example, if the main cause of the failure is a trim die set installation error, the corresponding button is operated to transit to the screen of FIG. 27, and if the confirm button is operated, the input information is confirmed. By this operation, information such as the name of the equipment for failure stop, the failure location, the main cause of the failure, the start time of the failure stop, and the like are accumulated in the event database 20b.

FIGS. 28 to 37 are screen transition diagrams of the operation information collection menu screen in the case of a break. Initial screen (Fig. 2
When the break button 5 is operated in step 8), a break category is searched from the operation master database 20a, and a transition is made to a large category selection screen (FIG. 29). When the operator A selects a predetermined break time from this screen, the screen is displayed. (FIG. 30)
The break start time is displayed, and when the confirm button is pressed, the break start time is fixed. In this state, the display of the break button 5 on the initial screen (FIG. 31) changes to the display of the break cancellation as described above, and the operator A can cancel the break.

When the break time selected by the operator A has elapsed from the break start time, the break is automatically terminated, and the screen automatically shifts to the next display screen (initial screen) (FIG. 32). When a failure occurs in the production equipment during the break and the predetermined break time ends, the screen changes to the screen of FIG. 33, and then the treatment start screen (FIG. 3).
4) is displayed in a large scale or blinks, and the state transitions to the state of waiting for the operator A to take action. Operator A
When the user operates the treatment start button 9, the screen transits to the middle classification selection screen for failure stop (FIG. 35).

Since the failure location of the production equipment 40 is transmitted to the process control system client 20 by the sensor 40a, an item indicating the failure location of the relevant equipment is searched from the operation master database 20a, and the middle category selection screen (FIG. 35) is displayed. Is displayed. The operator A checks the corresponding part of the equipment and selects a failure event from this screen. For example, if the P-cap supply time is over, when this button is operated, the sub-category item is searched, and the screen transits to the sub-category selection screen (FIG. 36). The user operates the button to confirm (FIG. 37). For example, if the main cause of the failure is a P-cap flip, the corresponding button is operated. By this operation, information such as the name of the equipment for failure stop, the failure location, the main cause of the failure, the start time of the failure stop, and the like are accumulated in the event database 20b.

FIGS. 38 to 43 are screen transition diagrams of the operation information collection menu screen in the case of setup. When the setup button 6 is operated on the initial screen (FIG. 38), the setup class is searched from the operation master database 20a, and the screen is transited to a large category selection screen (FIG. 39). select. For example, in the case of a switching operation, when the corresponding button is operated, the middle category item is searched and the screen transits to the middle category selection screen (FIG. 40).

The operator A selects the middle category (FIG. 40).
Select the relevant item from and operate the corresponding button. For example, when the C label switching button is operated, the sub-category item is searched and the display transits to the sub-category selection screen (FIG. 41). Thereafter, when the operator A operates a corresponding work item, for example, a 1-roll end button from the sub-category selection screen, the screen transits to a screen (FIG. 43).
The input information is determined. At this time, on the initial screen of FIG. 42, the item selected on the small category selection screen (FIG. 41), that is, the end of one roll, is displayed as a message.

FIG. 44 and FIG. 45 are screen transition diagrams of the operation information collection menu screen when referring to the operation status. When the operation status button 7 is operated on the initial screen (FIG. 44), the confirmed valid data stored in the event database 20b is searched, and the operation information list shown on the screen (FIG. 45) is displayed.

Next, a description will be given of the operation of the operation information tallying process and the output process in the production facility operation status management system 10.

FIG. 46 is a flowchart showing the procedure of the operation information tallying process. When the production management staff totals the operation status of the equipment based on the operation information of the production equipment collected as described above, the production management client 30
Starts the processing program 30a and performs a totaling process based on the totaling master database 14e of the production management system server 14.

First, working hours are calculated from collected data, which is operation information accumulated in the operation log database 14b (step S1). In this calculation, the work time is calculated by calculating the time from the start time to the end time and subtracting the rest time from the time.

Next, an overlap time elimination process for eliminating the times at which the overlaps are collected is performed (step S2), and then a management stop calculation for calculating the time of the management stop state is performed (step S3).

Similarly, a failure stop calculation for calculating the time during which the equipment was in the failure stop state (step S4), a setup calculation for calculating the time for performing the setup work for operating the equipment (step S5), A main work calculation (step S6) for calculating a main work time, which is a time during which the production equipment has been operating for production, is performed.

Further, other calculations for calculating the number of production units, the number of defective units, the failure rate of the equipment, the operation rate, and the like are performed (step S7), and total data of the operation state is created. The aggregated data created in this way is, as shown in FIG.
On the basis of the operation status totalization menu screen displayed on the screen of the CRT 30d of the production management system client 30, the totalization processing is performed in accordance with the designated conditions input by the production management staff, and the display is output (step S8).

This menu screen is displayed in the output destination designation area 5
1. A total output specification area 50 for specifying the output method of total data by setting predetermined data in the total unit specification area 52 and the total period specification area 53.

The output destination designation area 51 is for designating the output destination of the total data, and selects and designates one of screen display, form printing, and file output by operating the corresponding button.

The aggregation unit designation area 52 is used to select and designate a unit for performing aggregation, and to designate each of the facilities or each of the steps by operating a corresponding button (the default value is for each facility), and Enter the equipment name or process name.

The counting period designation area 53 is used to specify a period to be subjected to the counting process, and to input a target date for starting counting and a target date for ending counting. When there is no data between the specified start date and the specified end date, when the specified start date and the specified end date are logically inconsistent, or when the data is inconsistent with the internal calendar of the production management client 30 Displays an error message.

In the menu screen (FIG. 47), a text entry box for the name of the beginning plan is used to set the name of the beginning plan at the time of tabulation. Read the specified file name and use it as the beginning plan data. If the opening plan data is not used, it is ignored even if specified here.

The tabulation data item button is used to specify which tabulation item should be used for tabulation processing, and can be designated by operating the corresponding button for daily tabulation, graph tabulation, or period end report. I do.

The processing of each function button provided at the lower part of the menu screen is as follows.

The time ratio button tabulates the time ratio between the tabulated data items and outputs the tabulated result as a graph.

The failure rate button for each process is for summing up the failure rate for each process and outputting it as a graph. When the totaling for each process is specified as the totaling unit and the term-end report is specified as the total data item. It becomes operable and totals the failure rate for the specified period for each equipment in the specified process. The top 10 items of the totaled result are totaled by individual items, and the remaining items are collectively totaled by others, and can be output as a graph.

The equipment failure rate button tabulates the failure rate for each equipment and outputs it in a graph. This button can be operated when the totaling for each equipment is specified as the totaling unit and the graph data is specified as the totaling data item. Then, the failure rate in the designated period is totaled for each facility in the designated process. The top 10 items of the totaled result are totaled by individual items, and the remaining items are collectively totaled by others, and can be output as a graph.

The item 1 button and item 2 button are used to execute the totalization of the items. The button becomes operable when the daily totalization of the total data item is designated, and the items are totalized according to the designated totaling condition. .

The tabulation table button is used to perform tabulation of all data of the operation editing data. The tabulation button is operable when the daily tabulation of the tabulation data item is designated, and is operated according to the designated tabulation condition. Perform tallying. In the processing of each of the above function buttons, if printing is designated, a printing screen is displayed in a pop-up.

The end button is for terminating the operation status tabulation menu screen. When this button is operated, the operation status tabulation menu screen is unloaded and the screen returns to the management screen. During the tallying process, for example, a pop-up message screen is displayed, a message “Totaling process is being executed” is displayed, and a button for stopping the process is displayed.

The above totaling processing and output processing such as printing are performed based on the setting contents of the print master schematically shown in FIG. The print master is classified, total item, unit,
It is composed of a formula, a tabulation list (by process), a tabulation list (by equipment), a tabulation field or a calculation formula. For example, the working hours of the tally item are Class A, and the formula is calculated by accumulating the actual values. 1 in the columns of the tabulation list (by process) and tabulation list (by facility) indicates that the tally item of working hours is included in the tabulation list by process and by facility. Hereinafter, the same is applied to each total item.

FIG. 49 is a diagram showing an example of the total list when the total button (FIG. 47) is operated. The classification, the total item, the unit, and the formula have the same contents as those of the print master setting shown in FIG. 48. For each total item, the equipment MC01 in the period designated on the total menu screen (FIG. 47) is displayed.
The data for each of MC04 to MC04 is tabulated and printed. In addition,
The plan column is a column where the value of the beginning plan data is printed when used.

FIG. 50 is a view showing an example of the specification 1 printed when the specification 1 button (FIG. 47) is operated. Item 1 is for totaling the status of equipment management suspension. This example is for a case where a facility is specified on the totaling menu screen (FIG. 47) and totaling for one month in April 2000 is specified. Stop item, stop time,
The number of occurrences is counted and printed.

FIG. 51 is a diagram showing an example of the detail 2 printed when the detail 2 button (FIG. 47) is operated. Item 2 is for counting the failure stop state of the equipment. This example is for a case where the equipment is specified on the calculation menu screen (FIG. 47) and the total for one month in April 2000 is specified. The stop item, the stop time, and the number of occurrences are totaled and printed for each of the middle classifications of the failure stop. In addition, the quantity such as the number of good products and the number of defective products at that time is also printed.

FIG. 52 is a table showing an example of report items when the term end report is designated on the tabulation menu screen (FIG. 47). In the end-of-term report, these items are totaled and data such as the time ratio is output. For example, the turnover time is the time required for the original production obtained by dividing the quantity produced at the time excluding the rest time by the unit capacity of the equipment, and the time ratio is the C1 main work time. Note that C1, t1, t2, t2a, and C2 in the time ratio correspond to the classification in the print master setting shown in FIG.

FIG. 53 is a diagram showing an example in which the aggregated time ratio data is output as a graph. This graph shows the t1 time ratio 60a, the equipment failure ratio 60b, the non-t2 failure ratio 60c, and the C2 time ratio 60 for each month compared to the beginning plan.
d, C1 main work time ratio 60e is displayed in a graph.

FIG. 54 is a diagram showing an example in which the collected failure rate data is output as a graph. This graph shows the failure ratio of the designated facility MC01 in a bar graph for each month, and in each bar graph, the failure rate is displayed for each failure content in descending order from the bottom. In addition, below the bar graph, FIG.
As shown in FIG. 7, the failure contents from the first to tenth ratios are displayed. The details of the faults of the 11th rank or lower are collectively displayed in other sections.

By displaying the aggregated data as described above, it is possible to easily extract a defective portion that may reduce the operation rate.

[0081]

As described above, according to the production equipment operation status management system of the present invention, accurate information on the operation status of the production equipment is appropriately collected and stored in a database to improve the operation efficiency. The effect that total data for the purpose of analysis can be output is obtained.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of a production equipment operation status management system according to the present invention.

FIG. 2 is a schematic diagram showing a function and an operation flow of the production equipment operation status management system.

FIG. 3 is a diagram showing an initial screen of an operation information collection menu.

FIG. 4 is a diagram showing an operation information collection menu screen at the start of work.

FIG. 5 is a diagram showing an operation information collection menu screen at the start of work.

FIG. 6 is a diagram showing an operation information collection menu screen at the start of work.

FIG. 7 is a diagram showing an operation information collection menu screen at the start of work.

FIG. 8 is a diagram showing an operation information collection menu screen in the case of closing.

FIG. 9 is a diagram showing an operation information collection menu screen in the case of closing.

FIG. 10 is a diagram showing an operation information collection menu screen in the case of closing.

FIG. 11 is a diagram showing an operation information collection menu screen in the case of closing.

FIG. 12 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 13 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 14 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 15 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 16 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 17 is a diagram showing an operation information collection menu screen in the case of management suspension.

FIG. 18 is a diagram showing an operation information collection menu screen when automatically collecting operation information regarding a failure stop.

FIG. 19 is a diagram showing an operation information collection menu screen when automatically collecting operation information relating to a failure stop.

FIG. 20 is a diagram showing an operation information collection menu screen when automatically collecting operation information regarding a failure stop.

FIG. 21 is a diagram showing an operation information collection menu screen when automatically collecting operation information regarding a failure stop.

FIG. 22 is a diagram illustrating an operation information collection menu screen when automatically collecting operation information regarding a failure stop.

FIG. 23 is a diagram showing an operation information collection menu screen in a case where operation information regarding stoppage due to equipment failure is collected by an operator operation.

FIG. 24 is a diagram showing an operation information collection menu screen in a case where operation information regarding stoppage due to equipment failure is collected by an operator operation.

FIG. 25 is a diagram showing an operation information collection menu screen in a case where operation information relating to stoppage due to equipment failure is collected by an operator operation.

FIG. 26 is a diagram showing an operation information collection menu screen in a case where operation information regarding stoppage due to equipment failure is collected by an operator operation.

FIG. 27 is a diagram showing an operation information collection menu screen in a case where operation information regarding stoppage due to equipment failure is collected by an operator operation.

FIG. 28 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 29 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 30 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 31 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 32 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 33 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 34 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 35 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 36 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 37 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 38 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 39 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 40 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 41 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 42 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 43 is a diagram showing an operation information collection menu screen in the case of a break.

FIG. 44 is a diagram showing an operation information collection menu screen in the case of setup.

FIG. 45 is a diagram showing an operation information collection menu screen in the case of setup.

FIG. 46 is a flowchart illustrating a procedure of an operation information totaling process;

FIG. 47 is a diagram showing an operation status totaling menu screen.

FIG. 48 is a diagram showing an outline of print master setting contents.

FIG. 49 is a diagram illustrating an example of a tally list when the tally table button shown in FIG. 47 is operated.

50 is a diagram illustrating an example of a specification 1 printed when the specification 1 button illustrated in FIG. 47 is operated.

FIG. 51 is a table showing an example of report items when a term-end report is designated on the tabulation menu screen shown in FIG. 47;

FIG. 52 is a table showing an example of report items when a term end report is designated on the tabulation menu screen shown in FIG. 47;

FIG. 53 is a diagram showing an example in which time ratio data is output as a graph.

FIG. 54 is a diagram showing an example in which failure rate data is output as a graph.

FIG. 55 is a diagram showing a display example of failure content by rank.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 10 ... Production equipment operation status management system 14 ... Production management system server 14a ... Operation master database 14b ... Operation log database 14c, 20c, 30a ... Processing program 16 ... Network communication path 20 ... Process control system client 20a ... Operation master database 20b ... Event database 30 Production management client 40 Cutting machine (production equipment) 40a Sensor 40b Machine control panel 40c Information control panel

Claims (4)

[Claims] 1. A plurality of production facilities arranged on a production line, a plurality of process control clients for controlling the production facilities, and connected to the process control clients via a network to process production management operations. A production management system server and a production management system client, wherein the production management system server collects operation information of the production equipment, and an operation master storing information on an operation information collection menu screen. A database, and an operation log database that accumulates the operation information collected via the process management client. The process management client includes a local operation master database copied from the operation master database, and the operation information. Accumulate the operation information collected based on the collection menu A production equipment operation status management system, comprising: an event database; collecting the operation information stored in the event database in an operation log database; and creating required aggregated data by the production management client. 2. The production equipment operation status management system according to claim 1, wherein the collected information stored in the operation master database has a structure hierarchized for each event. 3. The production equipment operation status management system according to claim 2, wherein a screen of said operation information collection menu is set based on said hierarchically collected information. 4. An operation master database that stores hierarchically collected information for collecting operation information of a production facility, and information on a screen of an operation information collection menu; an event database that stores the operation information; An aggregation master database for creating aggregation data from the operation information accumulated in the event database; and setting a screen of the operation information collection menu according to the hierarchically collected information, and setting the screen to the set screen. A production equipment operation status management system, wherein the operation information is collected based on the collected operation information, and total data is created from the collected operation information.