WO2020255515A1

WO2020255515A1 - Information system and information management method

Info

Publication number: WO2020255515A1
Application number: PCT/JP2020/012955
Authority: WO
Inventors: 仁志石田; 啓生宮本; 韵成朱; 育美井上
Original assignee: 株式会社日立製作所
Priority date: 2019-06-20
Filing date: 2020-03-24
Publication date: 2020-12-24
Also published as: JP7393137B2; JP2021002138A

Abstract

This information system: associates and retains information relating to performance of operations, information relating to quality events, and a search history in which information relating to performance of operations was searched with respect to operation quality events; associates and extracts both a cause of a quality event, which was identified on the basis of a manufacturing record and quality event data, and either the manufacturing records that were examined until the identification of the cause, or the reason for the identification of the cause; and causes a user interface to display and thereby present the extracted cause and the extracted manufacturing records or reason to a user.

Description

Information system and information management method

The present invention relates to an information system and an information management method.

In various business formats such as manufacturing and service industries, products and services are provided by carrying out a large number of operations as a series of operations. For example, in each business constituting a manufacturing process in a factory or an office in the manufacturing industry, on-site data is generated and collected when the business is completed or a predetermined event occurs. On-site workers analyze this on-site data to optimize work efficiency in each task.

On the other hand, if the department that manages each business is different, it becomes difficult to share information between departments, and problems that cross departments or business cannot be improved. One of the reasons why the improvement of problems across departments or operations is not progressing is that the systems used for managing operations in each department are different and the management system is not unified.

In addition, in each department, the optimization of work efficiency within the department is progressing by analyzing the collected field data, so if the overall optimization of a series of manufacturing processes is sought, the efficiency of the own department will be poor. It can result in lower department ratings. However, in the manufacturing industry, cooperation between departments is indispensable in order to move from the mass production method to the low-volume, high-mix production method and improve the production efficiency of the entire manufacturing process.

On the other hand, in addition to on-site data generated in the manufacturing process, there is quality event data such as complaints about products, defective products, defects or deviations that occurred in the manufacturing process. For example, when a product complaint occurs, the quality control department collects on-site data, which is the manufacturing record of the product, analyzes the cause of the complaint, and considers corrective measures for the identified factor.

In Patent Document 1, "the code master DB contains a code that unifies the inspection items of the inspection process performed in each process of parts acceptance, production, shipping, and market and the items of quality defect information generated in connection with the inspection. Register in advance, record the part ID unique to the part and the product ID unique to the product in association with the barcode label for parts and the barcode label for products, and attach this barcode label to each part and each product. A quality control system is disclosed that manages the quality history of each product by reading the part ID or product ID for each process, inputting the inspection result and quality defect information, and storing them in each DB.

JP-A-2003-233652

However, in the quality control system disclosed in Patent Document 1, only the result of identifying the cause of the quality defect is managed. Therefore, even if the same event occurs, the experience of performing the same factor analysis in the past is experienced. It can be difficult to identify factors other than one technician or a technician skilled in factor analysis.

In addition, the quality may be affected by the change measures taken at the time of manufacturing the product before the defective product, but in the quality control system disclosed in Patent Document 1, a certain product ID is used. It is not easy to search for quality events other than quality events related to, and the factor analysis of quality events may take a long time.

The result of a series of business processes consisting of multiple businesses not only in the business process of product manufacturing in the manufacturing industry but also in other industries such as the logistics industry, retail business or service industry that provide products, goods or services. Common issues may arise.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an information system and an information management method capable of improving the efficiency of factor analysis of quality events.

In order to achieve the above object, the information system according to the first aspect includes a storage unit that can be read by a computer, and the storage unit includes information on the execution of business, information on quality events of the business, and the quality. Retains information on the analysis process related to events in association with each other.

According to the present invention, the efficiency of factor analysis of quality events can be improved.

It is a block diagram which shows the configuration example of the network environment to which the information system which concerns on 1st Embodiment is applied. It is a block diagram which shows the functional configuration example of the information system of FIG. It is a figure which shows the example of the data structure of the relevance data, and the relationship between the relevance data and the quality event management data. It is a figure explaining an example of the structure of the definition information of the relevance data of FIG. It is a figure which shows an example of the complaint information of FIG. It is a figure which shows an example of the deviation information of FIG. It is a figure which shows an example of the change information of FIG. It is a figure which shows the example of the operation procedure until the information system of FIG. 1 correlates and extracts the relevance data and the quality event data, and provides the data for analysis. It is a figure which shows the example of the operation procedure until the information system of FIG. 1 analyzes the root cause of a quality event and registers the analysis information. It is a figure which shows the example of the factor analysis result registered in the quality event management data storage part of FIG. It is a figure which shows the example of the analysis screen which confirms the quality event data, and selects and extracts the site data. It is a figure which shows the example of the screen which registers the process and result of the factor analysis of a quality event based on the confirmed field data. It is a figure which shows the example of the screen which searches and extracts the information of the registered factor analysis process and the past quality event. It is a figure which shows the example of the operation procedure which the information system of FIG. 1 searches for a quality event. It is a figure which shows the example of the search procedure of the quality event when the information system which concerns on 2nd Embodiment manages manufacturing record and quality event management data in different storage part. It is a figure which shows the example of the search procedure of the quality event when the information system which concerns on 3rd Embodiment manages quality event management data as extended information of definition information of relevance data. It is a figure which shows the example of the search procedure of the quality event when the information system which concerns on 4th Embodiment defines and manages the quality event management data as a node of the relevance data. It is a block diagram which shows the hardware configuration example of the information system of FIG.

The embodiment will be described with reference to the drawings. It should be noted that the embodiments described below do not limit the invention according to the claims, and all of the elements and combinations thereof described in the embodiments are essential for the means for solving the invention. Not necessarily.

FIG. 1 is a block diagram showing a configuration example of a network environment to which the information system according to the first embodiment is applied.
In FIG. 1, the information system 1 is connected to the network 2. Further, in the network 2, a plurality of

data generators

5a, 5b, and 5c (hereinafter,

data generators

5a, 5b, and 5c) that collect or generate on-site data corresponding to manufacturing records are simply data unless otherwise distinguished. The generator 5), the master data storage unit 3, and the site data storage unit 4 that stores the site data that is the manufacturing record are connected.

Further, the network 2 is connected to a quality event input device 7 for inputting quality event data such as product complaints and change measures, and a quality event data storage unit 6 for accumulating quality event data. These data generators 5, the master data storage unit 3, the field data storage unit 4, and the quality event data storage unit 6 are connected to the information system 1 via the network 2.

The data generator 5 may be, for example, a barcode reader that acquires the work log of the worker, a PC (Personal Computer) or a server (for example, the data generator 5a) that collects the work log, and processes parts. Alternatively, it may be a machine for assembling the finished product (for example, a data generator 5b), or a sensor (for example, a data generator) for collecting inspection information of RFID (Radio Frequency Identification) attached to a part or a finished product. 5c) may be used. The field data collected or generated by these data generators 5 is transmitted to the information system 1, the master data storage unit 3, or the field data storage unit 4 via the network 2.

The master data storage unit 3 is, for example, a storage device such as a server or a memory, and stores a model that defines what kind of information is stored in the field data storage unit 4 or the like. This model is also called master data. That is, by changing the master data (model) defined in the master data storage unit 3, it is possible to change what kind of site data (type of information to be collected) is collected from the data generator 5. The master data of the master data storage unit 3 can be set or changed via an external device (not shown).

The site data storage unit 4 is, for example, a storage device such as a server or a memory, and stores site data including information defined in the master data of the master data storage unit 3. On-site data storage unit 4 stores, for example, on-site data such as identification information, date and time of occurrence, and measured values.

The quality event input device 7 is a PC or a server for inputting quality event data such as information on complaints or inquiries about products received by a call center, a sales department, a quality control department, or the like. In addition, field workers or quality control departments can provide information on defects (sometimes called deviations) during the manufacturing process, information on changes to be taken as corrective actions such as complaints or defects, productivity improvement or maintenance. Information on change measures to be implemented for such purposes is also entered. The quality event input device 7 may be a different device for each quality event.

Further, the quality event input device 7 may be a management system that manages a series of workflows related to quality events such as registering the above-mentioned quality events, sending a factor analysis request, registering and approving the factor analysis results, and the like. Good. The quality event data input by the quality event input device 7 is transmitted to the quality event data storage unit 6 via the network 2.

The quality event data storage unit 6 is, for example, a storage device such as a server or a memory, and stores quality event data input via the quality event input device 7.

The information system 1 holds information on the execution of business, information on quality events of business, and information on the analysis process related to quality events in association with each other. This work is, for example, a work carried out as a series of flows in a manufacturing process in the manufacturing industry. This business may be a business carried out as a series of flows in a business process such as a logistics business, a retail business, or a service business.

Information on the implementation of business is, for example, an implementation record regarding the implementation of business. The implementation record regarding the implementation of the business contains the business information regarding the implementation of the business. The implementation record relating to the execution of the business may include business-related information related to the business together with the business information related to the performance of the business. Business-related information is information such as things, people, and procedures related to the performance of business. For example, the business-related information is worker information, machine information, parts information, and work procedure information associated with the business information.

Information on quality events is, for example, information such as deviations that occurred in the manufacturing stage, product complaints and their causes, change measures implemented as corrective measures, or change measures for improving productivity.

Information related to quality events may be associated with business information or business-related information related to quality events, or may be associated with business information or business-related information related to factors of quality events. Information about a quality event may be associated as an information element of business information or business-related information related to a quality event, or may be associated as an information element of business information or business-related information related to a factor of a quality event. .. Business information, business-related information, and information related to quality events may be defined as information elements, respectively.

The information on the analysis process related to the quality event is, for example, the search history of the information related to the execution of the business searched for the quality event. The information of the analysis process regarding the quality event indicates, for example, the information of the process leading to the identification of the cause of the occurrence of the quality event. The information in the analysis process regarding the quality event may include information on the judgment result and the reason for the judgment as to whether or not the business information or the business-related information is a factor of the quality event.

Here, the information system 1 is specified based on the manufacturing record and the quality event data by holding information on the execution of the business, information on the quality event of the business, and information on the analysis process related to the quality event in association with each other. It is possible to extract and display the factor of the quality event in association with the manufacturing record confirmed up to the identification of the factor or the reason for identifying the factor. Therefore, even if the engineer is not an engineer who has performed the same factor analysis in the past or an engineer who is skilled in the factor analysis, the factor analysis of the quality event such as a product complaint can be expedited.

Further, the information system 1 can facilitate the search for quality events other than the quality event related to a certain product ID, and the change measures implemented at the time of manufacturing the product before the defective product can be implemented. Even when the quality is affected, it is possible to prevent the long-term factor analysis of quality events from being prolonged.

The main functions of the information system 1 will be described below. The information system 1 is provided by a central processing unit (Central Processing Unit: CPU) that controls the entire information system 1, a storage device (Read Only Memory: ROM) that stores each control program that controls the information system 1, and a CPU. It is equipped with a primary storage device (Random Access Memory: RAM) and a hard disk drive (Hard Disk Drive: HDD) that temporarily store the processed information. The following functions are realized by the CPU executing each control program stored in the ROM.

FIG. 2 is a block diagram showing a functional configuration example of the information system of FIG.
In FIG. 2, the information system 1 is associated with the relevance data model creation unit 10, the relevance data registration unit 11, the relevance data search unit 12, the accumulated data acquisition unit 13, and the analysis data storage unit 14. The sex data storage unit 15, the data provision API (Appliance Programming Interface) unit 16, the control data definition unit 17, the temporary storage unit 18, the quality event management data acquisition unit 19, and the quality event management data storage unit 20. Have.

The information system 1 is connected to the site data storage unit 4, the data generator 5, the master data storage unit 3, the quality event data storage unit 6, and the dictionary database 21 via the network 2. The relevance data model creation unit 10 and the relevance data search unit 12 are connected to the user interface 9. The user interface 9 provides the user with a display environment for displaying the information of the result processed by the information system 1, or provides an input environment for inputting predetermined information to the relevance data model creation unit 10 or the relevance data search unit 12. Provide it to the user.

The analysis data storage unit 14 and the data provision API unit 16 provide the information of the result processed by the information system 1 to the application 8 external to the information system 1.

The relevance data model creation unit 10 reads the master data corresponding to the model data from the master data storage unit 3 based on the model data input from the user interface 9, and creates the definition information 300 of FIG. The definition information 300 created by the relevance data model creation unit 10 has a predetermined data structure, and what kind of data structure the relevance data registration unit 11 acquires on-site data from the data generator 5 is determined. Define.

The relevance data registration unit 11 receives the site data from the data generator 5 and structures the site data based on the data structure defined in the definition information 300 acquired from the relevance data model creation unit 10. Then, the relevance data registration unit 11 determines whether the site data acquired according to the definition information 300 is business information, a worker, a machine (or equipment), a work procedure, or a material (or a part). Judgment is made based on the identification information given to the site data.

Hereinafter, the acronym M for the worker (Man), machine (Machine), method (Method), and material (Material) is taken, and these information are referred to as 4M information (or 4M node) or business-related information. Sometimes. In addition, workers, machines (or equipment), work procedures and materials (or parts) may be abbreviated as 4M. In the following description, 4M may also refer to at least one of a worker, a machine (or equipment), a work procedure and a material (or part).

A control data definition unit 17 is connected to the relevance data registration unit 11. The control data definition unit 17 defines the relationship between the 4M information determined by the relevance data registration unit 11 and the identification information given to the site data. Based on this definition, the relevance data registration unit 11 associates the 4M information determined by the relevance data registration unit 11 with the actually acquired site data (mapping the identification information of the site data to the 4M information). To do). The relevance data registration unit 11 transmits 4M information related to the site data to the relevance data storage unit 15.

Further, a temporary storage unit 18 is connected to the relevance data registration unit 11. The temporary storage unit 18 is a storage device such as a memory, and registers information for forming a connection relationship (generating a connection line) of each information (business information and 4M information) included in the site data.

The accumulated data acquisition unit 13 acquires site data from the site data storage unit 4 or the master data storage unit 3 based on the relevance data 100 accumulated in the relevance data storage unit 15. As shown in FIG. 3, the relevance data 100 includes business information and 4M information.

The relevance data search unit 12 acquires on-site data and quality event data from the relevance data storage unit 15, the quality event management data storage unit 20, and the like according to the search conditions input from the user interface 9, and displays them on the user interface 9. And present it to the user. Further, the relevance data search unit 12 transmits the factor analysis information of the quality event input from the user interface 9 to the quality event management data storage unit 20. Further, the relevance data search unit 12 transmits the acquired site data and quality event data as analysis data to the analysis data storage unit 14.

The analysis data storage unit 14 transmits the analysis data composed of the site data and the quality event data transmitted from the relevance data search unit 12 to the application 8. The application 8 executes data analysis using various analysis methods by using the analysis data transmitted from the analysis data storage unit 14.

The data providing API unit 16 transmits the data associated with the relevance data 100 to the application 8. Further, the data providing API unit 16 acquires data related to the quality event from the quality event management data storage unit 20 and transmits the data to the application 8. The data providing API unit 16 is connected to the dictionary database 21. The dictionary database 21 associates and registers different words having the same meaning in the item names of the 4M information used in each manufacturing process.

By referring to the dictionary database 21, the data providing API unit 16 not only has the same word but also the same even if the item name of the 4M information used in each manufacturing process (business) is different for each manufacturing process. It is possible to accurately acquire the data associated with the relevance data 100, including words having different meanings.

The quality event management data acquisition unit 19 acquires the quality event data, the identification information required for the management thereof, the access information to the quality event data storage unit 6, etc. from the quality event data storage unit 6, and the quality event management data 200 Is stored in the quality event management data storage unit 20.

The quality event management data storage unit 20 holds information on business execution, information on quality events, and information on the analysis process related to quality events in association with each other. The information regarding the implementation of the business is, for example, the relevance data 100 of FIG. The information regarding the quality event is, for example, the quality event management data 200 of FIG. The information of the analysis process regarding the quality event is, for example, the information of the survey result of FIG.

FIG. 3 is a diagram showing an example of the data structure of the relevance data and the relationship between the relevance data and the quality event management data.
In FIG. 3, the information system 1 of FIG. 2 manages the data structure of the relevance data 100 and the data structure of the quality event management data 200, and the relationship between the relevance data 100 and the quality event management data 200. The relevance data 100 is data stored in the relevance data storage unit 15. The quality event management data 200 is data stored in the quality event management data storage unit 20.

The data structure of the relevance data 100 correlates on-site data generated from various devices (data generator 5) in each manufacturing process, so that any worker or machine can be used for a predetermined operation (manufacturing process). And, it shows how the parts were related in what kind of work procedure. The relevance data 100 is, for example, centered on the business node 110 associated with the business, the component node 120 associated with the material required when executing the business, and the worker node associated with the worker performing the business. 130, machine node 140 associated with the machine used to perform the work, finished product node 150 associated with the finished product generated as a result of performing the work using the parts, and the work execution procedure are defined. Includes work procedure node 160 and the like associated with the work procedure to be performed.

The finished product associated with the finished product node 150 is the material (part) used in the post-process 112, and the material associated with the part node 120 is the finished product produced in the pre-process 111. That is, the material associated with the part node 120 and the finished product associated with the finished product node 150 have the same meaning in terms of attributes, and if both are not particularly distinguished, they may be collectively referred to as a material node. Good. Further, as described above, the component node 120, the worker node 130, the machine node 140, the finished product node 150, and the work procedure node 160 are referred to as 4M information, 4M node, or business-related information.

When a problem occurs in the finished product itself, the information system 1 can search the 4M information associated with the finished product by the relevance data 100, and can determine the factors for the problem in the predetermined manufacturing process (business). You can explore.

In the following description, an example will be taken in which identification information is added to the on-site data collected or generated by the data generator 5 in each manufacturing process.

The information system 1 can manage the relevance between business by accumulating the relevance data 100 that defines the relevance of the machine, the worker, etc. to the business over a plurality of manufacturing processes (business). ..

The basic information of the relevance data 100 is the timing (date and time, time) related to the relationship between the identification information indicating each information and the identification information. The site data (actual data) indicated by each identification information of the relevance data 100 is stored in the site data storage unit 4 managed externally. The information system 1 manages an access method (memory address, etc. for accessing the site data storage unit 4) for the site data stored in the site data storage unit 4.

The relevance data 100 includes business node 110 and 4M information. The connection line connecting each node can be represented by a directed graph by inputting what is necessary to execute the business and outputting the finished product generated by those actions as an output. The information system 1 can display such relevance data 100 as a series of manufacturing processes by expressing a plurality of operations in a row.

The quality event management data 200 represents information on a product or various quality events related to the manufacture of the product. The quality event management data 200 may be the quality event data associated with the relevance data 100 among the quality event data stored in the quality event data storage unit 6, or may be associated with the relevance data 100. It may be information for accessing quality event data. The quality event management data 200 includes complaint information 210, deviation information 220 and change information 230.

Complaint information 210 represents information regarding complaints and inquiries regarding manufactured products. The complaint information 210 is associated with a finished product node 150 indicating the product for which the complaint was made. When the cause of the complaint is identified, the complaint information 210 is associated with the 4M information related to the 4M that caused the complaint. For example, if the cause of the complaint is an inadequate work procedure, the complaint information 210 and the work procedure node 160 are associated with each other.

The deviation information 220 represents information on defects that occurred in the execution and manufacturing stages of work that deviated from the standard work procedure. The deviation information 220 is associated with 4M information related to the 4M that caused the deviation or 4M information related to the 4M that caused the deviation.

Change information 230 represents information regarding 4M change measures. Here, the change measures include the change measures implemented as corrective measures due to defects or defects such as complaints or deviations, and the change measures voluntarily implemented to improve productivity.

The change information 230 is associated with the 4M information related to the 4M to be changed. For example, if the cause of the complaint is identified and, as a result, a modification of the routing associated with the routing node 160 is implemented, the change information 230 is associated with that routing node 160. As another example, if a component change is made to reduce costs, the change information 230 is associated with the component node 120 associated with that component.

Quality event management data 200 such as complaint information 210, deviation information 220, and change information 230 may be associated with different types of business-related information (that is, information classified into different Ms) in the same business. In addition, the quality event management data 200 may be associated with the same type or different types of business-related information of different businesses.

For example, if the cause of the complaint or deviation is 4M related to a plurality of business-related information such as the work procedure node 160 and the component node 120 related to the same business, the complaint information 210 or the deviation information The 220 is associated with a plurality of business-related information such as the work procedure node 160 and the component node 120. Further, when the cause of the complaint or deviation is the work procedure associated with the work procedure node 160 of the plurality of tasks, the complaint information 210 or the deviation information 220 is associated with the work procedure node 160 of the plurality of tasks. Be done.

Similarly, if changes are made due to the same event, such as corrective action or productivity improvement measures for a complaint, the changes relate to multiple business-related information such as routing node 160 and machine node 140. The change information 230 is associated with a plurality of business-related information, such as when it is implemented for the 4M to be performed or when it is implemented for a work procedure related to the work procedure node 160 of a plurality of operations.

In addition, each quality event management data 200 is also associated with each other. For example, if change measures are implemented as a result of a complaint or deviation, the complaint information 210 or deviation information 220 is associated with the change information 230. The change information 230 may be associated with the complaint information 210 or the deviation information 220 when the change causes a complaint or deviation. Further, when the deviation is the cause of the complaint, the deviation information 220 and the complaint information 210 may be associated with each other.

These quality event management data 200 are managed in the form of a table and may be associated with the relevance data 100 based on predetermined identification information. Each quality event management data 200 may be associated with the relevance data 100 as one of the data elements of the relevance data 100. Each quality event management data 200 is defined as a node similar to business information and 4M information, and may be associated with the relevance data 100 in the form of a valid graph using a connection line.

Although FIG. 3 shows an example in which the quality event management data 200 is associated with the 4M information which is business-related information, the quality event management data 200 may be associated with the business information, or the quality event management data 200 may be associated with the business information. May be associated with business information and business-related information.

FIG. 4 is a diagram illustrating an example of the structure of the definition information of the relevance data of FIG.
In FIG. 4, the relevance data model creation unit 10 of FIG. 2 creates and holds the definition information 300. The definition information 300 includes business information 310 as the definition information of the business node 110 in FIG. 3, worker information 320 as the definition information of the worker node 130, component information 330 as the definition information of the component node 120, and definition information of the finished product node 150. It includes finished product information 340, machine information 350 as definition information of machine node 140, and work procedure information 360 as definition information of work procedure node 160.

The business information 310 includes business identification information 311, operating time information 312, operating data access information 313, connection information 314, and extended information 315. The business identification information 311 is identification information that defines what kind of business the business node 110 is. For example, in the vehicle manufacturing process, the identification information that can uniquely identify the chassis press processing business and the assembly business. Set. The business identification information 311 defines the relationship with other business and has information for associating a plurality of business. In addition, the business identification information 311 also includes key information for acquiring site data (actual data) from the site data storage unit 4 or the master data storage unit 3 based on the operation data access information 313.

In the operating time information 312, information regarding the start time and the end time when the predetermined work is executed is set. For example, in a predetermined operation, when a finished product is generated from a part, a part input time is set as a start time, and a finished product production time is set as an end time. This operating time information 312 is used as information for narrowing down from the viewpoint of time when referring to operating information of a worker, a part, a machine, or the like. By having this operating time information 312, the definition information 300 can be provided to the user by associating it as time-series data when the business is executed, even if it is time-series data that is difficult to be associated from a viewpoint other than the time-series. it can.

The operation data access information 313 is used when accessing the site data and the like stored in the site data storage unit 4 managed outside the information system 1. Specifically, the operation data access information 313 includes, for example, the memory address of the site data stored in the site data storage unit 4 or the master data storage unit 3.

In the connection information 314, From-To indicating the connection relationship for associating the business node 110 with the 4M node is described.

The worker information 320 includes the worker identification information 321 and the worker data access information 322, and the extended information 325. In the worker identification information 321, an identifier for identifying the worker in charge when the work is performed at the worker node 130 of FIG. 3 is set. The worker identification information 321 is used as a key for accessing the work record (log) of the worker stored in the site data storage unit 4 or the master data storage unit 3 based on the worker data access information 322. To.

The part information 330 includes the part identification information 331, the part data access information 332, and the extended information 335. The part identification information 331 is defined to identify a material (part) used in business. The component data access information 332 includes, for example, a memory address for accessing information such as the material or processing history of the component stored in the site data storage unit 4 or the master data storage unit 3.

Finished product information 340 includes finished product identification information 341, finished product data access information 342, and extended information 345. The finished product identification information 341 is defined to identify the finished product generated in the business. The finished product data access information 342 includes, for example, a memory address for accessing information such as a processing history of the finished product stored in the site data storage unit 4 or the master data storage unit 3.

The machine information 350 includes machine identification information 351 and machine data access information 352, and extended information 355. The machine identification information 351 defines information for identifying a machine used in business. For example, the machine identification information 351 can be used to identify whether the machine used in business is a press machine, a painting machine, an assembly machine, or the like. The machine data access information 352 includes, for example, a memory address for accessing information such as a machine stored in the field data storage unit 4 or the master data storage unit 3. When the user refers to the operation data of the machine when the business is executed by the machine, the operation data of the machine can be referred to by using the machine data access information 352 and the machine identification information 351.

The work procedure information 360 includes the work procedure identification information 361, the work procedure data access information 362, and the extended information 365. The work procedure identification information 361 defines the identification information that identifies the work procedure manual in the target business. The work procedure data access information 362 includes a memory address or the like that is a key for accessing the work procedure manual data stored in the site data storage unit 4 or the like managed outside the information system 1.

The

extended information

315, 325, 335, 345, 355, 365 is a storage area for selectively storing information used for searching or display or information having a high utilization rate when acquiring site data. The information system 1 manages the relevance data 100 indicating the relationship between the site data collected or generated in each manufacturing process, and stores the actual site data in the site data stored outside the information system 1. Obtained from Part 4.

As a result, the capacity of the storage device included in the information system 1 can be reduced, but on the other hand, it may take time to search and acquire the on-site data managed externally. Therefore, by directly holding the information with high utilization rate in the site data as extended information in the definition information 300, it is possible to quickly acquire the information necessary for search and display and the information with high utilization rate. it can. Further, information important for managing operation information such as business or parts may be stored in extended information. In this way, it is possible to facilitate the analysis of the operation of the flow of the manufacturing process (line). Further, the information regarding the quality event management data 200 may be stored in the extended information.

The above-mentioned business information and 4M information identification information include information for identifying the product number or serial number that identifies the business specified by these information or the individual or lot of the product related to 4M. For example, the business identification information 311 may be composed of a combination of a product number in which the business is performed, a serial number, and an identifier of the business itself. Alternatively, the correspondence between the business information or 4M information identification information and the product number or serial number is separately held in the master data storage unit 6 or the relevance data storage unit 15, and the product number is obtained from the business or 4M identification information. Alternatively, the serial number may be extracted.

FIG. 5 is a diagram showing an example of the complaint information of FIG.
In FIG. 5, a complaint about a product is received by a call center, a sales department, a quality control department, or the like, is input to the quality event input device 7 of FIG. 1, and is stored as complaint information 210 in the quality event data storage unit 6. The quality event management data acquisition unit 19 of FIG. 2 acquires the complaint information 210 stored in the quality event data storage unit 6 and stores it in the quality event management data storage unit 20.

The complaint information 210 includes a complaint number which is identification information of the complaint, a drafting date and time which is a date and time when the complaint is received or a date and time input to the quality event input device 7, a product number (or product item name) of the product corresponding to the complaint, and the like. Includes product serial number (or lot number), date of manufacture, complaint classification and complaint content.

FIG. 6 is a diagram showing an example of deviation information of FIG.
In FIG. 6, the deviation information 220 is input to the quality event input device 7 by a worker at the manufacturing site, a quality control department, or the like, and is stored in the quality event data storage unit 6. The quality event management data acquisition unit 19 of FIG. 2 acquires the deviation information 220 stored in the quality event data storage unit 6 and stores it in the quality event management data storage unit 20.

Deviation information 220 is information such as deviation behavior or malfunction from the standard work procedure that occurred in the manufacturing process. The deviation information 220 includes a deviation number, an occurrence date and time, a product number, a serial number, an occurrence process, an occurrence of 4M information, a procedure number in which the deviation occurred in the work procedure manual, and an operator, which are identification information of the deviation information 220. Information, deviation content, deviation classification, comments entered by field workers, etc. and information of the person who entered the comment.

FIG. 7 is a diagram showing an example of the change information of FIG.
In FIG. 7, the change is implemented as a corrective measure for a complaint or deviation, and the quality control department or the like inputs the change information 230 to the quality event input device 7. Alternatively, the change is carried out for productivity improvement or maintenance, and the field worker or the like may input the change information 230 to the quality event input device 7. The change information 230 input to the quality event input device 7 is stored in the quality event data storage unit 6. The quality event management data acquisition unit 19 of FIG. 2 acquires the change information 230 and stores it in the quality event management data storage unit 20.

The change information 230 includes the change number, which is the identification information of the change, the draft date and time of the change measure, the application date and time of the change, the completion date and time, the product number to which the change is applied, and the serial number (or lot number) of the product to which the change is first applied. ), Includes details of changes. If the change is implemented as a corrective action, such as a complaint or deviation, the change information 230 also includes the complaint number or deviation number that caused it. The change measures may be affected by the changes made to the 4M of one job (or process), and may have to change the 4M of another job (or process) as well. Therefore, the details of the change information 230 include, in addition to the process that is the main target of the change, 4M information, the content of the change, and the change classification, the information of the change derived by the influence of the change that is the main target.

However, among the information shown as the above quality event management data 200, information other than the minimum information such as the product number, serial number, date and time information, which is an identifier used for searching or displaying the information, is the quality event data storage unit. Stored in 6, the quality event management data 200 may include access information of each quality event data.

FIG. 8 is a diagram showing an example of an operation procedure until the information system of FIG. 1 associates and extracts relevance data and quality event data and provides analysis data to the user. In FIG. 8, the factor analysis of the complaint will be described as an example. Users who use information systems to carry out factor analysis are quality control departments and the like. Alternatively, when the quality control department requests the manufacturing site of each manufacturing process to analyze the cause of the complaint and collects the factor analysis result from the field worker of each manufacturing process, the field worker may be the user.

In the operation procedure of FIG. 8, the user selects the quality event to be analyzed, the information system 1 extracts the relevance data 100 and the quality event data 200 in association with each other according to various search conditions, and the user should confirm. The manufacturing record (ie, field data) is determined, and the information system 1 provides the user with analytical data for performing factor analysis.

Specifically, the user selects an event to be analyzed via the user interface 9 (S101). For example, the user selects or inputs identification information (complaint number) of one or more complaints to be analyzed. The relevance data search unit 12 of the information system 1 searches the complaint information 210 stored in the quality event management data storage unit 20 based on the input complaint identification information (S102).

The relevance data search unit 12 extracts the access information of the quality event data storage unit 6 from the complaint information 210 stored in the quality event management data storage unit 20, and the complaint identification information from the quality event data storage unit 6. The complaint information 210 may be searched based on. In this case, the quality event data storage unit 6 extracts the quality event data (complaint information) corresponding to the identification information (complaint number) received from the relevance data search unit 12 and provides it to the information system 1 (S103).

The information system 1 provides the user interface 9 with the complaint information 210 acquired from the quality event management data storage unit 20 or the quality event data storage unit 6 (S104). As a result, the user can confirm the complaint information 210 of FIG.

The user determines the manufacturing record to be confirmed, that is, the search condition of the site data based on the displayed complaint information, and inputs it to the user interface (S105). For example, the user confirms a series of manufacturing records of the product for which the complaint was made and the quality event related thereto by specifying the product number or the serial number of the product for which the complaint was made as a search condition. can do. Alternatively, as a search condition, the user may specify a manufacturing period before and after the date and time when the product for which the complaint was made was manufactured. As a result, the user can perform factor analysis while comparing the manufacturing status of the product for which the complaint was made with the manufacturing status before and after that, and confirming the change measures taken before the manufacturing of the product. Can be done.

Next, the relevance data search unit 12 of the information system 1 creates a search condition for the relevance data 100 based on the input search condition (S106), and searches for the relevance data (S107). Specifically, the relevance data 100 such as the input product number, serial number, business information corresponding to the manufacturing period, or 4M information is extracted from the relevance data storage unit 15. For example, the relevance data search unit 12 selects a series of manufacturing processes composed of a plurality of businesses and 4M, business information or 4M information identifiers, business information or 4M information data items that can be selected via the user interface 9, and the like. Extract.

Next, the relevance data search unit 12 of the information system 1 creates a search condition for the quality event management data 200 from the search condition input in S105 and the relevance data 100 searched in S107 (S108), and the quality event. The management data 200 and the quality event data are searched (S109). At this time, the relevance data search unit 12 searches for deviation information 220, change information 230, and the like related to the search conditions. The quality event data storage unit 6 provides quality event data based on the conditions received from the information system 1 (S110).

The information system 1 has the relevance data 100 searched from the relevance data storage unit 15 in S106 to S109, the quality event management data 200 acquired from the quality event management data storage unit 20, and the quality provided by the quality event data storage unit 6. Display data is created based on the event data and provided to the user interface 9 (S111). The user interface 9 displays the display data provided in S111 (S112).

Based on the content of the complaint to be analyzed and the quality event data displayed in S112, the user should confirm the work to be confirmed in order to identify the cause of the complaint, 4M and the field data associated with the work or 4M. The data item is determined, and the data item to be confirmed on the user interface 9 is selected (S113).

The relevance data search unit 12 creates a search condition for site data based on the selected data item information and the relevance data information searched in S107 (S114). Then, the relevance data search unit 12 stores the site data via the accumulation data acquisition unit 13 based on the access information to the site data acquired from the relevance data storage unit 15 according to the search conditions of the site data. The site data accumulated in the part 4 is searched (S115).

The site data storage unit 4 extracts the site data corresponding to the search condition notified from the storage data acquisition unit 13 and provides it to the storage data acquisition unit 13 of the information system 1 (S116). The information system 1 creates analysis data based on the site data and the relevance data 100 provided by the site data storage unit 4, and provides the data to the user interface 9 (S117).

FIG. 9 is a diagram showing an example of an operation procedure from the user analyzing the root cause of the quality event to registering the analysis information in the information system of FIG. The operation procedure of FIG. 9 is carried out following the operation procedure of FIG.
In the operation procedure of FIG. 9, the user confirms the analysis data provided from the information system 1 via the user interface 9, analyzes the root cause of the quality event (here, the complaint), and converts the analysis information into the information system 1. Register with.

Specifically, the user confirms the site data by various methods based on the analysis data provided by the information system 1 in S117 of FIG. 8, and analyzes the cause of the complaint (S118). For example, the user confirms machine operation data, work records, work procedure manual information, and the like, and analyzes the presence or absence of a phenomenon (that is, doubt) that causes a complaint.

Then, the user inputs the execution result of the analysis into the user interface 9 (S119). For example, the user inputs the presence or absence of suspicion of the confirmed site data or the reason for determining the presence or absence of suspicion. When the cause of the complaint cannot be identified, the user confirms other business information or 4M information or other business information or 4M information of the process, and repeats the procedures S105 to S119 (S120).

When the root cause of the complaint can be identified, the user inputs the root cause information into the information system 1 from the user interface 9 (S121). However, if the root cause cannot be identified, the user may enter information that will conclude the analysis result. When all the analyzes are completed, the user registers the analysis results from the user interface 9 (S122).

The information system 1 is registered in the quality event management data storage unit 20 in association with the analysis result information registered from the user interface 9, the analyzed relevance data 100, the site data, and the complaint information 210 subject to analysis. (S123).

FIG. 10 is a diagram showing an example of factor analysis results registered in the quality event management data storage unit of FIG.
In FIG. 10, the factor analysis result is registered in the quality event management data storage unit 20 at 123 or the like in FIG. Factor analysis results include identifiers (complaint numbers or deviation numbers) of quality events that are the subject of factor analysis, such as complaints or deviations, root cause information, analysis worker information, and factor analysis process information.

The root cause information includes, for example, information on the process determined to be the root cause or 4M, and a comment indicating the reason determined to be the root cause.

The information of the analysis process is the information of the process in which the user confirms the site data by the procedure shown in FIGS. 8 and 9 and identifies the cause of the occurrence of the quality event. Information on the analysis process is analyzed by, for example, search conditions for manufacturing records, selected manufacturing records (that is, site data), presence / absence of doubt (status), comments indicating the reason for determining the presence / absence of doubt, and external application 8. It is an analysis file (attached file) when it is done.

When multiple analyzes are performed with the unit for which the analysis was performed (that is, the unit for which S105 to S119 of FIGS. 8 and 9 are performed) as one group, the information of the analysis process of the multiple times is the factor analysis result. It is accumulated in the information of. The information of the analysis process of a plurality of times is registered in the quality event management data storage unit 20 of FIG. 2 as, for example, the survey result No1 and the survey result No2. When analysis results are collected from multiple departments or workers, and the quality control department or the person in charge determines the final root cause based on the information, the analysis worker information is provided for each survey result. May be registered.

The information system 1 of FIG. 2 stores the information of the factor analysis result of FIG. 10 in the quality event management data storage unit 20, and manages the quality event data, the manufacturing record, the analysis process, and the information of the reason for the determination in association with each other. Can be extracted.

For example, the information of the factor analysis result is associated with the complaint information 210 of FIG. 5 or the deviation information 220 of FIG. 6 by using the complaint number or the deviation number as a key. Further, using the information such as the product number, the serial number, the date and time information stored in the complaint information 210 or the deviation information 220, the process determined to be the root cause, and the 4M information as keys, the information of the factor analysis result and the manufacturing The record is associated with complaint information 210 or deviation information 220. In addition, the information of the factor analysis result can include the reason for determining the root cause of the quality event such as a complaint or deviation and the information of the analysis process leading to the identification of the root cause together with the information of the analysis worker.

Therefore, it is possible to share the manufacturing record and the reason for judgment confirmed before identifying the cause of each quality event with other analysis workers. Furthermore, the know-how of factor analysis of quality events can be converted into data by statistically processing the information of the analysis result for each analysis worker or learning by machine learning or the like. For example, it is possible to quantify the difference in the confirmed data and the difference in the number of analyzes performed to reach the root cause between the case of analysis by a skilled technician and the case of analysis by an inexperienced technician. it can.

FIG. 11 is a diagram showing an example of an analysis screen in which the user confirms the quality event data and selects and extracts the site data.
In FIG. 11, the user interface 9 of FIG. 8 displays the analysis screen 40 on S112 or the like. On the analysis screen 40, the user confirms quality event data and the like according to the search conditions, and selects and extracts on-site data which is a manufacturing record.

The analysis screen 40 includes an area 400 for displaying the quality event to be analyzed, an area 410 for inputting search conditions, and an area 420 for displaying the manufacturing process (business information and 4M information) and the quality event associated with the manufacturing process. , Includes area 430 for displaying quality event data and the like.

Information indicating a quality event to be analyzed is displayed or input in the area 400. FIG. 11 shows an example in which the complaint number to be analyzed is displayed. For example, when the user selects (clicks) the complaint number, the user interface 9 may display the complaint information 210 of FIG. 5 associated with the complaint number on a pop-up screen or the like.

In the area 410, search conditions for searching the site data which is the manufacturing record and the quality event data associated with the site data are input. FIG. 11 shows an example in which a product number, a serial number, a manufacturing period, and the like are displayed as search conditions.

In the area 420, a series of manufacturing processes of products matching the conditions entered in the search conditions are displayed based on the business of FIG. 3 and the relevance data 100 of 4M. In FIG. 11, there are three business nodes of business 1 to 3 as a product manufacturing process, and procedures 1 to 3, workers 1 to 3, machines 1 to 3 and parts 1 to 3 as 4M information related to each business. The node of the product 4 and the node of the finished product 4 as the final product are displayed.

In addition, the number of quality event data associated with each business information or 4M information is displayed in the form of a balloon. In FIG. 11, there are 2 changes corresponding to the search conditions in the

business

1 and 3 cases in the

business

2, and 2 deviations corresponding to the search conditions in the

business

1 and 2 cases in the business 3. An example is shown. Further, in FIG. 11, in another complaint of the product corresponding to the search condition, one case was the root cause of the 4M of the business 1 or the business 1, and the case was the root cause of the 4M of the business 3 or the business 3. An example is shown in which two cases occur. In S113 of FIG. 8, the user can extract the site data related to the business and 4M by selecting the business node and the 4M node in the area 420.

In the area 430, detailed information of the quality event data displayed in the balloon in the area 420 is displayed. In FIG. 11, as quality event data related to business 1, two change information 230s are displayed in the area 431, two deviation information 220s are displayed in the area 432, and one complaint information 210 is displayed in the area 433. The displayed example is shown. At this time, each quality event data is grouped by 4M classification and displayed in the area 430.

Here, the change information 230 has information on related complaints for the first change information, but no information on related complaints for the second change information. This indicates that the first change information is a change implemented as a corrective measure for a complaint, and the second change information is a change implemented to improve productivity, etc. ..

Note that the area 430 may display quality event data related to all operations that meet the search conditions. Further, the information of the areas 431 to 433 may be displayed when each balloon in the area 420 is clicked, or may be displayed in a pop-up format on another screen.

Here, in FIG. 11, the number of all quality event data is displayed around the business node, and the classification of 4M is shown in the details of each quality event data in the area 430. The number of quality event data corresponding to each 4M may be displayed around the 4M node.

Further, in FIG. 11, an example in which the number of quality event data is displayed in the balloon in the area 420 is shown, but other information may be displayed. For example, the number of comments left by the worker at the manufacturing stage may be displayed. Alternatively, characteristic information may be extracted from the site data or the relevance data and displayed in a balloon. For example, if you want to intuitively understand whether multiple tasks have occurred due to rework in each task, the number of times each task has been executed or passed (if multiple products meet the search conditions). , The average number of times) may be displayed, or the time (or average time) taken for each work may be displayed.

As shown in FIG. 11, by visually displaying the quality event data related to each operation and 4M in a series of manufacturing processes, it is easy to analogize the operations and 4M that can cause quality events (for example, complaints). Become. For example, if it can be understood that the product for which a complaint has occurred is a product manufactured immediately after changing the work procedure of work 1, it can be inferred that the changed work procedure was inadequate, or the worker was changed. It can be inferred that there is a high possibility that a problem has occurred because he was unfamiliar with the work procedure. Based on this information, the user, that is, the analyst, can select from the most suspicious business site data and check the details, thereby reducing the time and man-hours required to reach the root cause.

FIG. 12 is a diagram showing an example of a screen for registering the process and result of factor analysis of quality events based on the confirmed field data.
In FIG. 12, the user interface 9 of FIG. 8 displays the registration screen 41 at S119, S121, S122, or the like of FIG. On the registration screen 41, the user registers the process and result of the factor analysis of the quality event based on the confirmed site data. The registration screen 41 includes

areas

400, 410, and 420, similar to the analysis screen 40 of FIG. In addition, the registration screen 41 includes an area 440 for registering the process of factor analysis and an area 450 for inputting root cause information identified as a result of the factor analysis.

In the area 440, the search conditions of the area 410 and the information of the site data selected in the area 420 (that is, the information corresponding to the search history of the manufacturing record or the utilization history of the information system 1) are displayed in advance. Further, the area 440 is provided with an area for inputting the survey result of investigating whether the corresponding work or 4M is a factor of the quality event from the confirmed site data. Specifically, the area for inputting the survey results is provided with a comment field for inputting the presence or absence of doubt as a cause of the quality event, a comment field for inputting the judgment criteria, and an area for attaching the file used for the analysis. These survey results are input for each group of data items of site data confirmed in units such as for each process.

Each time the user inputs the survey result into the area 440, the already confirmed work of the field data or 4M and its data item may be displayed so as to be visually understood in the area 420. For example, the already confirmed business node or 4M node may be grayed out or highlighted, or the data item name displayed when each business or 4M is selected may be colored. As a result, the user can proceed with the factor analysis while easily grasping how much on-site data has been confirmed in the analysis process.

The area 450 includes an area for inputting the business or 4M information that caused the root cause and an area for inputting the reason determined to be the root cause as a comment. However, the area for inputting the business or 4M information that caused the root cause may be configured to be selected from the selected data analyzed in the area 440. In that case, the data to be selected may be limited to the survey results judged to be suspicious.

In addition, the registration button 451 is displayed in the area 450. When the registration button 451 is pressed, the information and the root cause of the series of factor analysis processes of FIG. 10 are registered in the quality event management data storage unit 20 together with the quality event identifier.

However, when multiple analysis workers perform factor analysis of quality events and the quality control department or the person in charge determines the root cause based on the information, each analysis worker is in area 440. It may be registered by inputting, or information indicating the conclusion of performing the factor analysis of each analysis worker may be input to the area 450. Further, if there is a survey result already registered by another analysis worker or the like for the same quality event, it may be displayed in the area 440 or the like.

Further, for example, the root cause may be input only by the quality control department or the person in charge, and other workers may input only the survey result, and the information that can be input may be limited for each user. Alternatively, the information displayed for each user may be different, such as allowing only the quality control department or the person in charge to check the survey results entered by other analysts.

FIG. 13 is a diagram showing an example of a screen for searching and extracting information on the registered factor analysis process and past quality events.
In FIG. 13, the user interface 9 of FIG. 8 displays the quality event data search screen 50 in S201 or S202 of FIG. On the search screen 50, the user performs a search operation for information on the factor analysis process registered on the registration screen 41 or the like in FIG. 12 or quality event data such as complaints or changes that have occurred in the past.

The search screen 50 is, for example, an area 500 for inputting search conditions for quality events, an area 510 for inputting search conditions for manufacturing records, an area 520 for displaying a series of manufacturing processes and operations, and quality events associated with 4M, and quality. Includes area 530 and the like for displaying event details.

FIG. 13 illustrates a case where a search for complaint information is performed. In the area 500, the user selects or inputs a complaint as an event classification, and inputs a product number, a complaint identifier, or a period during which a quality event is drafted as a search condition for complaint information. In addition, the user may input a typical complaint classification (in-event classification) such as damage or failure, a process (business) to be searched, or 4M.

The information system 1 in FIG. 2 searches for complaints based on the input conditions, totals the number of complaints that meet the search conditions for each business, and displays it in the area 520 as a balloon of the cause of the complaint. In addition, the user can input the search condition of the manufacturing record in the area 510 to search the manufacturing record. When the information system 1 searches the manufacturing record, it extracts the relevance data corresponding to the search conditions of the manufacturing record, and also extracts other quality events (changes and deviations) related to the manufacturing record. , The number of changes and deviations is totaled and displayed as a change and deviation balloon.

The information system 1 may extract only the manufacturing record and the relevance data from the search conditions input in the area 510, and search for quality events according to the search conditions in the area 500. In this case, for example, a plurality of quality event classifications may be selected in the region 500.

Details of each quality event data are displayed in area 530. Alternatively, when the user clicks the balloon in the area 520, the details of the corresponding quality event data are displayed in the area 530. At this time, information on the factor analysis process of the complaint registered in FIG. 12 is also displayed in the

areas

531 and 532.

Further, the change information 230 in FIG. 7 includes not only the information that is the main target of the change but also the information of the change derived by the influence of the change that is the main target. In this case, the change of the business 1 is the main target, and the change information of the business 1 in the area 520 and the change information of the business 2 are displayed in order to visually indicate that the change of the business 2 has been implemented as a derivative change thereof. You may connect it with the balloon of. In this way, the information system 1 visually expresses the relevance of the past changes, so that the user can easily grasp what kind of business has affected when considering the implementation of the changes. can do.

FIG. 14 is a diagram showing an example of an operation procedure in which the information system of FIG. 1 searches for quality events.
In FIG. 14, the user searches for quality event data via the user interface 9 using the search screen 50 of FIG. 13 and the like.

Specifically, the user inputs the search condition of the quality event and the search condition of the manufacturing record from the user interface 9 and performs the search (S201, S202, S203). The relevance data search unit 12 of the information system 1 determines a search scenario based on the input search conditions, information on which screen the information was input from, and the like (S204). The search scenario shows the classification of the quality event that searches only the quality event data according to the search condition of the quality event and the quality event that is extracted together with the manufacturing record according to the search condition of the manufacturing record.

For example, in the search on the analysis screen 40 of FIG. 11, the information system 1 searches for change information 230, deviation information 220, complaint information 210, and the like related to the manufacturing record according to the search conditions of the manufacturing record.

On the other hand, in the search on the search screen 50 of FIG. 13, the information system 1 searches only the quality event data corresponding to the input event classification according to the search condition of the quality event input in the area 500, and searches the area 510. Search for other quality event data according to the search conditions of the manufacturing record entered in. The information system 1 may search the quality event data only according to the search conditions input in the area 500.

The relevance data search unit 12 of FIG. 2 determines the search conditions for the quality event alone according to the search scenario determined in S204, and searches the quality event management data storage unit 20 (S205). The relevance data search unit 12 extracts quality event data from the quality event data storage unit 6 as needed. The quality event data storage unit 6 provides the quality event data in response to the notification from the information system 1 (S206).

Next, the relevance data search unit 12 determines the search conditions for quality events to be extracted together with the manufacturing record, and searches the relevance data storage unit 15 and the quality event management data storage unit 20 (S207).

Similarly, the relevance data search unit 12 extracts the quality event data from the quality event data storage unit 6 as needed, and the quality event data storage unit 6 provides the quality event data (S208). The information system 1 aggregates the extracted quality event management data 200 and the number of quality event data for each business or 4M, creates display data, and provides it to the user interface 9 (S209). The user interface 9 displays the display data received from the information system 1 (S210).

Hereinafter, an example of the operation procedure of the information system 1 in the case of searching the quality event data alone or the quality event data associated with the manufacturing record will be described. Since this operation procedure differs depending on the management method of the quality event management data 200, a typical example will be described below.

FIG. 15 is a diagram showing an example of a quality event search procedure when the information system according to the second embodiment manages manufacturing records and quality event management data in different storage units.
In FIG. 15, it is assumed that the on-site data, the relevance data 100, and the quality event management data 200, which are manufacturing records, are managed in different storage units. At this time, the information system 1 searches for quality event data according to the following procedure.

That is, the information system 1 receives the search condition input by the user via the user interface 9 (S301). Then, the information system 1 determines the search scenario according to the received search condition or the screen used for the input (S302). Specifically, the quality event to be searched independently and the quality event to be searched in relation to the manufacturing record are determined.

Next, the information system 1 searches the quality event management data storage unit 20 using the quality event search condition as a key (S303). Here, the search condition of the quality event is, for example, the identifier of the quality event, the product number, the period of the drafting date, etc. shown in the area 500 of FIG. 13, and is shown in FIGS. 5, 6, 7, and 10. Any information contained in the quality event management data. Therefore, in the search for quality events, the information system 1 may search for quality events that include information that matches the search conditions for quality events.

Next, the information system 1 searches for quality events related to the manufacturing record based on the search conditions of the manufacturing record. At this time, depending on the entered search conditions, it may not be possible to identify the quality event. For example, suppose that a product number and a manufacturing period are input as search conditions for manufacturing records. In this case, the manufacturing date of the product, which is the end date of the final work of the manufacturing process, and the execution date of other work may be different. Therefore, for example, the deviation information 220 of FIG. I can't search.

Therefore, the information system 1 determines whether or not the serial number is included in the search condition of the manufacturing record (S304). If the serial number is included in the search condition of the manufacturing record (Yes in S304), the process proceeds to S307.

On the other hand, when the serial number is not included in the search condition of the manufacturing record (No in S304), the information system 1 uses the product number and the manufacturing period (that is, the end date and time of the final manufacturing operation) as keys as the key to the relevance data storage unit 15. Is searched (S305). Then, the serial number is extracted from the identification information of the extracted relevance data (for example, business identification information 311 or finished product identification information 341) (S306). Here, a plurality of serial numbers may be extracted.

Next, the information system 1 searches the quality event management data storage unit 20 for the quality event associated with the manufacturing record using the product number and the manufacturing number as keys (S307). The information system 1 aggregates the respective quality event management data 200 or quality event data extracted in S303 or S307 for each business and 4M included in the quality event management data 200 (S308), and FIGS. 11, 12, and 12 and As shown in FIG. 13, it is created as a numerical value in the balloon and provided to the user interface 9 as display data together with the details of the quality event data (S309).

FIG. 16 is a diagram showing an example of a quality event search procedure when the information system according to the third embodiment manages quality event management data as extended information of definition information of relevance data.
In FIG. 16, it is assumed that the information system 1 manages the quality event management data 200 as extended information of the definition information 300 of the relevance data 100 of FIG. In this case, the quality event management data storage unit 20 becomes a part of the relevance data storage unit 15. For example, the complaint information 210 is stored in the extended information 345 of the finished product of the product that is the subject of the complaint or the extended information of 4M that caused the root cause. The deviation information 220 is stored in the extended information of 4M in which the deviation has occurred. The change information 230 is stored in the extended information of 4M in which the change has been made. At this time, the information system 1 searches for quality event data according to the following procedure.

That is, the information system 1 performs the same processing as S301 and S302 in FIG. 15 (S401, S402). Next, the information system 1 searches the extended information of the relevance data 100 using the search condition of the quality event as a key (S403). Specifically, the information system 1 searches all the business and the extended information of the 4M relevance data 100 including the information input in the search condition of the quality event.

Similarly, the information system 1 searches the relevance data 100 based on the search conditions of the manufacturing record. At that time, the information system 1 extracts the information including the quality event management data 200 in each business or 4M extended information (S404). Then, the information system 1 aggregates the number of each quality event data for each business and 4M (S405) and provides it to the user interface 9 as display data together with detailed information, as in S308 and S309 of FIG. 15 (S405). S406).

FIG. 17 is a diagram showing an example of a quality event search procedure when the information system according to the fourth embodiment defines and manages quality event management data as a node of relevance data.
In FIG. 17, it is assumed that the information system 1 defines and manages the quality event management data 200 as a node of the relevance data 100. In this case, each quality event is defined in the relevance data storage unit 6 as a node similar to the business information or 4M information, and the information of the quality event management data 200 is managed as the definition information 300. Then, each quality event is connected to the related 4M node as a directed graph. In this case, the quality event management data storage unit 20 may be a part of the relevance data storage unit 15. Further, the relevance data 100 may store only the identification information of the quality event, and may include the information of the quality event management data storage unit 20 as the access information to the other quality event management data 200. At this time, the information system 1 searches for quality event data according to the following procedure.

That is, the information system 1 performs the same processing as S301 and S302 in FIG. 15 (S501, S502). Next, the information system 1 searches for the node of the quality event of the relevance data 100 using the search condition of the quality event as a key (S503).

Next, the information system 1 searches the relevance data 100 based on the search conditions of the manufacturing record. At that time, the information system 1 extracts the node of the quality event connected to the extracted 4M node (S504). Then, similarly to S308 and S309 of FIG. 15, the information system 1 aggregates the number of each quality event data for each business or 4M (S505) and provides it to the user interface 9 as display data together with detailed information (S505). S506).

As described above, according to the above-described embodiment, the information system 1 has information on defects or deviations that occurred in the manufacturing stage, information on complaints about products, corrective action, information on changes implemented for productivity improvement, and the like. Since the information on the quality event and the manufacturing record can be extracted and displayed in association with each other, it is possible to quickly identify the cause of the defect that has occurred.

Further, since the information system 1 can extract and display the manufacturing record (that is, search history or usage history) confirmed up to the identification of the factor, the quality event, the factor, and the changed implementation, the quality event can be displayed. It is possible to share the know-how of factor analysis and corrective measures for the disease with others, and it is possible to facilitate the understanding of the range of influence of factor analysis and corrective measures. As a result, it is possible to speed up the response to complaints or inquiries received at the call center, etc., and to speed up the response to defects, which is expected to have effects such as improvement in productivity.

FIG. 18 is a block diagram showing a hardware configuration example of the information system of FIG.
In FIG. 18, the information system 1 includes a processor 51, a communication control device 52, a communication interface 53, a main storage device 54, an auxiliary storage device 55, and an input / output interface 57. The processor 51, the communication control device 52, the communication interface 53, the main storage device 54, the auxiliary storage device 55, and the input / output interface 57 are connected to each other via the internal bus 56. The main storage device 54 and the auxiliary storage device 55 are accessible from the processor 51.

Further, an input device 60 and an output device 61 are provided outside the information system 1. The input device 60 and the output device 61 are connected to the internal bus 56 via the input / output interface 57. The input device 60 is, for example, a keyboard, a mouse, a touch panel, a card reader, a voice input device, or the like. The output device 61 is, for example, a screen display device (liquid crystal monitor, organic EL (Electro Luminescence) display, graphic card, etc.), an audio output device (speaker, etc.), a printing device, or the like.

The processor 51 is hardware that controls the operation of the entire information system 1. The processor 51 may be a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The processor 51 may be a single-core processor or a multi-core processor. The processor 51 may include a hardware circuit (for example, FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs a part or all of the processing. The processor 51 may include a neural network.

The main storage device 54 can be composed of, for example, a semiconductor memory such as SRAM or DRAM. The main storage device 54 can store a program being executed by the processor 51, or can provide a work area for the processor 51 to execute the program.

The auxiliary storage device 55 is a storage device having a large storage capacity, and is, for example, a hard disk device or an SSD (Solid State Drive). The auxiliary storage device 55 can hold an executable file of various programs and data used for executing the program. The information management program 55A can be stored in the auxiliary storage device 55. A part of the information management program 55A or one or more of the processing units shown in FIG. 2 is software that can be installed in the information system 1 from another device via a communication line or a non-temporary storage medium. It may be, or it may be incorporated as firmware in the information system 1.

The communication control device 52 is hardware having a function of controlling communication with the outside. The communication control device 52 is connected to the network 59 via the communication interface 53. The network 59 may be a WAN (Wide Area Network) such as the Internet, a LAN (Local Area Network) such as Wi-Fi (registered trademark) or Ethernet (registered trademark), or a WAN. LANs may be mixed.

The input / output interface 57 converts the data input from the input device 60 into a data format that can be processed by the processor 51, and converts the data output from the processor 51 into a data format that can be processed by the output device 61. ..

The processor 51 reads the information management program 55A into the main storage device 54 and executes the information management program 55A to obtain information on the execution of the business, information on the quality event of the business, and the execution of the business searched for on the quality event. The cause of the quality event identified based on the manufacturing record and the quality event data by associating and holding the information search history, and the manufacturing record confirmed before the identification of the factor or the reason for identifying the factor. Can be associated and extracted and displayed on the output device 61. At this time, the information management program 55A includes the relevance data model creation unit 10 of FIG. 2, the relevance data registration unit 11, the relevance data search unit 12, the accumulated data acquisition unit 13, and the data provision API unit 16. , The function of the quality event management data acquisition unit 19 can be realized.

Note that the execution of the information management program 55A may be shared by a plurality of processors and computers. Alternatively, the processor 51 may instruct a cloud computer or the like to execute all or a part of the information management program 55A via the network 59, and may receive the execution result.

In the above-described embodiment, an example in which the information system 1 is applied when collecting and displaying on-site data generated in each manufacturing process in a manufacturing factory and quality event data related to manufactured products has been described. Is not limited to manufacturing factories, but is composed of multiple operations and can be applied to any type of business in which quality events occur.

For example, in the logistics industry or the transportation industry, there are a plurality of operations that constitute a transportation process from the arrival of packages to sorting, storage, packing, and delivery. Then, changes in work procedures, equipment, workers, etc. related to each work can be managed in the same manner as change information in the manufacturing process. In addition, complaints or inquiries regarding the delivery of packages can be managed in the same way as complaint information, and defects that occur in each business can be managed in the same way as deviation information.

Similarly, in the retail or service industry, a series of business processes can be defined as business information and business-related information, and changes, defects, complaints, etc. in each business can be managed in the same way as the manufacturing process. Therefore, the information system 1 can manage and display business information of various industries, business-related information, and quality event information in association with each other, and as a result, in a wide variety of industries, it is possible to quickly identify factors for quality events. It is possible to grasp the range of influence of the change and corrective measures, and to share the analysis know-how up to the identification of the factors.

The present invention is not limited to the above-described embodiment, and includes various modifications. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, it is possible to add / delete / replace a part of the configuration of each embodiment with another configuration. Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit.

1 ... Information system, 4 ... Field data storage unit, 5a-5c ... Data generator, 6 ... Quality event data storage unit, 9 ... User interface, 10 ... Relevance data model creation unit, 11 ... Relevance data registration unit, 12 ... Relevance data search unit, 13 ... Accumulated data acquisition unit, 14 ... Analytical data storage unit, 15 ... Relevance data storage unit, 16 ... Data provision API unit, 17 ... Control data definition unit, 18 ... Temporary storage unit , 19 ... Quality event management data acquisition unit, 20 ... Quality event management data storage unit, 100 ... Relevance data, 110 ... Business node, 120 ... Parts node, 130 ... Worker node, 140 ... Machine node, 150 ... Finished product Node, 160 ... Work procedure node, 200 ... Quality event management data, 210 ... Complaint information, 220 ... Deviation information, 230 ... Change information, 300 ... Definition information

Claims

Equipped with a computer-readable storage unit
The storage unit is an information system that stores information on business execution, information on quality events of the business, and information on analysis processes related to the quality events in association with each other.
Further equipped with a processor accessible to the storage unit
The information system according to claim 1, wherein the processor extracts and displays information on the execution of the business and information on quality events of the business associated with the information on the performance of the business according to a search condition.
The information system according to claim 1, wherein the information regarding the execution of the business includes business information that identifies the business and business-related information related to the business.
The information system according to claim 3, wherein the information related to the quality event is associated with business information or business-related information related to the quality event, or is associated with business information or business-related information related to the factor of the quality event. ..
The information system according to claim 3, wherein the business-related information includes at least one of worker information, machine information, parts information, and work procedure information associated with the business information.
Information on the quality event
Includes at least one of complaint information about the business, inquiries about the business, and information about defects that occurred in the business.
The information system according to claim 3, which is associated with business-related information related to the cause of the quality event.
A search unit for inputting search conditions for information related to the execution of the above-mentioned business,
A providing unit that extracts, displays, or provides the business information, the business-related information, and the quality event associated with the business information or the business-related information according to the search conditions input to the search unit. ,
It is equipped with an input unit for inputting the investigation results of the factors of the quality event.
In the input unit, information on the determination result and the reason for determining whether or not the business information or the business-related information displayed or provided by the providing unit is a factor of the quality event is input.
The business information or the business-related information displayed or provided by the providing unit, the determination result and the reason for determining whether or not the cause is the quality event input to the input unit, and the identification information of the quality event. The information system according to claim 3, wherein the information system is associated and recorded.
Information on the quality event
Contains information on changes to or related to the work
The information system according to claim 3, which is associated with business information or business-related information related to the change measures.
The information regarding the quality event includes at least one of information on a complaint about the business, information on an inquiry about the business, and information on a defect that has occurred in the business.
The information system according to claim 8, wherein when the change measure is implemented due to the complaint, the inquiry or the defect, the change measure is stored in association with the complaint, the inquiry or the defect.
The information on the change measures is carried out by the information on the first change measure for the first work or related to the first work and the information for the second work or in relation to the second work by the first change measure. Including information on the second amendment made
The information system according to claim 8, wherein the business information or business-related information associated with the first modification measure and the business information or business-related information associated with the second modification measure are displayed in association with each other.
The business information has a first identification information that identifies the business, and has
The business-related information has a second identification information that identifies an object related to the execution of the business.
The information regarding the quality event is associated with the business information or the business-related information related to the quality event based on the first identification information or the second identification information, or the business information related to the factor of the quality event. Or the information system according to claim 3, which is associated with business-related information.
A claim that the information about the quality event is associated as an information element of business information or business-related information related to the quality event, or as an information element of business information or business-related information related to the factor of the quality event. The information system according to 3.
The business information, the business-related information, and the information related to the quality event are recorded in the same storage device.
The business information, business-related information, and information related to the quality event are defined as information elements, respectively.
The information system according to claim 3, wherein the business information or the business-related information is associated with the information related to the quality event by connecting the information elements with a connecting line.
An information management method including a storage unit that can be read by a computer and a processor that can access the storage unit.
The storage unit holds information on the execution of the business, information on the quality event of the business, and information on the analysis process related to the quality event in association with each other.
An information management method in which the processor extracts and displays information on the execution of the business and information on a quality event associated with the information on the performance of the business according to a search condition.
The information management method according to claim 14, wherein the information relating to the execution of the business includes business information specifying the business and business-related information related to the business.