[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2016189603A1 - Procédé et système d'assistance à l'optimisation d'opération - Google Patents

Procédé et système d'assistance à l'optimisation d'opération Download PDF

Info

Publication number
WO2016189603A1
WO2016189603A1 PCT/JP2015/064830 JP2015064830W WO2016189603A1 WO 2016189603 A1 WO2016189603 A1 WO 2016189603A1 JP 2015064830 W JP2015064830 W JP 2015064830W WO 2016189603 A1 WO2016189603 A1 WO 2016189603A1
Authority
WO
WIPO (PCT)
Prior art keywords
production
machine
risk
plan
countermeasure
Prior art date
Application number
PCT/JP2015/064830
Other languages
English (en)
Japanese (ja)
Inventor
角谷 有司
野口 純司
眞見 山崎
藤城 孝宏
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2015/064830 priority Critical patent/WO2016189603A1/fr
Priority to JP2017520080A priority patent/JP6553720B2/ja
Publication of WO2016189603A1 publication Critical patent/WO2016189603A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention relates to an operation optimization support system and an operation optimization support method, and is suitable for application to an operation optimization support system and an operation optimization support method that support machine operation optimization at the time of detection of a machine failure sign. is there.
  • the present invention has been made in view of the above points, and is an operation optimization support system and operation optimization capable of presenting countermeasures against failure signs detected based on production / operation plans and machine operation risks. It is intended to propose a support method.
  • a machine a production / operation management apparatus that manages production / operation of the machine, a production / operation planning apparatus that plans production / operation of the machine, A maintenance management device that manages operating states and operational risks, wherein the maintenance management device detects a failure sign of the machine, and the production / operation management device manages the production / operation planning device.
  • an operation optimization support system that creates a countermeasure plan for a failure sign detected by the maintenance management device using the operation plan and the operation risk managed by the maintenance management device.
  • a machine a production / operation management apparatus that manages production / operation of the machine, a production / operation planning apparatus that plans production / operation of the machine,
  • An operation optimization support method in an operation optimization support system having a maintenance management device for managing an operation state and an operation risk, wherein the maintenance management device detects a failure sign of the machine,
  • the operation management device uses the production / operation plan managed by the production / operation planning device and the operation risk managed by the maintenance management device to create a countermeasure plan for the failure sign detected by the maintenance management device.
  • the operation optimization support method characterized by including a step.
  • the present invention it is possible to present a countermeasure against a failure sign detected based on a production / operation plan and a machine operation risk, thereby reducing the failure risk of the target device.
  • FIG. 1 shows the structural example of the operation optimization assistance system concerning the 1st Embodiment of this invention. It is a figure which illustrates schematic structure of the production and operation management apparatus concerning the embodiment. It is a figure which illustrates schematic structure of the production / operation plan apparatus concerning the embodiment. It is a figure which illustrates schematic structure of the maintenance management apparatus concerning the embodiment. It is a figure which shows the structural example of the production / operation condition management table concerning the embodiment. It is a figure which shows the structural example of the countermeasure candidate management table concerning the embodiment. It is a figure which shows the structural example of the production / operation capability management table concerning the embodiment. It is a figure which shows the structural example of the production / operation plan management table concerning the embodiment.
  • FIG. 1 It is a figure which shows the example of presentation of the countermeasure plan concerning the embodiment. It is a figure which illustrates schematic structure of the quality assurance apparatus concerning the 2nd Embodiment of this invention. It is a figure which shows the structural example of the FMEA management table concerning the embodiment. It is a figure which shows the structural example of the sign corresponding
  • FIG. 1 is a diagram illustrating a configuration example of an operation optimization support system according to the present embodiment.
  • the operation optimization support system includes machines E001, E002, and E003 that execute production and operation, a production and operation management device A001 that manages production and operation of the machine, and a production and operation planning device that plans production and operation of the machine.
  • These devices can transmit / receive information to / from each other via the network N001. it can.
  • the quality assurance device A003 will be described in detail in the second embodiment.
  • the maintenance management device A003 detects a failure sign of the machine E001. Then, the production / operation management device A001 creates a countermeasure plan for the failure sign by using the production / operation plan managed by the production / operation planning device A002 and the machine operation risk managed by the maintenance management device A003, to the user. Present.
  • FIG. 2 is a diagram illustrating a schematic configuration of the production / operation management apparatus A001.
  • the production / operation management apparatus A001 includes a CPU 101, a memory 102, a storage device 103, a user interface 104, a communication interface 105, a production / operation condition management unit 111, and a countermeasure candidate management unit. 112, a countermeasure plan creation unit 113, and a countermeasure execution unit 114, which are designed to be able to transmit and receive each other via the internal bus 100.
  • the CPU 101 is a central processing unit that performs various numerical calculations, information processing, device control, and the like.
  • the memory 102 is a semiconductor storage device such as a RAM and a ROM that can be directly read and written by the CPU 101.
  • the storage device 103 is a hard disk, magnetic tape, flash memory, or the like that stores data and programs in the computer.
  • the user interface 104 is a device such as a display, a mouse, or a keyboard for outputting a processing result to the user and receiving a user instruction and reflecting it on each component of the production / operation management apparatus A001.
  • the communication interface 105 is a device for controlling transmission / reception of data via the network N001 of each component of the production / operation management device A001.
  • the communication interface 105 performs authentication processing with the other party to establish a communication path, and controls such as disconnecting the communication path after completion of the process or when there is no response from the other party even after a predetermined time has elapsed. I do.
  • the production / operation condition management unit 111 is a device that registers the production / operation conditions stored in the memory 102 or the storage device 103 in the production / operation condition management table T130 and performs processing such as updating. Details of the production / operation condition management table T130 will be described later.
  • the countermeasure candidate management unit 112 is an apparatus that registers countermeasure candidates stored in the memory 102 or the storage device 103 in the countermeasure candidate management table T140 and performs processing such as updating. Details of the countermeasure candidate management table T140 will be described later.
  • the countermeasure plan creation unit 113 includes a production / operation condition (obtained from the production / operation condition management unit 111), a countermeasure candidate (obtained from the countermeasure candidate management unit 112), and a production stored in the memory 102 or the storage device 103.
  • the measure execution unit 114 is a device that executes a measure selected from the measure plan (obtained from the measure plan creation unit 113) stored in the memory 102 or the storage device 103.
  • each device may execute processing alone or each device. May comprise only a program, and the CPU 101 may read the program into the memory 102 and execute it.
  • FIG. 3 is a diagram illustrating a schematic configuration of the production / operation planning apparatus A002.
  • the production / operation planning apparatus A002 includes a CPU 201, a memory 202, a storage device 203, a user interface 204, a communication interface 205, a production / operation capability management unit 211, and a production / operation plan.
  • a management unit 212 and a production / operation plan creation unit 213 are provided, and are designed to be able to transmit and receive each other via the internal bus 200.
  • the production / operation capability management unit 211 is a device that registers the production / operation capability stored in the memory 202 or the storage device 203 in the production / operation capability management table T230 and performs processing such as updating. Details of the production / operation capacity management table T230 will be described later.
  • the production / operation plan management unit 212 is a device that registers the production / operation plan stored in the memory 202 or the storage device 203 in the production / operation plan management table T240 and performs processing such as updating. Details of the production / operation plan management table T240 will be described later.
  • the production / operation plan creation unit 213 includes the production / operation conditions (obtained from the production / operation management device A001) stored in the memory 202 or the storage device 203, and the production / operation capability (from the production / operation capability management unit 211). Acquisition) and a production / operation plan (obtained from the production / operation plan management unit 212), a production / operation plan is created and stored in the memory 202 or the storage device 203.
  • each device may execute processing alone, or each device may be a program.
  • the CPU 201 may read the program into the memory 202 and execute it.
  • FIG. 4 is a diagram illustrating a schematic configuration of the maintenance management apparatus A003.
  • the maintenance management device A003 includes a CPU 301, a memory 302, a storage device 303, a user interface 304, a communication interface 305, an operation risk constant management unit 311, an operation risk management unit 312, and an operation risk calculation. 313 and a failure sign detection unit 314, which are designed to be able to transmit and receive each other via the internal bus 300.
  • the CPU 301, the memory 302, the storage device 303, the user interface 304, and the communication interface 305, which are general-purpose components in the maintenance management device A003, are the CPU 101 of the production / operation management device A001 shown in FIG. Since the memory 102, the storage device 103, the user interface 104, and the communication interface 105 have the same functions, detailed descriptions thereof are omitted.
  • the operation risk constant management unit 311 stores operation risk constants such as a time-dependent deterioration risk, a failure predictor risk, and a risk threshold stored in the memory 302 or the storage device 303, a deterioration deterioration risk management table T330, a failure predictor risk management table T340.
  • This is an apparatus that registers in an operation risk constant management table such as the operation risk threshold management table T350 and performs processing such as update. Details of the temporal deterioration risk management table T330, the failure predictor risk management table T340, and the operation risk threshold management table T350 will be described later.
  • the operation risk management unit 312 is a device that registers an operation risk stored in the memory 302 or the storage device 303 in the operation risk management table T360 and performs processing such as updating. Details of the operation risk management table T360 will be described later.
  • the operation risk calculation unit 313 includes a production / operation plan (obtained from the production / operation management device A001 or the production / operation planning device A002) stored in the memory 302 or the storage device 303, an aging deterioration risk, and a failure predictor risk.
  • This is a device that calculates an operation risk using an operation risk constant such as a maintenance guideline risk and stores it in the memory 302 or the storage device 303.
  • the failure sign detection unit 314 is a device that stores failure sign information (created by the failure sign detection unit 314 or acquired from the machine E001) in the memory 302 or the storage device 303.
  • the operation risk constant management unit 311, the operation risk management unit 312, the operation risk calculation unit 313, and the failure sign detection unit 314 may each execute processing alone, or each device. May comprise only a program, and the CPU 301 may read the program into the memory 302 and execute it.
  • FIG. 5 is a diagram showing a configuration example of the production / operation condition management table T130.
  • the production / operation condition management table T130 is a list of production / operation conditions under which the current machine managed by the production / operation management apparatus A001 operates as described in the explanation of FIG.
  • the production / operation condition management table T130 includes a machine column 131 storing machine identifiers, temperature, pressure, speed, acceleration, deceleration (brake), route, vehicle currently selected by the machine. It includes a production / operation condition column 132 for storing an identifier of production / operation conditions such as a configuration, and a product condition column 133 for storing an identifier of a product currently produced by the machine.
  • FIG. 6 is a diagram showing a configuration example of the countermeasure candidate management table T140.
  • the countermeasure candidate management table T140 is a list of candidate countermeasures that can be implemented at the time of failure sign detection managed by the production / operation management apparatus A001, as described in the explanation of FIG.
  • the countermeasure candidate management table T140 includes a countermeasure candidate column 141 for storing countermeasure contents, an additional number of days column 142 for storing time required for implementing countermeasures, and an additional storage for storing expenses required for implementing countermeasures.
  • the cost column 143 is configured.
  • the additional time column 142 and the additional cost column 143 may be a mathematical expression using other information such as a machine, failure sign information, and a date as a variable, an identifier representing an acquisition destination, or the like.
  • FIG. 7 is a diagram showing a configuration example of the production / operation capacity management table T230.
  • the production / operation capacity management table T230 is a list of the production / operation capacity of the machine managed by the production / operation planning apparatus A002 as described in the explanation of FIG.
  • the production / operation capacity management table T230 includes a machine column 231 for storing machine identifiers, temperature, pressure, speed, acceleration, deceleration (brake), route, vehicle configuration, etc. selected by the machine.
  • the machine E001 produces the product G001 with the capacity “10” under the production / operation condition B111
  • the machine E002 produces the product G001 with the capacity “8” under the production / operation condition B211.
  • the production of the machine E001 is high in terms of production.
  • the machine E001 produces the product G001 with the capacity “6” under the production / operation condition B112
  • the capacity changes by changing the production / operation conditions.
  • the machine E001 produces the product G002 with the capacity “8” under the production / operation condition B121, it can be seen that another product can be produced by changing the production / operation conditions.
  • the value in the capability column 234 may be a mathematical expression using other information such as production / operation conditions and operation time as a variable, an identifier representing an acquisition destination, or the like.
  • FIG. 8 is a diagram showing a configuration example of the production / operation plan management table T240.
  • the production / operation plan management table T240 is a list of production / operation plans for each product managed by the production / operation plan apparatus A002 as described in the explanation of FIG.
  • the production / operation plan management table T240 includes a product column 241 for storing product identifiers, a remaining amount column 242 for storing the remaining production amount up to the product production target, The remaining time column 243 for storing the remaining time is used.
  • the product G001 should produce the remaining “80” in the remaining “15” time
  • the product G002 should produce the remaining “150” in the remaining “30” time.
  • the remaining amount column 242 and the remaining time column 243 may be mathematical expressions using other information such as market information and date as variables, identifiers representing acquisition sources, and the like.
  • FIG. 9 is a diagram showing a configuration example of the temporal deterioration risk management table T330.
  • the aging risk management table T330 is a list of aging risks of machines managed by the maintenance management device A003 as described in the explanation of FIG.
  • the time degradation risk management table T330 includes a machine column 331 for storing machine identifiers, temperature, pressure, speed, acceleration, deceleration (brake), route, vehicle configuration, and the like selected by the machine.
  • the machine E001 has a production / operation condition B111 and the operation risk increase coefficient of the component P001 is “15”, and the machine E002 has an operation risk increase coefficient “10” in the production / operation condition B211.
  • the increase in operating risk of the machine E001 is large.
  • the operation risk increase coefficient of the part P001 is “3” in the production / operation condition B112, it can be seen that the increase in the operation risk is changed by changing the production / operation conditions.
  • the operation risk increase coefficient of the part P002 is “10” in the production / operation condition B121, it can be understood that the machine E001 changes the part whose operation risk increases by changing the production / operation condition.
  • the value in the coefficient column 334 may be a mathematical expression using other information such as production / operation conditions and operating time as a variable, an identifier representing an acquisition destination, or the like.
  • FIG. 10 is a diagram showing a configuration example of the failure sign risk management table T340.
  • the failure sign risk management table T340 is a list of machine failure sign risks managed by the maintenance management apparatus A003 as described in the description of FIG.
  • the failure sign risk management table T340 includes a failure sign column 341 that stores a failure sign identifier, a risk degree column 342 that stores an operation risk that increases when a failure sign is detected, and the like.
  • the operation risk increases by “1000” when the failure sign D001 is detected.
  • the value of the risk degree column 342 is absolutely large such as a mathematical value using other information as a variable, such as an operation risk at the time of detection, a part identifier, or a constant value or infinity that does not depend on the operation risk at that time.
  • An identifier representing a value or an acquisition destination may be used.
  • FIG. 11 is a diagram showing a configuration example of the operation risk threshold management table T350.
  • the operation risk threshold value management table T350 is a list of operation risk threshold values of the machines managed by the maintenance management apparatus A003, as described in the explanation of FIG.
  • the operation risk threshold management table T350 includes a machine column 351 for storing machine identifiers, a component column 352 for storing identifiers of machine maintenance target parts, and operation risk thresholds serving as maintenance guidelines.
  • the threshold value column 353 is stored.
  • the operation risk threshold value of the part P011 of the machine E001 is “2000”.
  • the value of the threshold value column 353 may be a mathematical expression using other information such as an operation time as a variable, an identifier representing an acquisition destination, or the like.
  • FIG. 12 is a diagram showing a configuration example of the operation risk management table T360.
  • the operation risk management table T360 is a list of current operation risks of the machines managed by the maintenance management apparatus A003 as described in the explanation of FIG.
  • the operation risk management table T360 includes a machine column 361 for storing machine identifiers, a component column 362 for storing identifiers of machine maintenance target components, and a risk degree column for storing current operation risks of components. 363 or the like.
  • the current operation risk of the part P011 of the machine E001 is “935”.
  • FIG. 13 is a flowchart showing an example of a processing procedure of countermeasure proposal presentation processing in the present embodiment.
  • Each step described below is realized by a program executed by each device constituting the operation optimization support system shown in FIG.
  • These programs are composed of codes for performing various operations described below. This premise is the same for other processing procedures.
  • the failure sign detection unit 314 of the maintenance management device A003 diagnoses a failure sign (S001). Specifically, the failure sign detection unit 314 detects a failure sign of a machine and stores information on the machine and the failure sign in the memory 302 or the storage device 303.
  • the maintenance sign device A003, the machine E001, or another device may be used to create the failure predictor information.
  • the machine E001 collects operation information (S011).
  • the operation information is not only production / operation information such as operation time, parts used, production / operation conditions, but also information indicating symptoms such as vibration, sound, images, and machines and parts such as maintenance history. It should include information on work on
  • the machine E001 transmits the operation information to the maintenance management apparatus A003 (S012).
  • the failure sign detection unit 314 of the maintenance management device A003 receives the operation information via the communication interface 305 and stores it in the memory 302 or the storage device 303 (S013).
  • the stored operation information includes the machine “E001”, the part “P011”, the production / operation condition “B111”, and the elapsed time “1”.
  • the failure sign detection unit 314 of the maintenance management apparatus A003 diagnoses the failure sign using the operation information stored in the memory 302 or the storage device 303.
  • the diagnosis of the failure sign may be a diagnosis using current information such as threshold detection or a diagnosis using past information and current information such as abnormality detection using clustering.
  • the failure sign detection unit 314 of the maintenance management apparatus A003 determines whether there is a failure sign (S014) and determines whether there is a failure sign (S015). If a failure sign D001 is detected in step S015, the failure sign detection unit 314 of the maintenance management device A003 stores the failure sign information in the memory 302 or the storage device 303 (S016). Here, it is assumed that the failure sign “D001” is included in the stored failure sign information.
  • the operation risk calculation unit 313 of the maintenance management device A003 updates the operation risk (S002).
  • the operation risk calculation unit 313 includes the current operation risk of the machine acquired from the operation risk management unit 312 based on the machine information stored in the memory 302 or the storage device 303, and the memory 302 or storage.
  • a new operation risk of the machine is calculated and stored in the memory 302 or the storage device 303 using the increase amount of the operation risk acquired from the operation risk constant management unit 311 based on the information on the failure sign stored in the device 303.
  • the operation risk management unit 312 updates the operation risk management table T360 based on the new operation risk of the machine stored in the memory 302 or the storage device 303.
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 acquires the current value of the operation risk from the operation risk management table T360 via the operation risk management unit 312 (S021).
  • the current operation risk “935” of the machine (FIG. 12). Record 364) is acquired.
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 calculates an increase in the risk of deterioration over time using the deterioration deterioration management table T330 (S022).
  • the degradation risk increasing coefficient “15” (record in FIG. 9) based on the machine “E001”, the part “P011”, and the production / operation condition “B111” stored in the memory 302 or the storage device 303. 335) is obtained, and the risk increase “15” of deterioration with time is calculated by multiplication with the elapsed time “1” stored in the memory 302 or the storage device 303.
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 determines whether there is a failure sign (S023).
  • the failure sign information includes a failure sign identifier “D001”.
  • the operation risk calculation unit 313 of the maintenance management device A003 refers to the failure sign risk management table T340 and calculates the risk increase of the failure sign (S024).
  • the risk increase “1000” of the sign of failure (record 343 in FIG. 10) is acquired.
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 calculates a new operation risk, and updates the operation risk management table T360 via the operation risk management unit 312.
  • the current operating risk “935” of the machine is added to the risk increase “15” of deterioration over time and the risk increase “1000” of the predictive failure, and a new operating risk “1950” is calculated to calculate the operating risk.
  • Update (S025) the current operating risk “935” of the machine is added to the risk increase “15” of deterioration over time and the risk increase “1000” of the predictive failure, and a new operating risk “1950” is calculated to calculate the operating risk. Update (S025).
  • the failure sign detection unit 314 of the maintenance management device A 003 transmits the machine and failure sign stored in the memory 302 or the storage device 303 to the production / operation management device A 001 via the communication interface 305. Is transmitted (S003). Then, the countermeasure plan creation unit 113 of the production / operation management apparatus A001 receives information on the machine and the failure sign via the communication interface 105 and stores the information in the memory 102 or the storage device 103.
  • the failure sign detection unit 314 of the maintenance management device A003 stores the machine “E001”, the part “P011”, the production / operation condition “B111”, and the failure sign “D001” stored in the memory 302 or the storage device 303. Assume that the data is transmitted to the production / operation management apparatus A001. Further, it is assumed that the measure plan creation unit 113 of the production / operation management apparatus A001 stores the information received from the maintenance management apparatus A003 in the memory 102 or the storage device 103.
  • the countermeasure candidate management unit 112 of the production / operation management apparatus A001 acquires countermeasure candidate information from the countermeasure candidate management table T140 based on the machine 102 and the failure predictor information stored in the memory 102 or the storage device 103. Then, it is stored in the memory 102 or the storage device 103 (S004).
  • the countermeasure candidate management unit 112 of the production / operation management apparatus A001 receives “as is”, “condition change”, “product change”, “product” as the countermeasure candidates (column 141 in FIG. 6) from the countermeasure candidate management unit 112.
  • “Consignment”, “Machine replacement”, “Parts replacement”, the additional time for the countermeasure candidate (column 142 in FIG. 6) and the additional cost of the countermeasure candidate (column 143 in FIG. 6) are acquired and these are the candidate countermeasure Is stored in the memory 102 or the storage device 103.
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 calculates the plan of each countermeasure candidate included in the acquired countermeasure candidate information to the production / operation planning apparatus A002 via the communication interface 105.
  • Information on each countermeasure candidate and the current production / operation conditions acquired from the production / operation condition management unit 111 are transmitted, and a plan for each countermeasure candidate is requested (S005).
  • the production / operation plan creation unit 213 of the production / operation planning apparatus A002 receives the information on each countermeasure candidate and the current production / operation conditions via the communication interface 205, and stores them in the memory 202 or the storage device 203. To do.
  • the measure creation unit 113 of the production / operation management apparatus A001 includes the machine “E001”, the part “P011”, the production / operation condition “B111” stored in the memory 102 or the storage device 103, Combinations of candidate countermeasures (column 141 in FIG. 6) and additional time (column 142 in FIG. 6), machines acquired from the production / operation condition management unit 111 (column 131 in FIG. 5), production / operation conditions (in FIG. 5) Assume that a combination of a column 132) and a product (column 133 in FIG. 5) is transmitted and a plan for each countermeasure candidate is requested. Further, it is assumed that the production / operation plan creation unit 213 of the production / operation planning apparatus A002 stores the information received from the production / operation management apparatus A001 in the memory 202 or the storage device 203.
  • the production / operation plan creation unit 213 of the production / operation planning apparatus A002 formulates a countermeasure plan (S006).
  • the production / operation plan creation unit 213 includes information on countermeasure candidates stored in the memory 202 or the storage device 203, current production / operation conditions stored in the memory 202 or the storage device 203, and production.
  • a plan of candidate countermeasures is calculated, and a feasible plan is taken Formulate.
  • the production / operation plan creation unit 213 transmits the formulated countermeasures to the production / operation management apparatus A001 via the communication interface 205. Then, the countermeasure plan creation unit 113 of the production / operation management apparatus A001 receives each countermeasure plan via the communication interface 105 and stores it in the memory 102 or the storage device 103.
  • step S006 the countermeasure drafting process in step S006 will be described.
  • the production / operation plan creation unit 213 of the production / operation planning apparatus A002 acquires the countermeasure candidates stored in the memory 202 or the storage device 203 one by one (S061). The following steps S062 to S064 are repeated until there are no countermeasure candidates.
  • the production / operation plan creation unit 213 acquires the machine / condition / capacity (S062), calculates the production time (S063), determines whether the calculated production time is realizable (S064), and can be realized. If so, it is recorded as a measure (S065).
  • step S062 the production / operation plan creation unit 213 determines the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5).
  • the production / operation capability “10” (record 235 in FIG. 7) is acquired from the production / operation capability management table T230 via the production / operation capability management unit 211.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “8” is calculated by dividing by the production / operation capacity “10” acquired in step S062.
  • step S 064 “0” (record 144 in FIG. 6), which is the additional time for the countermeasure candidate “as is”, is added to calculate the production target achievement time “8” of the product G001. Since this is less than the remaining production time “15” (record 244 in FIG. 8) of the product G001, it is determined that this is feasible.
  • step S065 the countermeasure candidate “as is” is stored in the memory 202 or the storage device 203 as a countermeasure plan together with the production time “8” and the achievement time “8”.
  • step S062 the production / operation plan creation unit 213 determines that the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5). Based on the record 134), another production / operation condition “B112” in which the product “G001” can be produced by the machine “E001” from the production / operation capability management table T230 via the production / operation capability management unit 211. The production / operation capability “6” (record 236 in FIG. 7) is acquired.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “14” is calculated by dividing by the production / operation capacity “6” acquired in step S062. Here, the time is calculated by rounding up the fractional part, but fraction processing may be performed by other methods.
  • step S 064 “1” (record 145 in FIG. 6), which is the additional time of the countermeasure candidate “condition change”, is added to calculate the production target achievement time “15” of the product G001. Since this is less than the remaining production time “15” (record 244 in FIG. 8) of the product G001, it is determined that this is feasible.
  • step S065 the countermeasure candidate “condition change” is stored as a countermeasure 202 together with the production / operation condition “B112”, the production time “14”, and the achievement time “15”. Alternatively, it is stored in the storage device 203.
  • step S062 the production / operation plan creation unit 213 determines that the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5). Record 134), the current machine “E002” of the product “G002”, and production / operation conditions “B221” (record 135 in FIG.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “10” is calculated by dividing by the production / operation capacity “8” of the product G001 acquired in step S062. Further, based on the product “G002”, the remaining production amount “150” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212, and step S062 is performed. The necessary production time “19” is calculated by dividing by the production / operation capacity “8” of the product G002 acquired in step (b). Here, the time is calculated by rounding up the fractional part, but fraction processing may be performed by other methods.
  • step S 064 “1” (record 146 in FIG. 6), which is the additional time of the countermeasure candidate “product change”, is added to achieve the production target achievement time “11” of the product G001 and the product goal of the product G002.
  • Time “20” is calculated. This is less than the remaining production time “15” (record 244 in FIG. 8) of the product G001 and less than the remaining production time “30” (record 245 in FIG. 8) of the product G002.
  • step S 065 the countermeasure candidate “product replacement” is the product “G001”, the machine “E002”, the production / operation condition “B211”, the production time “10”, and the achievement time. “11”, product “G002”, machine “E001”, production / operation condition “B121”, production time “19”, and achievement time “20” are stored in the memory 202 or the storage device 203 as countermeasures.
  • step S062 the production / operation plan creation unit 213 determines that the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5). Record 134), the current machine “E002” of the product “G002”, and production / operation conditions “B221” (record 135 in FIG. 5), production / operation through the production / operation capacity management unit 211 The machine “E002” to which the product “G001” can be commissioned, the production / operation condition “B211”, and the production / operation capability “8” (record 238 in FIG.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “20” is calculated by dividing by the production / operation capacity “4” acquired in step S062.
  • step S 064 “1” (record 147 in FIG. 6) as the additional time for the countermeasure candidate “product consignment” is added, and “21” is added as the time required to achieve the production target of the product G001. calculate. Since this is longer than the remaining production time “15” of the product G001 (record 244 in FIG. 8), it is determined that it cannot be realized.
  • step S062 the production / operation plan creation unit 213 determines that the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5).
  • Production / operation capacity management via the production / operation capacity management unit 211 based on the record 134), the machine “E003”, the production / operation condition “ ⁇ ”, and the product “ ⁇ ” (record 136 in FIG. 5).
  • the machine “E003” that can be exchanged for the machine “E001”, the production / operation condition “B311”, and the production / operation capability “8” (record 239 in FIG. 7) are acquired from the table T230.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “10” is calculated by dividing by the production / operation capacity “8” acquired in step S062.
  • step S 064 “3” (record 148 in FIG. 6), which is the additional time of the countermeasure candidate “machine replacement”, is added, and “13” is set as the time required to achieve the production target of the product G001. calculate. Since this is less than the remaining production time “15” (record 244 in FIG. 8) of the product G001, it is determined that this is feasible.
  • step S065 the countermeasure candidate “machine replacement” is stored in the memory 202 or the storage device 203 as a countermeasure plan together with the machine “E003”, the production / operation condition “B311”, the production time “10”, and the achievement time “13”. To do.
  • step S062 the production / operation plan creation unit 213 determines that the current machine “E001” and the production / operation condition “B111” of the product “G001” stored in the memory 202 or the storage device 203 (FIG. 5).
  • the production / operation capability “10” (record 235 in FIG. 7) is acquired from the production / operation capability management table T230 via the production / operation capability management unit 211.
  • step S063 based on the product “G001”, the remaining production amount “80” (record 244 in FIG. 8) is acquired from the production / operation plan management table via the production / operation plan management unit 212. Then, the necessary production time “8” is calculated by dividing by the production / operation capacity “10” acquired in step S062.
  • step S 064 “10” (record 149 in FIG. 6), which is the additional time for the countermeasure candidate “part replacement”, is added, and “18” is set as the time required to achieve the production target of the product G001. calculate. Since this is longer than the remaining production time “15” of the product G001 (record 244 in FIG. 8), it is determined that it cannot be realized.
  • the production of the product G001 may be outsourced to other vendors as a countermeasure candidate, so that it can be distributedly produced by a plurality of machines.
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 performs communication in order to calculate the operation risk of each countermeasure candidate included in the countermeasure candidate information stored in the memory 102 or the storage device 103.
  • the plan of each countermeasure candidate stored in the memory 102 or the storage device 103 is transmitted to the maintenance management apparatus A003 via the interface 105, and an operation risk calculation of each countermeasure candidate is requested (S007).
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 receives information on each countermeasure candidate and its plan via the communication interface 305, and stores them in the memory 302 or the storage device 303.
  • the operation risk calculation unit 313 of the maintenance management apparatus A003 calculates the operation risk of the countermeasure plan (S008).
  • the operation risk calculation unit 313 includes information on countermeasure candidates stored in the memory 302 or the storage device 303, a countermeasure plan stored in the memory 302 or the storage device 303, and the operation risk constant management unit 311. Based on the acquired operation risk constant and the current operation risk acquired from the operation risk management unit 312, the operation risk of the countermeasure plan is calculated.
  • the operation risk calculation unit 313 transmits the calculated operation risk of each countermeasure plan to the production / operation management apparatus A001 via the communication interface 305.
  • the measure plan creation unit 113 of the production / operation management apparatus A001 receives the operation risk of each measure plan via the communication interface 105 and stores it in the memory 102 or the storage device 103.
  • step S008 the operation risk calculation process in step S008 will be described.
  • the operation risk calculation unit 313 of the maintenance management device A003 obtains countermeasures stored in the memory 302 or the storage device 303 one by one (S081). The following steps S082 to S083 are repeated until there are no countermeasures.
  • the operation risk calculation unit 313 calculates an increase in the risk of deterioration with time (S082), and records the operation risk (S083).
  • step S082 based on the machine “E001” and the production / operation condition “B111”, the operation risk increase coefficient “of the component P011 from the time-dependent deterioration risk management table T330 via the operation risk constant management unit 311. 15 ”(record 335 in FIG. 9) is obtained and multiplied by the production time“ 8 ”to calculate a risk increase“ 120 ”of deterioration with time.
  • step S083 the risk increase “120” is added to the current operation risk “1950” of the component P011 calculated in step S002, thereby calculating the operation risk “2070” and the countermeasure plan “as is”. It is stored in the memory 302 or the storage device 303.
  • step S082 based on the machine “E001” and the production / operation condition “B112”, the operation risk increase coefficient “of the part P011 is determined from the time-dependent deterioration risk management table T330 via the operation risk constant management unit 311. 3 ”(record 335 in FIG. 9) is obtained and multiplied by the production time“ 14 ”to calculate the risk increase“ 42 ”of deterioration with time.
  • step S083 the risk increase “42” is added to the current operation risk “1950” of the component P011 calculated in step S002, thereby calculating the operation risk “1992” and the countermeasure proposal “condition change”. At the same time, it is stored in the memory 302 or the storage device 303.
  • step S082 based on the machine “E001” and the production / operation condition “B121”, the operation risk increase coefficient of the component P011 is calculated from the time-dependent deterioration risk management table T330 via the operation risk constant management unit 311. can not get.
  • the operation risk of the component P011 does not increase.
  • the operation risk may be calculated with a policy of increasing without using parts.
  • step S083 the current operation risk “1950” of the part P011 is stored in the memory 302 or the storage device 303 together with the countermeasure proposal “product change”.
  • step S082 based on the machine “E001” and the production / operation condition “ ⁇ ”, the operation risk increase coefficient of the component P011 is calculated from the time-dependent deterioration risk management table T330 via the operation risk constant management unit 311. can not get.
  • the operation risk of the component P011 does not increase.
  • the operation risk may be calculated with a policy of increasing without operating the machine.
  • step S083 the current operation risk “1950” of the part P011 is stored in the memory 302 or the storage device 303 together with the countermeasure plan “machine replacement”.
  • step S ⁇ b> 009 the countermeasure plan creation unit 113 of the production / operation management apparatus A ⁇ b> 001 receives the failure sign and the countermeasure plan information stored in the memory 102 or the storage device 103 via the user interface 104. Present to the user. Here, it may be modified using a risk threshold that can be acquired from the operation risk constant management unit 311 of the maintenance management apparatus A003.
  • a list of countermeasures (display item C002 in FIG. 18) is displayed together with information on the detected failure signs (display item C001 in FIG. 18).
  • the countermeasure proposal displays the time required to achieve the production target calculated in steps S005 to S008 and the operation risk when the target of the component P011 of the machine E001 that is the target of the detected failure sign is achieved. Further, the additional cost of the countermeasure plan (column 143 in FIG. 6) is also displayed.
  • the operation risk threshold of the part P011 of the machine E001 that can be acquired from the operation risk constant management unit 311 of the maintenance management apparatus A003 is “2000” (record 354 in FIG. 11)
  • this is included in the operation risk of the countermeasure plan. If there is an excess, the background is colored (display item C003 in FIG. 18). Further, when there is a change in the operation risk of the countermeasure plan from the current operation risk (part P011 is not used), the text is italicized (display item C004 in FIG. 18).
  • the user selects countermeasures by rearranging the items (time, risk, cost) that are important in the operation status at that time (display items C007, C008, C009 in FIG. 18), etc. (FIG. 18).
  • Display item C010) and instructing execution of the countermeasure (display item C011 in FIG. 18)
  • the countermeasure execution unit 114 of the production / operation management apparatus A001 executes the selected countermeasure.
  • the production / operation plan managed by the production / operation planning apparatus A002 may only be reflected, instructions may be automatically sent to the machine, other systems such as a parts ordering system, maintenance personnel call system, etc. It may be linked with other company systems.
  • the production / operation management apparatus A001 that manages the production / operation of the machine E001 and the like, and the production / operation planning apparatus that plans the production / operation of the machine
  • the operation optimization support system having A002 and the maintenance management device A003 that manages the operation state and operation risk of the machine, the maintenance management device A003 detects a failure sign of the machine, and the production / operation management device A001 Using the production / operation plan managed by the production / operation planning apparatus A002 and the operation risk managed by the maintenance / management apparatus A003, a countermeasure plan for the failure sign detected by the maintenance / management apparatus A003 is created.
  • a failure sign of a machine is detected, in order to optimize the machine operation, it is possible to support the user's decision making according to the items emphasized in the operation status at that time.
  • FMEA Feilure Mode and Effects Analysis
  • each device constituting the operation optimization support system will be described.
  • the configurations of the production / operation management device A001, the production / operation planning device A002, and the maintenance management device A003 are the same as those in the first embodiment, a detailed description thereof will be omitted.
  • FIG. 19 is a diagram illustrating a schematic configuration of the quality assurance device A004.
  • the quality assurance device A004 includes a CPU 401, a memory 402, a storage device 403, a user interface 404, a communication interface 405, an FMEA management unit 411, and an indication correspondence management unit 412.
  • a CPU 401 CPU 401
  • a memory 402 volatile and non-volatile memory
  • a storage device 403 volatile and non-volatile memory
  • a user interface 404 includes a keyboard 401, a keyboard, a printer, and the like.
  • the CPU 401 the memory 402, the storage device 403, the user interface 404, and the communication interface 405, which are general-purpose components in the quality assurance device A004, the CPU 101 of the production / operation management device A001 shown in FIG. Since the memory 102, the storage device 103, the user interface 104, and the communication interface 105 have the same functions, detailed descriptions thereof are omitted.
  • the FMEA management unit 411 registers FMEA items indicating possible failure modes and their causes, effects, and importance stored in the memory 402 or the storage device 403 in the FMEA management table T430, and performs processing such as updating. It is a device to perform. Details of the FMEA management table T430 will be described later.
  • the sign correspondence management unit 412 is a device that registers the correspondence relationship between the sign stored in the memory 402 or the storage device 403 and the FMEA item in the sign correspondence management table T440 and performs processing such as update. Details of the sign correspondence management table T440 will be described later.
  • FIG. 20 is a diagram illustrating a configuration example of the FMEA management table T430.
  • the FMEA management table T430 is a list of FMEAs indicating possible failure modes managed by the FMEA management unit 411 as described in the description of FIG.
  • the FMEA management table T430 includes an item column 431 that stores an identifier of the FMEA item, a mode column 432 that stores a failure mode indicated by the FMEA item, and a cause column that stores the cause of the failure mode indicated by the FMEA item. 433, an influence column 434 that stores the influence of the failure mode indicated by the FMEA item, and an importance column 435 that stores the importance of the failure mode indicated by the FMEA item.
  • FMEA item F001 is machine E001, component P011, failure mode “damage” is caused by “deterioration”, influence is “stop”, and importance is “27” machine E002.
  • FIG. 21 is a diagram showing a configuration example of the sign correspondence management table T440.
  • the sign correspondence management table T440 is a list of correspondence relationships between failure signs and FMEA items managed by the sign correspondence management unit 412 as described in the description of FIG.
  • the predictive correspondence management table T440 includes a failure predictor column 441 for storing an identifier of a failure predictor to be diagnosed, a machine column 442 for storing an identifier of a machine related to the failure predictor, and a part related to the failure predictor.
  • the component column 443 stores an identifier
  • the item column 444 stores an identifier of an FMEA item corresponding to a failure sign, and the like.
  • the machine E001, the part P011, and the failure sign D001 correspond to the FMEA item F001.
  • the failure sign “-” indicates that it is common to all the failure signs.
  • step S009 of FIG. 13 the countermeasure plan creation unit 113 of the production / operation management apparatus A001 sends the failure sign and the countermeasure plan information stored in the memory 102 or the storage device 103 to the user via the user interface 104.
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 sends the failure sign and the countermeasure plan information stored in the memory 102 or the storage device 103 to the user via the user interface 104.
  • display related FMEA items When presenting, display related FMEA items.
  • the measure creation unit 113 of the production / operation management apparatus A001 sends the machine “E001” stored in the memory 102 or the storage device 103 to the quality assurance apparatus A004 via the communication interface 105. ”, The part“ P011 ”, and the failure sign“ D001 ”are transmitted, and the FMEA item is requested (S191).
  • the sign correspondence management unit 412 of the quality assurance device A004 receives the machine “E001”, the part “P011”, and the failure sign “D001” via the communication interface 405, and stores them in the memory 402 or the storage device 403. .
  • the predictive response management unit 412 of the quality assurance device A004 uses the predictive response management table T440 based on the machine “E001”, the part “P011”, and the failure predictor “D001” stored in the memory 402 or the storage device 403.
  • the FMEA item “F001” (record 445 in FIG. 21) and the FMEA item “F002” (record 446 in FIG. 21) are retrieved and acquired (S192).
  • the predictive response management unit 412 of the quality assurance device A004 associates the related information from the FMEA management table T430 via the FMEA management unit based on the FMEA item “F001” and the FMEA item “F002” acquired in step S192.
  • Information on the failure mode to be performed (record 436 and record 437 in FIG. 20) is acquired and transmitted to the production / operation management apparatus A001 via the communication interface 405 (S193).
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 receives information regarding the failure mode of the FMEA item “F001” and the FMEA item “F002” via the communication interface 105, and the memory 102 or the storage device 103. To store.
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 provides information on the failure mode of the FMEA item “F001” and the FMEA item “F002” stored in the memory 102 or the storage device 103 as a failure sign and a countermeasure plan. Is displayed on the screen together with the information (S194).
  • FIG. 23 is a diagram showing an example of a proposed measure. Since the display items of C001, C002, C003, C004, C005, C006, C007, C008, C009, C010, and C011 in FIG. 23 are the same as those in the first embodiment, detailed description thereof is omitted.
  • a countermeasure plan can be selected together with FMEA information, so that the user's decision making can be further facilitated.
  • FIG. 24 is a diagram illustrating a schematic configuration of the production / operation management apparatus A001.
  • the CPU 101, the memory 102, the storage device 103, the user interface 104, the communication interface 105, the production / operation condition management unit 111, the countermeasure candidate management unit 112, and the countermeasure execution unit 114 are described in the first embodiment. Detailed description will be omitted.
  • the strategy management unit 115 is a device that registers a strategy stored in the memory 102 or the storage device 103 in the strategy management table T150 and performs processing such as updating. Details of the strategy management table T150 will be described later.
  • the countermeasure plan creation unit 113 creates a countermeasure plan in the same manner as in the first embodiment, selects an optimum countermeasure plan from the prepared countermeasure plans according to the logic stored in the strategy management table T150, and stores the memory 102 or This is a device stored in the storage device 103.
  • FIG. 25 is a diagram showing a configuration example of the strategy management table T150.
  • the strategy management table T150 is a list of strategies managed by the strategy management unit 115 as described with reference to FIG.
  • the strategy management table T150 includes a strategy column 151 that stores a strategy identifier, a logic column 152 that stores logic for realizing the strategy, a selection column 153 that stores a selection state of the user, and the like. Is done.
  • step S009 of FIG. 13 the countermeasure plan creation unit 113 of the production / operation management apparatus A001 provides the user with the failure sign and the countermeasure plan information stored in the memory 102 or the storage device 103 via the user interface 104. When presenting, it presents based on the information of the strategy management table T150.
  • the measure plan creation unit 113 of the production / operation management apparatus A001 uses the strategy management unit to select the strategy “cost while suppressing risk” from the strategy management table T150 where the selected column is “ ⁇ ”. “Importance” and its logic “minimum additional cost below risk threshold” (record 154 in FIG. 25).
  • the countermeasure plan creation unit 113 of the production / operation management apparatus A001 selects a countermeasure plan that matches the logic “minimum additional cost below the risk threshold” from the countermeasure plans stored in the memory 102 or the storage device 103.
  • the risk threshold “2000” (record 354 in FIG. 11) of the machine “E001” and the part “P011” is acquired from the operation risk threshold management table T350 via the operation risk constant management unit 311 of the maintenance management apparatus A003. Therefore, if the operation risk is “2000” or less and the additional cost is minimum, the countermeasure proposal “condition change” is used.
  • FIG. 26 is a diagram showing an example of a proposed measure. Since the display items of C001, C002, C003, C004, C005, C006, C007, C008, C009, C010, and C011 are the same as those in the first embodiment, detailed description thereof is omitted.
  • the measure proposal “condition change” selected based on the information in the strategy management table T150 is displayed at the top (display item C201 in FIG. 26).
  • the currently selected strategy is also displayed (display item C202 in FIG. 26).
  • a countermeasure plan can be automatically selected according to the strategy selected by the user, so that the user's decision making can be made smoothly and accurately.
  • A001 Production / operation management device 111 Production / operation condition management unit 112
  • Countermeasure candidate management unit 113 Countermeasure plan creation unit 114
  • Countermeasure execution unit 115 Strategic management unit
  • A002 Production / operation planning device 211
  • Production / operation capacity management unit 212 Production / operation plan management Unit 213
  • Maintenance management device 311 Operation risk constant management unit 312
  • Failure sign detection unit A004
  • FMEA management unit 412 Predictive response management unit E001, E002, E003 machine

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • General Factory Administration (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système d'assistance à l'optimisation d'opération ayant une machine, un dispositif de gestion de production/opération destiné à gérer la production/l'opération de la machine, un dispositif de planification de production/opération destiné à planifier la production/l'opération de la machine et un dispositif de gestion de maintenance destiné à gérer un état de fonctionnement et un risque de fonctionnement de la machine, le dispositif de gestion de maintenance détectant un présage de dysfonctionnement de la machine et le dispositif de gestion de production/opération utilisant un plan de production/opération géré par le dispositif de planification de production/opération et le risque de fonctionnement géré par le dispositif de gestion de maintenance pour créer une contre-mesure contre le présage de dysfonctionnement détecté par le dispositif de gestion de maintenance.
PCT/JP2015/064830 2015-05-22 2015-05-22 Procédé et système d'assistance à l'optimisation d'opération WO2016189603A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2015/064830 WO2016189603A1 (fr) 2015-05-22 2015-05-22 Procédé et système d'assistance à l'optimisation d'opération
JP2017520080A JP6553720B2 (ja) 2015-05-22 2015-05-22 運行最適化支援システム及び運行最適化支援方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/064830 WO2016189603A1 (fr) 2015-05-22 2015-05-22 Procédé et système d'assistance à l'optimisation d'opération

Publications (1)

Publication Number Publication Date
WO2016189603A1 true WO2016189603A1 (fr) 2016-12-01

Family

ID=57393011

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/064830 WO2016189603A1 (fr) 2015-05-22 2015-05-22 Procédé et système d'assistance à l'optimisation d'opération

Country Status (2)

Country Link
JP (1) JP6553720B2 (fr)
WO (1) WO2016189603A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020052931A (ja) * 2018-09-28 2020-04-02 セイコーエプソン株式会社 生産システムおよび生産方法
JP7245940B1 (ja) 2022-03-14 2023-03-24 株式会社 日立産業制御ソリューションズ リスクアセスメント装置およびリスクアセスメント方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004165216A (ja) * 2002-11-08 2004-06-10 Matsushita Electric Ind Co Ltd 生産管理方法および生産管理装置
JP2010091840A (ja) * 2008-10-09 2010-04-22 Ricoh Co Ltd 故障予兆報知システム、故障予兆報知方法および画像形成装置の保守方法
JP2011089751A (ja) * 2009-10-26 2011-05-06 Sanyo Electric Co Ltd 空気調和装置の故障診断システム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004165216A (ja) * 2002-11-08 2004-06-10 Matsushita Electric Ind Co Ltd 生産管理方法および生産管理装置
JP2010091840A (ja) * 2008-10-09 2010-04-22 Ricoh Co Ltd 故障予兆報知システム、故障予兆報知方法および画像形成装置の保守方法
JP2011089751A (ja) * 2009-10-26 2011-05-06 Sanyo Electric Co Ltd 空気調和装置の故障診断システム

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020052931A (ja) * 2018-09-28 2020-04-02 セイコーエプソン株式会社 生産システムおよび生産方法
JP7107144B2 (ja) 2018-09-28 2022-07-27 セイコーエプソン株式会社 生産システムおよび生産方法
US11774949B2 (en) 2018-09-28 2023-10-03 Seiko Epson Corporation Production system and production method
JP7245940B1 (ja) 2022-03-14 2023-03-24 株式会社 日立産業制御ソリューションズ リスクアセスメント装置およびリスクアセスメント方法
JP2023133814A (ja) * 2022-03-14 2023-09-27 株式会社 日立産業制御ソリューションズ リスクアセスメント装置およびリスクアセスメント方法

Also Published As

Publication number Publication date
JPWO2016189603A1 (ja) 2018-02-08
JP6553720B2 (ja) 2019-07-31

Similar Documents

Publication Publication Date Title
US11030551B2 (en) Predictive deconstruction of dynamic complexity
CN110546606B (zh) 租户升级分析系统及方法
AU2018260855B2 (en) Hybrid cloud migration delay risk prediction engine
US10416662B2 (en) Maintenance optimization for asset performance management
US11334831B2 (en) Predictive risk assessment in system modeling
KR102069386B1 (ko) 노후 예측 툴
US20090112668A1 (en) Dynamic service emulation of corporate performance
US10685319B2 (en) Big data sourcing simulator
US20200342419A1 (en) Intelligent management of one or more machines of a vehicle service center
US10007682B2 (en) Dynamically maintaining data structures driven by heterogeneous clients in a distributed data collection system
JP2016194736A (ja) プロジェクト実行計画立案支援方法、プロジェクト実行計画立案支援プログラム、および、プロジェクト実行計画立案支援システム
US20140173408A1 (en) Identity based automated form filling
US20200201840A1 (en) Self-adaptive data source aggregation system and method
US20230117225A1 (en) Automated workflow analysis and solution implementation
WO2014061229A1 (fr) Dispositif, procédé et programme d'aide à la construction de système d'informations
CN115685892A (zh) 工业规划的方法、装置、设备、存储介质和程序产品
CN106127365A (zh) 定量遥感产品在线交互式自主生产方法
JP2022002099A (ja) データをラベリングするための方法、装置、電子機器、記憶媒体およびコンピュータプログラム
WO2016189603A1 (fr) Procédé et système d'assistance à l'optimisation d'opération
CN110400085B (zh) 信息处理方法、信息处理装置和信息处理系统
US8510142B2 (en) Conflicting expert systems
KR20190066768A (ko) 스마트 제조환경에서의 프로세스 평가를 위한 파라미터 처리
KR20190066758A (ko) 스마트 제조를 위한 프로세스 평가 모델
KR101899298B1 (ko) 클라우드 및 가상화 기반의 프로세스 자동화 처리 시스템 및 그 처리 방법
US20180046974A1 (en) Determining a non-optimized inventory system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15893239

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017520080

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15893239

Country of ref document: EP

Kind code of ref document: A1