WO2015114760A1 - Planning assistance system, planning assistance method, and program - Google Patents

Abstract

[Problem] To propose a planning system, a planning method, and a program, whereby it is possible to create a plan taking into account profits from an entire mining business. [Solution] A planning assistance system for creating a plan for a mining business, said planning assistance system being characterized in that a processor: identifies mining machinery for which a plan is to be created, with reference to a mining machinery database; identifies business dates and times for which the plan is to be created, with reference to a calendar database; creates a plurality of feasible plans with reference to a work database; selects plans satisfying operational and maintenance restrictions from among the plurality of feasible plans with reference to a restriction database; calculates information relating to profits obtained by executing the plans satisfying the restrictions, with reference to a profit database; and presents the calculated profit-related information for each plan satisfying the restrictions.

Description

Planning support system, planning support method and program

The present invention relates to a planning support system, a planning support method, and a program.

In recent years, the market for mining equipment has been expanding rapidly due to rising demand for resources. In mining operations, the production of mined resources is directly linked to profits. Therefore, it is required to efficiently perform the operation work that directly contributes to the improvement of the production amount. The operation work here refers to, for example, an operation of actually collecting resources from a mine with an excavator and an operation of transporting the collected resources to a predetermined point by a dump.

On the other hand, maintenance work is necessary for stable operation. The maintenance work is, for example, work for exchanging parts as necessary so that an excavator, a dump truck or the like (hereinafter referred to as a mining machine) that performs operation works stably. Since parts of mining machines are generally expensive and large, it is costly to replace the parts frequently, and if the parts are not replaced for a long period of time, the mining machine may stop suddenly due to the life of the parts.

Therefore, Patent Document 1 discloses a technique for making a maintenance plan with high accuracy based on the actual operation status of a mining machine. Specifically, in Patent Document 1, after the operation status and work status of the mining machine are simulated by the simulation means, the cumulative load for each part corresponding to the operation status and work status is calculated by the cumulative load calculation means, and calculated. A technique for calculating the lifetime of each component by the lifetime calculation means based on the accumulated load is disclosed.

Therefore, according to this Patent Document 1, it is possible to devise a maintenance plan with higher accuracy as compared with a case where a maintenance plan is simply drafted based on the operating time. In addition, the maintenance cost can be reduced because it is not necessary to perform work that deviates greatly from the maintenance plan.

Japanese Patent No. 488421

However, the technique described in Patent Document 1 merely makes a plan for the timing of maintenance work such as parts replacement, and does not make a plan to perform maintenance work in consideration of cooperation with operation work. . And it does not create a plan that takes into account the benefits of mining operations as a whole.

That is, in the technique described in Patent Document 1, for example, when parts of a plurality of mining machines reach the end of their lives at the same time, a plan to replace a plurality of parts at the same time is planned. Not linked. Therefore, when there is only one maintenance staff at the time of replacement work, parts cannot be replaced as planned because of the lack of maintenance staff. In this case, since the mining machine remains stopped, the productivity is lowered and the profit of the entire mining operation is lowered.

Also, even if the maintenance personnel are sufficiently arranged and the parts can be replaced as planned, if a plurality of parts are replaced at the same time, a plurality of mining machines will be stopped at the same time. In this case, if a mining machine that operates instead is not prepared, the operation work is hindered, so that productivity is lowered and profit of the entire mining operation is lowered.

The present invention has been made in consideration of the above points, and proposes a planning support system, a planning support method, and a program that can formulate an optimal plan in consideration of the benefits of the entire mining operation.

In order to solve such a problem, in the planning support system for planning a mining work of the present invention, a mining machine database having information on mining machines, a calendar database having information on work date and time, and information on work contents A working database having a constraint, a constraint database having information on constraints, a profit database having information on benefits, and a processor. The processor refers to the mining machine database and identifies a mining machine to be planned. Then, refer to the calendar database to identify the work date and time to be planned, and refer to the work database to assign multiple tasks that can be executed by assigning the identified mining machine work to the identified work date and time. Create and reference the constraint database and create the executable The plan that satisfies the constraints is extracted from the plans of the above, and the profit database is calculated by referring to the profit database, and the information about the profits obtained when the plan that satisfies the constraints is executed is calculated for each plan that satisfies the constraints. It is characterized by presenting.

In order to solve such a problem, in the planning support method for planning a mining operation according to the present invention, the processor refers to a mining machine database having information on the mining machine, and the mining target is a planning target. Refer to the first step of specifying the machine, the second step of specifying the work date and time to be planned, with reference to the calendar database having the work date and time information, and the work database having the work content information The third step of creating a plurality of plans that can be executed by assigning the work by the specified mining machine to the specified work date and time, and the executable that has been created by referring to the constraint database having information on the constraints 4th step of extracting a plan satisfying constraints from among a plurality of plans, and a profit database having information on profit Referring to calculates the information on benefits obtained when running the plan that satisfies the constraints, characterized in that it comprises a fifth step of presenting for each plan that satisfies the constraints of information about the calculated gains.

In order to solve such a problem, in the program for planning a mining operation of the present invention, a mining machine database having information on the mining machine is referred to on a computer to identify a mining machine to be planned. The function to identify the work date and time to be planned and the work database having work content information by referring to the calendar database having the function and the work date and time information, and the work by the specified mining machine A function that creates multiple plans that can be executed by assigning them to the specified business date and time, and extracts a plan that satisfies the constraints from the multiple executable plans that have been created by referring to the constraint database that has information on the constraints. When a plan that satisfies the constraints is executed with reference to a profit database that has information on Calculating information on benefits to be, characterized in that to realize the function of presenting for each plan that satisfies the constraints of information about the calculated gains.

According to the present invention, it is possible to devise an optimal plan in consideration of the profits of the entire mining operation.

It is a whole block diagram of the mine system in this Embodiment. It is a conceptual diagram of a calendar database. It is a conceptual diagram of a mining machine database. It is a conceptual diagram of a work database. It is a conceptual diagram of a production volume database. It is a conceptual diagram of a mineral market price database. It is a conceptual diagram of an operation performance database. It is a conceptual diagram of a personnel database. It is a conceptual diagram of an inventory database. It is a conceptual diagram of a maintenance interval database. It is a conceptual diagram of a maintenance cost database. It is a conceptual diagram of a plan database. It is a conceptual diagram of a plan management database. It is a flowchart which shows a planning process. It is a flowchart which shows a plan creation process. It is a flowchart which shows a restriction | limiting confirmation process. 1 is an overall configuration diagram of a mine system using a cloud.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(1) Overall Configuration FIG. 1 shows the overall configuration of the mine system 1. The mine system 1 includes a planning support system 10, a client terminal 20, and a network N1. The network N1 is, for example, a local area network (LAN) or a wide area network (WAN), and is a communication path that connects the planning support system 10 and the client terminal 20 so that they can communicate with each other.

The planning support system 10 includes an IO (Input / Output) device 11, a communication device 12, a memory 13, a processor 14, and a storage device 15. The IO device 11 is a device that executes input / output processing in the planning support system 10. The communication device 12 is a device that transmits a plan made to the client terminal 20 via the network N1 and receives an instruction requesting to make a plan from the client terminal 20.

The memory 13 is, for example, a RAM (Random Access Memory), and is a volatile storage medium that temporarily stores various programs and various information. The processor 14 includes a CPU (Central Processing Unit), expands various programs and various information stored in the storage device 15 to the memory 13, cooperates with the expanded various programs, and refers to various information. Thus, it is an arithmetic device that comprehensively controls the operation of the planning support system 10.

The storage device 15 is, for example, an HDD (Hard Disk Drive), and is a non-volatile storage medium that stores various programs and various information. As various programs stored in the storage device 15, there are a plan generation program 1511, a personnel confirmation program 1512, an inventory confirmation program 1513, a maintenance interval confirmation program 1514, a dependency relationship confirmation program 1515, an amount calculation program 1516, and a plan presentation program 1517. Details of processing executed by these various programs will be described later (FIGS. 14 to 16).

Various information stored in the storage device 15 includes a calendar database 1521, a mining machine database 1522, a work database 1523, a production volume database 1524, a mineral market database 1525, an operation results database 1526, a human resources database 1527, an inventory database 1528, and a maintenance interval. There are a database 1529, a maintenance cost database 1530, a plan database 1531, and a plan management database 1532. Details of these various types of information will be described later (FIGS. 2 to 13).

The client terminal 20 is provided with an input interface such as a keyboard and a mouse (not shown), and accepts an instruction for requesting to make a plan for one mining operation. Then, the client terminal 20 transmits the received instruction to the planning support system 10 via the network N1. In addition, the client terminal 20 receives the planned plan from the planning support system 10 and displays the received plan on the display.

In the present embodiment, the client terminal 20 receives a planning instruction and transmits the received instruction to the planning support system 10. However, the present invention is not limited to this. For example, the planning support system 10 performs the planning. It is also possible to directly accept a planning instruction. Further, a plurality of client terminals 20 may be connected to the network N1, and any one of the client terminals 20 may receive a planning instruction.

(2) Database Configuration FIG. 2 shows a conceptual configuration of the calendar database 1521. The calendar database 1521 is a database having information on the operation date and time of the mine operation. Specifically, the calendar database 1521 includes a year / month / day column 15211, a start time column 15212, and an end time column 15213.

The year / month / day column 15211 stores the date of the mining operation, the start time column 15212 stores the start time of the mining operation, and the end time column 15213 stores the end time of the mining operation.

Therefore, in the case of FIG. 2, for example, a mine operation of a certain mine is scheduled to be performed between “2013/6/1” and “2013/6/30”, and “2013/6/1” is “9” It is shown that the mining operation starts at 1:00 and is scheduled to end at 15:00.

FIG. 3 shows a conceptual configuration of the mining machine database 1522. The mining machine database 1522 is a database having information on mining machines used for mining operations. Specifically, the mining machine database 1522 includes a machine ID column 15221, a model name column 15222, a vehicle type column 15223, and an initial position column 15224.

The machine ID column 15221 stores identification information for identifying the mining machine, the model name column 15222 stores the model name of the mining machine, and the vehicle type column 15223 stores the vehicle type of the mining machine. The initial position column 15224 stores the position of the mining machine at the start of the business on the first day of the mine business.

Therefore, in the case of FIG. 3, for example, the mining machine with the machine ID “1” has the model name “xx-101” and the vehicle type “dump”. Also, it is shown that it is placed at “point A” at the start of the first day of the mining operation.

FIG. 4 shows a conceptual diagram of the work database 1523. The work database 1523 is a database having information indicating the work contents of a plurality of works in the mining operation. Specifically, the work database 1523 includes a work ID column 15231, a target machine column 15232, a work classification column 15233, a work time column 15234, a start position column 15235, an end position column 15236, a load information column 15237, a dependency relationship column 15238, and necessary parts. It consists of a column 15239 and a necessary maintenance personnel column 15240.

The work ID column 15231 stores identification information for identifying the work content, the target machine column 15232 stores the type name of the mining machine to be worked, and the work classification column 15233 stores the work content classification. The work time column 15234 stores a standard work time for the work, the start position column 15235 stores the work start position, and the end position column 15236 stores the work end position.

The load information column 15237 stores load information such as the distance traveled by the work and sensor data obtained from the sensor attached to the mining machine, and the dependency column 15238 stores other mining machines necessary for the work. The identification information for specifying the work content of is stored.

The necessary parts column 15239 stores identification information of parts required when the work classification is maintenance work, and the necessary maintenance staff field 15240 stores the number of maintenance personnel required when the work classification is maintenance work. Is done.

Therefore, in the case of FIG. 4, for example, for the work with work ID “S-000-0”, the work target mining machine is “all” (all mining machines), the work classification is “stop”, and all mining machines It is shown that the movement distance in this work is “0 km” because the operation is stopped.

In addition, the work with the work ID “O-101-1” has the type name of the target mining machine “xx-101”, the work classification “operation”, and the standard work time of this work is “15 minutes”, this mining machine is located at “point A” at the start of work, moves to “point C” at the end of the work, and moves from point A to point C, so the travel distance of “7 km” is It is shown to be loaded.

For the work with work ID “M-101-1”, the type name of the mining machine to be worked is “xx-101”, the work classification is “maintenance”, and the standard work time of this work is It is “30 minutes”, and it is shown that the maintenance work of this mining machine is performed at “point N”. In addition, it is indicated that the replacement part necessary for the maintenance work is a part specified by “p-101-01”.

Here, the work with the work ID “O-101-1” will be described in detail. This work is a work by “dump” because the model name is “xx-101” (see FIG. 2). It is shown that the work is to move from “point A” to “point C” ahead of “7 km” over “15 minutes”.

When the work with the work ID “O-201-1” is referred to, this work is a work by “excavator” because the model name is “xx-201” (see FIG. 2). "It is shown that the work is to mine resources at" point C ".

When the work with the work ID “O-101-7” is referred to, this work is a work by “dump” because the model name is “xx-101” (see FIG. 2), and the dump is “30 minutes”. ”To“ Point A ”ahead of“ Point C ”by“ 7 km ”, and“ O-201-1 ”is specified as the dependency. ing.

Thus, for example, if a dump moves from point A to point C, then an excavator loads resources at the point C, and the dump loaded with resources moves from point C to point A, The work IDs “O-101-1”, “O-201-1”, “O-101-7” are extracted from the work database 1523, and the combination order is “O-101-1”, “O-201-”. 1 ”and“ O-101-7 ”in order.

In the case of this plan, when the dump truck moves from point A to point C, the work time is set to “10 minutes” because it is merely moved and no resources are loaded. When the loaded dump truck moves from point C to point A, the working time is set to “30 minutes” because the weight increases.

In addition, if the excavator does not perform the work of loading resources onto the dump (O-201-1), the work of moving the dump from the point C to the point A (O-107-1) is not performed. The task “O-201-1” is designated as the dependency of the task “−1”. Thus, by extracting each work from the work database 1523 and combining them efficiently, a plan that takes into account the actual operation work can be created.

Here, the work classification of the operation of moving the dump from point A to point C (O-101-1) and the operation of moving the dump from point C to point A (O-107-1) are both “operation”. Although it is set to be the same, these work classifications may be further subdivided.

For example, the operation of moving the dump from point A to point C (O-101-1) is an operation that indirectly contributes to production, so it is set as “indirect operation”, and the operation of moving the dump from point C to point A Since (O-107-1) is an operation that directly contributes to production, “direct operation” may be set. In this case, for example, a plan with a high profit or production amount can be created by efficiently combining work with work classification “direct operation”.

FIG. 5 shows a conceptual configuration of the production volume database 1524. The production amount database 1524 is a database having information on the production amount of resources collected when work is performed. Specifically, the production volume database 1524 includes a work ID column 15241, a spot column 15242, and a production column 15243.

The work ID column 15241 stores identification information for specifying the work content, the point column 15242 stores the point where the work is performed, and the production amount column 15243 produces the resources collected at the point where the work is performed. The quantity is stored. The production amount here is obtained, for example, by the product of the transport amount transported by the dump truck by one operation and the mineral content (mineral concentration) at each point. The transport amount transported by one operation work can be acquired based on load information such as sensors provided in the mining machine. The mineral concentration at each point can be obtained based on geological surveys during mine development and feedback from the mineral refining process.

Therefore, in the case of FIG. 5, for example, when the work with the work ID “O-101-7” is performed, “6.1 g” resource is collected at “point C”.

Here, the work of transporting resources to the depot is defined as the work that directly contributes to production, and the work ID of this work is stored in the work ID column 15241. When the work for removing impurities is also considered, the work ID of the work for removing impurities is stored in the work ID column 15241 as a work that directly contributes to production.

FIG. 6 shows a conceptual configuration of the mineral market database 1525. The mineral market database 1525 is a database having resource market price information that changes from day to day. Specifically, the mineral market database 1525 includes a date column 15251 and a market column 15252. The year / month / day column 15251 stores information on the year / month / day, and the market price column 15252 stores the market price of resources per unit quantity (yen, dollar, etc.).

Therefore, in the case of FIG. 6, for example, the resource price of “2013/6/1” is “97” (unit omitted), and the next day “2013/6/2” is the resource price of “101”. It is shown.

FIG. 7 shows a conceptual configuration of the operation result database 1526. The operation result database 1526 is a database having information on conditions that allow continuous operation until the next maintenance work. Specifically, the operation record database 1526 includes a machine ID column 15261, a necessary maintenance column 15262, and a continuous operation enable condition column 15263.

The machine ID column 15261 stores identification information for specifying a mining machine, the necessary maintenance column 15262 stores identification information for specifying a necessary maintenance operation, and the continuous operation possible condition column 15263 indicates the time until the next maintenance operation. Information on the distance that can be traveled and other information that can be loaded until the next maintenance work are stored. The continuous operation enabling condition is calculated based on the operation record of the mining machine up to the present and the predetermined periodic maintenance requirement or failure sign detection technology.

Therefore, in the case of FIG. 7, for example, the mining machine with the machine ID “1” needs the maintenance work specified by the work ID “M-101-1”, and the distance traveled until the next maintenance work is It is shown to be “73 km”.

Note that the mining machine with the machine ID “1” is “dump” (see FIG. 3). When the mining machine is a non-moving mining machine such as “excavator”, the total amount of accumulated resources and the operation time may be stored in the continuous operation possible condition column 15263.

FIG. 8 shows a conceptual configuration of the human resource database 1527. The human resource database 1527 is a database having information on the number of maintenance personnel secured on business days when mining operations are performed. Specifically, the human resource database 1527 includes a date column 15271 and a maintenance staff number column 15272.

The date field 15271 stores the date when the mine operation is performed, and the maintenance number field 15272 stores the number of maintenance personnel who can perform the maintenance work. Here, the number of maintenance personnel is shown in units of years, but the present invention is not limited to this, and the number of maintenance personnel may be shown in time units.

Therefore, in the case of FIG. 8, for example, “2013/6/1” has “0” maintenance personnel who can perform maintenance work, “2013/6/2” is “0” people, “2013/6”. "/ 3" is shown to be "3" people.

FIG. 9 shows a conceptual configuration of the inventory database 1528. The stock database 1528 is a database having information on when the parts required for maintenance work are available. Specifically, the inventory database 1528 includes an inventory ID column 15281, a part number column 15282, and an available time column 15283.

The inventory ID column 15281 stores identification information for identifying inventory, the component number column 15282 stores component identification information necessary for maintenance work, and the available time column 15283 indicates the time when the component can be used. Stored.

Therefore, in the case of FIG. 9, the inventory with the inventory ID “1” is information indicating the inventory of the part with the part number “p-101-01”, and this part arrived at the site at “2013/5/28”. It is shown that it will be available after this date.

FIG. 10 shows a conceptual configuration of the maintenance interval database 1529. The maintenance interval database 1529 is a database having maintenance work interval information. Specifically, the maintenance interval database 1529 includes a maintenance ID column 15291 and a post-maintenance continuous operation enable condition column 15292.

The maintenance ID column 15291 stores identification information for specifying the maintenance work, and the post-maintenance continuous operation enable condition column 15292 has information on the distance that can be traveled between immediately after the maintenance work and the next maintenance work and immediately after the other maintenance work. The allowable load information is stored from the time until the next maintenance work. The post-maintenance continuous operation enabling condition is calculated based on predetermined periodic maintenance requirements, failure sign detection technology, component life prediction technology, or the like.

Therefore, in the case of FIG. 10, when the maintenance work with the maintenance ID “M-101-1” is performed, it is possible to continue traveling “100 km” until the next similar maintenance work is performed. It is shown.

The maintenance work of “M-101-1” is performed on the mining machine whose model name is “xx-101” (see FIG. 4), and the mining machine whose model name is “xx-101”. It can be specified that the machine is a “dump” (see FIG. 3). Therefore, it is shown that when the maintenance operation of “M-101-1” is performed on “dump”, traveling of “100 km” is possible until the next maintenance.

When the mining machine is a non-moving mining machine such as “excavator”, the post-maintenance continuous operation enable condition column 15292 may store the total amount of resources and the operation time.

FIG. 11 shows a conceptual configuration of the maintenance cost database 1530. The maintenance cost database 1530 is a database having information (such as yen and dollars) such as parts costs and labor costs for maintenance work. Specifically, the maintenance cost database 1530 includes a maintenance ID column 15301 and a price column 15302.

The maintenance ID column 15301 stores identification information for specifying maintenance work, and the price column 15302 stores the total amount of parts and labor costs actually borne by the miner operator.

Therefore, in the case of FIG. 11, for example, when the maintenance work with the maintenance ID “M-101-1” is performed, it is indicated that the miner operator needs to bear the cost of “1000” (unit omitted). Yes.

FIG. 12 shows a conceptual configuration of the plan database 1531. The plan database 1531 is a database having specific work content information in mining operations. Specifically, the plan database 1531 includes a plurality of minimum plan information 1531A for each mining machine and each year / month / day with respect to one plan. The minimum plan information 1531A includes a plan ID column 15311, a machine ID column 15312, a date / month column 15313, a start time column 15314, an end time column 15315, and an execution work column 15316.

The plan ID column 15311 stores identification information for identifying a plurality of plans planned for the mining operation, the machine ID column 1531 stores identification information for identifying a mining machine, and the date / month column 15313 Stores the date when the mining operation is performed.

Further, the start time and end time of each work are stored in the start time column 15314 and the end time column 15315, and identification information for specifying the work is stored in the execution work column 15316.

Therefore, in the case of FIG. 12, for example, the mining machine with the machine ID “1” in the plan with the plan ID “57” is from “10:00” to “10:15” of “2013/6/3”. It is shown that the work with the work ID “O-101-1” is performed. Note that the mining machine with the machine ID “1” is “dump” (see FIG. 3), and the operation of “O-101-1” is “operation” that moves from “point A” to “point C”. Work (see FIG. 4).

The minimum plan information 1531A shown on the top surface of FIG. 12 is information of work scheduled to be performed on “2013/6/3” as “Dump” as described above, and is duplicated in the minimum plan information 1531A. The other minimum plan information 1531A shown is information on work scheduled to be performed on “2013/6/3” by other mining machines (dumpers and excavators having different model names) having different machine IDs.

Although not shown in FIG. 12, information on work scheduled to be performed on a date (for example, 2013/6/4) different from the plurality of minimum plan information 1531A is also stored in the plan database 1531. All of these are stored as a “57” plan.

FIG. 13 shows a conceptual configuration of the plan management database 1532. The plan management database 1532 is a database having information on profits and information on constraints. Specifically, the plan management database 1532 includes a plan ID column 15321, a profit column 15322, a sales column 15323, a cost column 15324, a total production volume column 15325, a production volume column 15326 at each point, a constraint confirmation column 15327, a constraint column 15328, and personnel. It is composed of a constraint column 15329, an inventory constraint column 15330, a maintenance interval constraint column 15331, and a dependency relationship constraint column 15332.

The plan ID column 15321 stores identification information for identifying a plurality of plans planned for the mining operation, and the profit column 15322 stores the net profit (yen, dollars, etc.) obtained when one plan is executed. Stored. This net profit is calculated by subtracting the cost from the sales. The sales column 15323 stores the sales obtained when one plan is executed. This sales is calculated by multiplying the total production volume by the market price.

The cost column 15324 stores the maintenance cost when one plan is executed, and the total production amount column 15325 stores the total production amount of resources obtained when one plan is executed. The production amount column 15326 stores the production amount of resources at each point obtained when one plan is executed. The total production volume at each point is the total production volume.

Here, any one of the sales, maintenance cost, total production amount, and production amount at each point stored in the profit column 15322, the sales column 15323, the cost column 15324, the total production amount column 15325, and the production amount column 15326 at each point. Or the information including all is demonstrated as information regarding profit.

The constraint confirmation column 15327 stores information indicating whether or not various constraints have been confirmed for the planned plan, and the constraint column 15328 indicates whether or not the planned plan satisfies all the various constraints. Information to be stored is stored.

The personnel restriction column 15329 stores information indicating whether or not the plan is planned within the resource range of the maintenance staff, and the inventory constraint column 15330 is a plan planned within the range of the inventory resource. Is stored, and the maintenance interval restriction column 15331 stores information indicating whether or not the mining machine is a plan planned within a maintenance interval range in which the mining machine can be operated continuously. The dependency relationship restriction column 15332 stores information indicating whether or not work having a dependency relationship is being performed simultaneously.

Here, information including any or all of various types of information stored in each of the constraint confirmation column 15327, the constraint column 15328, the personnel constraint column 15329, the inventory constraint column 15330, and the maintenance interval constraint column 15331 is used as information regarding maintenance constraints. explain. The information stored in the dependency relationship restriction column 15332 will be described as information related to restrictions on operation.

Accordingly, in the case of FIG. 13, for example, if a plan specified by the plan ID “57” is executed, the profit is “3200” (unit omitted), the sales is “4000”, and the cost is predicted to be “800”. Has been shown to be.

When the plan with the plan ID “57” is executed, the total production amount is “1800”, and it is predicted that the production amount “241” is obtained at the point C and “321” is obtained at the point F. Has been.

Also, for the plan with the plan ID “57”, the constraint has been confirmed (“1”), which indicates that various constraints are satisfied (“0”). Specifically, it indicates that personnel constraints are satisfied (“0”), inventory constraints are satisfied (“0”), maintenance interval constraints are satisfied (“0”), and dependency constraints are satisfied (“0”). Has been.

(3) Flowchart FIG. 14 shows the processing procedure of the planning process. This planning process is triggered by the operator of the client terminal 20 instructing the planning support system 10 to plan or by a predetermined periodic timing (timing such as the beginning of the month). The program is executed in cooperation with the processor 14 of the planning support system 10 and various programs (1511 to 1517).

The processor 14 executes the processing in steps SP1 to SP3 in cooperation with the plan generation program 1511, and performs the processing in step SP4 with a personnel confirmation program 1512, an inventory confirmation program 1513, a maintenance interval confirmation program 1514, and a dependency relationship confirmation program 1515. The processing in step SP5 is executed in cooperation with the amount calculation program 1516, and the processing in step SP6 is executed in cooperation with the plan presentation program 1517. Hereinafter, for convenience of explanation, the processing main body will be described as the processor 14.

First, the processor 14 refers to the mining machine database 1522 and identifies mining machines necessary for the mining operation to be planned (SP1). Next, the processor 14 refers to the calendar database 1521 and specifies the work date and time of the mining work to be planned (SP2). Next, the processor 14 refers to the work database 1523 and creates a plan that can be executed by the mining machine identified in step SP1 within the business date and time identified in step SP2 (SP3).

The details of step SP3 will be described later (FIG. 15), but briefly described here. First, the processor 14 selects one mining machine from the mining machines specified in step SP1, and the work specified in step SP2. One business date and time (date, date, start time and end time) is selected from the date and time.

Next, the processor 14 refers to the work database 1523 and creates a plan (minimum plan information 1531A) that can be executed by one mining machine from the start time to the end time of one date. At this time, the processor 14 creates a plurality of variations of minimum plan information 1531A.

For example, when creating the minimum plan information 1531A for the dump, the processor 14 creates the minimum plan information 1531A for the pattern in which the maintenance work is performed only once and the other minimum plan information 1531A for the pattern in which the maintenance work is performed twice. In this case, for example, the minimum plan information 1531A of the pattern in which the maintenance work is performed only once requires less maintenance cost and the profit or the production amount is higher than the other minimum plan information 1531A of the pattern in which the maintenance work is performed twice.

However, depending on the combination with other mining equipment or the minimum plan information 1531A of other dates, the plan including the minimum plan information 1531A with a pattern in which maintenance work is performed only once is not necessarily profit or production as a whole. Is not necessarily high. The profit or production amount of the entire mining operation is calculated in step SP5.

Next, the processor 14 similarly creates the minimum plan information 1531A that can be executed by the other mining machines from the start time to the end time of the same date.

By the above processing, a plurality of minimum plan information 1531A for one date (for example, 2013/6/3) is created for each of a plurality of variations. The processor 14 can create a plurality of plans by executing the same processing as described above for all other business dates (for example, 2013/6/4). The processor 14 stores the created plans in the plan database 1531.

Next, the processor 14 refers to the work database 1523, the human resource database 1527, the inventory database 1528, the operation result database 1526, and the maintenance interval database 1529, and confirms whether or not each plan created in step SP3 satisfies various constraints. (SP4).

The details of step SP4 will be described later (FIG. 16). Briefly described here, first, the processor 14 refers to the work database 1523 to confirm the number of persons required for maintenance work, while referring to the human resource database 1527. Confirm the number of people who can perform maintenance work. Then, the processor 14 compares the number of persons required for the maintenance work with the number of persons capable of the maintenance work, thereby confirming whether or not each plan created in step SP3 satisfies the personnel constraint.

Next, the processor 14 refers to the work database 1523 to confirm parts necessary for the maintenance work of the mining machine, while referring to the inventory database 1528 to confirm available inventory parts of the mining machine. Then, the processor 14 compares the parts necessary for the maintenance work with the available inventory parts, thereby confirming whether or not each plan created in step SP3 satisfies the inventory constraint.

Next, the processor 14 refers to the operation record database 1526 to confirm the load information (for example, the travelable distance) of the mining machine, refers to the work database 1523 to confirm the load information (for example, the travelable distance) for each work, With reference to the maintenance interval database 1529, the load information after the maintenance work (for example, the travelable distance) is confirmed. Then, the processor 14 compares the load information of the mining machine, the load information after each work, and the load information after the maintenance work to confirm whether each plan created in step SP3 satisfies the maintenance interval constraint. To do.

Next, the processor 14 refers to the work database 1523 to confirm the dependency relationship, thereby confirming whether each plan created in step SP3 satisfies the dependency constraint. The processor 14 stores information on these restrictions in the plan management database 1532.

Next, the processor 14 refers to the production volume database 1524, the mineral market database 1525, and the maintenance cost database 1530, and calculates information related to profits for the plan that satisfies all of the various constraints confirmed in step SP4 (SP5).

The information on profit is information on profit, sales, maintenance cost, total production volume, and production volume at each point among the information held in the plan management database 1532 (FIG. 13).

The step SP5 will be described in detail. First, the processor 14 refers to the production volume database 1524, calculates the production volume at each point predicted when the plan is executed, and adds all the production volumes at each point. To calculate the total production. Next, the processor 14 refers to the mineral market database 1525 to calculate the sales predicted when the plan is executed by multiplying the total production volume by the market price.

Next, the processor 14 refers to the maintenance cost database 1530 and calculates a maintenance cost predicted when the plan is executed. Then, the processor 14 calculates a profit by subtracting the maintenance cost from the sales. The processor 14 stores the calculated profit, sales, maintenance cost, total production amount, and production amount information at each point in the plan management database 1532.

Next, when receiving an instruction to present a plan from the client terminal 20, the processor 14 refers to the plan database 1531 and the plan management database 1532 to obtain information on a plurality of plans and profits that satisfy all of the various restrictions, for example, the client terminal 20 Is displayed and presented (SP6), the planning process is terminated.

For step SP6, for example, an instruction for presenting a plan from the client terminal 20 includes an instruction for confirming various constraints and presenting a plan that satisfies all the various constraints. Upon receiving an instruction from the client terminal 20, the processor 14 refers to the plan management database 1532, stores “1” in the constraint confirmation column 15327, and stores “0” in the constraint column 15328. Existing plan IDs can be extracted, and the extracted plan IDs can be arranged in descending order and displayed on the display of the client terminal 20.

Further, for example, when any one of the plans displayed on the client terminal 20 is selected, the processor 14 refers to the plan database 1531 and performs each work of the selected one plan on the client terminal 20. Can be displayed on the display. Therefore, it is possible to present an optimal plan that can be executed from the viewpoint of profit for one mining operation.

Also, the plan presentation instruction from the client terminal 20 may include an instruction for leveling the production volume at each point. In this case, the processor 14 can display only the plan in which the production amount at each point is leveled on the display of the client terminal 20. Therefore, resources are collected uniformly from each point, excluding plans in which only the production volume at one highly concentrated point (for example, point C) is significantly higher than the production volume at other points (for example, point F). Only plans can be presented.

FIG. 15 shows the processing procedure of the plan creation process. This plan creation processing is executed when the processing in the planning processing (FIG. 14) has shifted to step SP3.

As a premise, in the plan creation process described here, one mining machine (for example, dump) and one work date (for example, 2013/6/3 from 9:00 to 18:00) are selected. This is a process of creating a plan (minimum plan information 1531A) that can be executed by a mining machine on one business date and time. By executing the plan creation process described here for other mining machines and other business dates, a plurality of plans are created for one mining business.

First, the processor 14 substitutes the type name of one mining machine selected as a premise into the variable K, and also substitutes the initial position of the mining machine into the variable X (SP31). Next, the processor 14 substitutes the work start time of the one work date and time selected as the premise into the variable T, and substitutes the work end time into the variable T_END (SP32). Then, the processor 14 creates minimum plan information 1531A having an empty element (SP33).

The processor 14 determines whether or not the variable T matches the variable T_END (SP34). Note that the processor 14 stores the work in the time-series order for the minimum plan information 1531A whose elements are empty in the subsequent processing, and at this time, the time required for each work is cumulatively added to the variable T. . Therefore, when the variable T after the cumulative addition matches the variable T_END, all the operations are stored in the minimum plan information 1531A. On the other hand, when the variable T does not match the variable T_END, there is still work to be stored in the minimum plan information 1531A.

If the processor 14 obtains a negative result in the determination at step SP34, it determines that there is still work to be stored in the minimum plan information 1531A. Therefore, the processor 14 refers to the work database 1523 and extracts work that matches the values assigned to the variables K and X (SP35).

Next, the processor 14 selects one work whose work time is shorter than the time obtained by subtracting the variable T from the variable T_END from the work extracted in step SP35, and sets the work ID of the selected work to the variable L. Substituting, the working time is substituted into the variable M, and the end position is substituted into the variable X (SP36).

When the work time of the selected work is empty, the processor 14 substitutes the time of the minimum unit designated in advance for the variable M. If the end position is empty, the variable X is not updated. Further, since there are a finite number of operations to be selected in step SP36, it is possible to cover all possible operation plan patterns using existing algorithms such as dynamic programming.

Next, the processor 14 substitutes the work with the start time as the variable T, the end time as T + M, and the work ID as L in the minimum plan information 1531A (SP37). Then, the processor 14 substitutes T + M for the variable T (SP38), and moves to step SP34.

The processor 14 repeats the above processing (SP34 to SP38) until the variable T matches T_END. When the processor 14 obtains a positive result in the determination at step SP34, it stores the minimum plan information 1531A in the plan database 1531 (SP39), This plan creation process is terminated.

As described above, the plan creation process described here is the minimum plan information that can be executed in one mining machine (for example, dump) and one work date (for example, 2013/6/3 from 9:00 to 18:00). 1531A is created. The processor 14 creates a plurality of plans for one mining operation by executing the plan creation processing described here for other mining machines and other business dates.

Further, when creating a plurality of plans, the processor 14 stores an element in which items other than the plan ID are empty in the plan management database 1532. Items other than the plan ID are stored in the processing of steps SP4 and SP5 (FIG. 14).

FIG. 16 shows a processing procedure for the constraint confirmation processing. This constraint checking process is executed when the process in the planning process (FIG. 14) has shifted to step SP4.

First, the processor 14 refers to the plan management database 1532 to determine whether or not there is a plan in which the constraint confirmation column 15327 is not “1” (the constraint has not been confirmed) (SP41). When the processor 14 obtains a positive result in the determination at step SP41, it determines that there is a plan that has not been checked for constraints, sets “1” in the constraint check field 15327 corresponding to the plan that has not been checked for constraints, and The plan ID of the plan is extracted (SP42).

Next, the processor 14 refers to the plan database 1531 and extracts the plan specified by the extracted plan ID (SP43). Next, the processor 14 refers to the work database 1523 and the human resource database 1527 and confirms whether or not the plan that has not been subjected to the constraint confirmation extracted in step SP43 satisfies the personnel constraint (SP44).

Describing step SP44 in detail, the processor 14 refers to the work database 1523, extracts the work that matches the work ID in the execution work column 15316 of the plan that has not been checked for constraints extracted in step SP43, and extracts the work of the extracted work By further extracting the work whose classification field 15233 is “maintenance”, the number of maintenance work performed simultaneously on each date and each time is calculated.

Then, the processor 14 refers to the human resource database 1527 and confirms that the number of maintenance operations performed simultaneously at each date and time is equal to or less than the number of maintenance personnel in the maintenance personnel column 15272. The processor 14 sets “1” indicating that the personnel constraint is not satisfied in the personnel constraint column 15329 for a plan including a task in which the number of maintenance operations performed simultaneously is not less than the number of maintenance personnel.

Next, the processor 14 refers to the work database 1523 and the inventory database 1528 and confirms whether the plan that has not been checked for constraints extracted in step SP43 satisfies the stock constraints (SP45).

The step SP45 will be described in detail. The processor 14 refers to the work database 1523, extracts the work that matches the work ID in the execution work column 15316 of the plan that has not been checked for the constraint extracted in step SP43, and needs the extracted work. By further extracting the work in which the necessary parts are stored in the parts column 15239, the necessary parts and the number of parts are calculated for each date.

Next, the processor 14 refers to the inventory database 1528 to calculate the inventory parts and the number of parts that can be used for each date, and the number of parts of the calculated inventory parts has not been confirmed by the constraint extracted in step SP43. Confirm that the number of parts is more than necessary in the plan. Alternatively, the processor 14 refers to the inventory database 1528 and confirms that the availability date of the parts necessary for the maintenance work is after the maintenance work date performed in the plan that has not been checked for the restriction extracted in step SP43.

The processor 14 stores the plan including the work in which the number of parts in the inventory does not exceed the required number of parts or the plan including the work in which the available date of the parts required for the maintenance work is not after the maintenance work date in the inventory constraint column 15330. On the other hand, “1” indicating that the inventory constraint is not satisfied is set.

Next, the processor 14 refers to the work database 1523, the operation result database 1526, and the maintenance interval database 1529 to check whether or not the plan that has not been checked for constraints extracted in step SP43 satisfies the maintenance interval constraints (SP46).

The step SP46 will be described in detail. The processor 14 refers to the work database 1523, extracts the work that matches the work ID in the execution work column 15316 of the plan that has not been checked for the constraint extracted in step SP43, and extracts the work load thus extracted. By further extracting the work whose load information is stored in the information column 15237, the cumulative load between each maintenance work for each mining machine is calculated.

Next, the processor 14 refers to the maintenance interval database 1529 and confirms that the value in the post-maintenance continuous operation enable condition column 15292 is equal to or greater than the cumulative load between maintenance operations for each mining machine. Further, the processor 14 refers to the operation result database 1526 and confirms whether or not the load information of the mining machine at the beginning of the plan execution is equal to or greater than the value in the continuous operation possible condition column 15263. The processor 14 sets “1” indicating that the maintenance interval restriction is not satisfied in the maintenance interval restriction column 15331 for any element that is less than one.

Next, the processor 14 refers to the work database 1523 to check whether or not the plan that has not been checked for constraints extracted in step SP43 satisfies the dependency constraint (SP47).

Describing in detail about step SP47, the processor 14 refers to the work database 1523, extracts the work that matches the work ID in the execution work column 15316 of the plan that has not been checked for constraints extracted in step SP43, and depends on the extracted work. Elements for which a dependency relationship is specified in the relationship constraint column 15332 are further extracted.

Then, the processor 14 confirms whether or not the mining machine having the dependency relationship in the extracted work exists at the same time and at the same point as the mining machine of the extracted work. The processor 14 sets “1” indicating that the dependency constraint is not satisfied in the dependency constraint column 15332 for the plan including the work in which the dependency mining machine does not exist at the same time and at the same point.

The processor 14 refers to the plan management database 1532 to determine whether or not all the constraints of the personnel constraint, the inventory constraint, the maintenance constraint, and the dependency constraint are satisfied (SP48). If the processor 14 obtains a positive result in the determination at step SP48, it sets “0” indicating that the constraint is established in the constraint column 15328, and then proceeds to step SP41 to execute the above for other plans for which the constraint has not been confirmed. Repeat the processing (SP41 to SP48).

On the other hand, if the processor 14 obtains a negative result in the determination at step SP48, it refers to the plan management database 1532 and sets “1” indicating that the constraint is not established in the constraint column 15328 (SP49), and then step The process proceeds to SP41, and the above-described processing (SP41 to SP48) is repeated for other plans that have not been checked for constraints.

If the processor 14 obtains a negative result in the determination at step SP41, it determines that there is no plan that has not been checked for constraints in the plan management database 1532 and ends this constraint checking process.

(4) Effects of the present embodiment As described above, according to the planning support system 10 of the present embodiment, a plurality of operations that can be executed for one mining operation based on the relationship between the mining machine and the operation date and time. A plan to link the operation work and maintenance work by checking whether or not the created plans satisfy various constraints is extracted, and based on production volume, mineral market price and maintenance cost As a result, information on the profits of the entire mining operation that is predicted when a plan that satisfies various constraints is executed is calculated, and information on the calculated profits is presented for each plan that satisfies the various constraints. It is possible to formulate an optimal plan that takes profit into consideration.

(5) Other Embodiments FIG. 17 shows the overall configuration of a mine system 1A using a cloud as another embodiment. The mine system 1A according to another embodiment refers to the point that various information related to mine operations is collected in the cloud, the cloud creates and includes various databases (1521 to 1532) based on the collected various information, and the various databases. Thus, it differs from the mine system 1 described above in that a plan is prepared by executing various programs (1511 to 1517) provided in advance in the cloud.

As shown in Fig. 17, the cloud collects information necessary for creating various databases (1521-1532) from mining equipment, operation managers, maintenance personnel, parts inventory managers, offices and agents To do. Specifically, the cloud collects information such as sensor data and operation results from the mining machine and creates an operation result database 1526.

Also, the cloud collects operation restrictions and mine information from the operation manager, and creates a calendar database 1521, a mining machine database 1522, a work database 1523, a production volume database 1524, and a mineral market database 1525.

The cloud also collects information such as maintenance results, parts inventory, and shifts of maintenance personnel from maintenance personnel and parts inventory managers, and information such as necessary parts, standard work time, price, and shipping availability from agents. Thus, a human resource database 1527, an inventory database 1528, a maintenance interval database 1529, and a maintenance cost database 1530 are created.

The cloud can create the plan database 1531 and the plan management database 1532 by referring to these various databases (1521 to 1530) and executing various programs (1511 to 1517). The cloud can display information included in the created plan database 1531 and the plan management database 1532 so that it can be viewed on each terminal connected to the cloud.

As described above, according to the mine system 1A according to the other embodiment, information necessary for creating various databases can be directly collected from each person concerned via the network, so that it is troublesome for collection. The collected information can be quickly reflected in the plan database 1531 and the plan management database 1532. Therefore, even if it is necessary to change the plan on the way for some reason, the plan can be changed quickly.

1 Mining System 10 Planning System 1511 Plan Generation Program 1512 Personnel Confirmation Program 1513 Inventory Confirmation Program 1514 Maintenance Interval Confirmation Program 1515 Dependency Confirmation Program 1516 Amount Calculation Program 1517 Plan Presentation Program 1521 Calendar Database 1522 Mining Machine Database 1523 Work Database 1524 Production Volume Database 1525 Mineral market database 1526 Operation result database 1527 Personnel database 1528 Inventory database 1529 Maintenance interval database 1530 Maintenance cost database 1531 Plan database 1532 Plan management database 20 Client terminal

Claims (8)

1. In the planning support system for planning mining operations,
   A mining machine database having information on mining machines used in the mining operations;
   A calendar database having information on the work date and time for performing the mine work;
   A work database having work content information of work performed in the mining operation;
   A constraint database having information on operational and maintenance constraints of the mining machine;
   A profit database having information on profits of the mining operations;
   With a processor,
   The processor is
   Referring to the mining machine database, identify the mining machine that is the subject of the plan,
   Referring to the calendar database, specify the work date and time to be drafted of the plan,
   Referring to the work database, create a plurality of plans that can be executed by assigning work by the specified mining machine to the specified work date and time,
   With reference to the constraint database, a plan that satisfies the operational and maintenance constraints is extracted from the created executable plans.
   By referring to the profit database, information related to profits obtained when a plan that satisfies the operational and maintenance constraints is executed, and the calculated profit information is used as the operational and maintenance restrictions. A planning support system characterized by presenting each plan to be met.
2. The constraint database is
   A human resource database having information on the number of maintenance personnel secured on a business day for performing the mining operation;
   An inventory database having information on availability dates of parts required for maintenance work of the mining machine;
   An operation result database having information on the load immediately after the operation work of the mining machine;
   A maintenance interval database having information on allowable load immediately after maintenance work of the mining machine,
   The processor is
   With reference to the human resource database, a plan in which the number of necessary maintenance personnel is equal to or less than the number of maintenance personnel to be secured is extracted from the created plurality of executable plans,
   With reference to the inventory database, a plan in which the required maintenance work date is after the availability date is extracted from the created executable plans.
   With reference to the operation record database and the maintenance interval database, the load immediately after the operation operation of the mining machine is within the allowable load range immediately after the maintenance operation among the created executable plans. Extract the plan,
   The planning system according to claim 1, wherein plans corresponding to all of the extracted plans are extracted as plans satisfying the maintenance constraints.
3. The work database is
   In the information of the work content of the work to be performed in the mining work, it has dependency information indicating other work to be performed at the same time and at the same time in relation to one work,
   The processor is
   With reference to the dependency information, out of the created executable plans, extract a plan in which the other work is performed simultaneously with the one work,
   The planning system according to claim 1, wherein the extracted plan is extracted as a plan that satisfies the operational constraints.
4. The work database is
   In the work content information of the work to be performed in the mining work, it has information of work classification that classifies work that directly contributes to the production of resources and work that does not contribute directly to the production of resources,
   The processor is
   Referring to the profit database, information on profits obtained when a work that directly contributes to the resource is executed among a plurality of work included in the plan satisfying the operational and maintenance constraints is calculated. The planning system according to claim 1, wherein information relating to the calculated profit is presented for each plan satisfying the operational and maintenance constraints.
5. The work database is
   In the information on the work content of the work performed in the mining operation, it has information on the load of the mining machine when performing one work,
   The processor is
   With reference to the work database, when assigning work by the specified mining machine to the specified work date and time, the load of the mining machine is cumulatively added, and the plurality of executable plural loads having different loads of the mining machine The planning system according to claim 1, wherein a plan is created.
6. The profit database is
   A production database having information on the production of resources obtained when the work is performed;
   A mineral quotes database with resource quotes,
   A maintenance cost database having maintenance cost information when the maintenance work is performed,
   The processor is
   Referring to the production volume database, calculate the production volume of resources obtained when executing a plan that satisfies the operational and maintenance constraints,
   Referring to the mineral market database, calculate the sales by multiplying the calculated production amount with the market price,
   Referring to the maintenance cost database, calculating the maintenance cost when executing a plan that satisfies the operational and maintenance constraints,
   Net income is calculated by subtracting the maintenance cost from the sales,
   2. The planning support system according to claim 1, wherein the calculated net profit, sales, maintenance cost, and production amount are presented for each plan that satisfies the operational and maintenance constraints as information on the profit. .
7. In the planning support method of the planning support system for planning a mine operation plan,
   The planning support system includes a processor,
   The processor is
   Referring to a mining machine database having information on mining machines to be used in the mining operation, a first step of identifying a mining machine to be planned;
   A second step of identifying a work date and time to be drafted in the plan with reference to a calendar database having information on a work date and time for performing the mine work;
   A third database that creates a plurality of executable plans by referring to a work database having work content information of work performed in the mining work and assigning work by the specified mining machine to the specified work date and time. Steps,
   A reference is made to a constraint database having information on constraints on operation and maintenance of the mining machine, and a plan satisfying the constraints on operation and maintenance is extracted from the created plurality of executable plans. 4 steps,
   Referring to a profit database having information on profits of the mining operations, information on profits obtained when a plan that satisfies the operational and maintenance constraints is executed, and information on the calculated profits is calculated And a fifth step of presenting each plan that satisfies the above and maintenance constraints.
8. In the program of the planning support system for planning mining operations,
   On the computer,
   A function for identifying a mining machine to be drafted in the plan with reference to a mining machine database having information on a mining machine used in the mining operation;
   With reference to a calendar database having information on the business date and time for performing the mine business, a function for specifying the business date and time to be drafted of the plan,
   A function of creating a plurality of plans that can be executed by assigning work by the specified mining machine to the specified work date and time with reference to a work database having information on work contents of work performed in the mining work;
   A function of extracting a plan that satisfies the operational and maintenance constraints from among the plurality of executable plans created with reference to a constraint database having information on the operational and maintenance constraints of the mining machine When,
   Referring to a profit database having information on profits of the mining operations, information on profits obtained when a plan that satisfies the operational and maintenance constraints is executed, and information on the calculated profits is calculated And a program for each plan that satisfies the above maintenance constraints.
   
   
   

Images