WO2016143037A1 - Logistics plan generation method and system - Google Patents

Logistics plan generation method and system Download PDF

Info

Publication number
WO2016143037A1
WO2016143037A1 PCT/JP2015/056847 JP2015056847W WO2016143037A1 WO 2016143037 A1 WO2016143037 A1 WO 2016143037A1 JP 2015056847 W JP2015056847 W JP 2015056847W WO 2016143037 A1 WO2016143037 A1 WO 2016143037A1
Authority
WO
WIPO (PCT)
Prior art keywords
risk
logistics
plan
plan generation
logistics plan
Prior art date
Application number
PCT/JP2015/056847
Other languages
French (fr)
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/056847 priority Critical patent/WO2016143037A1/en
Publication of WO2016143037A1 publication Critical patent/WO2016143037A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • the present invention relates to a logistics plan generation method and system.
  • logistics necessary to carry materials and people necessary for operation are indispensable.
  • a logistics plan Since the efficiency of the logistics plan directly affects the cost, it is necessary to formulate an efficient plan as much as possible to reduce the cost.
  • the operation is stopped due to a shortage of goods, etc., it will be seriously damaged, so it is necessary to fully consider the risks. Therefore, it is necessary to develop a logistics plan that carries goods and people while taking risks and costs into consideration.
  • Patent Document 1 discloses a technique for assigning a large number of personnel to a predetermined place in consideration of human technical information, vacation acquisition status, and the like.
  • Patent Document 2 discloses a technique for assigning transportation equipment from supply and demand information.
  • JP 2003-157343 A Japanese Patent Laid-Open No. 11-328573
  • Patent Document 1 only assigns necessary persons to the required work, and does not consider a delivery method to the office.
  • Patent Document 2 although transportation equipment is allocated, since supply and demand information is fixed, it is not possible to consider a portion that can be made efficient by early departure as described above.
  • the present invention takes the above-mentioned problems into consideration and aims to generate a logistics plan for goods and people that is safe and low in cost.
  • a typical example of the invention disclosed in the present application is as follows.
  • the present invention is calculated from a standard plan generation unit that generates a logistics standard plan from supply and demand information of goods and human resource information, a stable production risk calculation unit that calculates stable production risk from the logistics standard plan, and a stable production risk calculation unit And a risk adjustment unit that adjusts the logistics standard plan based on the determined stable production risk. From the stable production risk calculated by the stable production risk calculation unit, the plan changeable part is extracted from the logistics plan generated by the standard plan generation unit, and the risk adjustment unit adjusts the plan within the changeable range and creates the logistics plan. Generate.
  • Another aspect of the present invention is a logistics plan generation method executed by a computer having a data input unit, a data output unit, and a processing unit that processes input data.
  • the processing unit is based on the stable production risk against the logistics standard plan, the standard plan generation unit that generates the logistics standard plan from the supply and demand information of goods and the human resource information, the stable production risk calculation unit that calculates the stable production risk
  • a risk adjustment unit that extracts a plan changeable part and adjusts the plan within a changeable range to generate a logistics plan.
  • the supply and demand information of goods includes information specifying the target goods, information specifying the place where the goods are supplied, and the time to be supplied.
  • the human resource information includes information specifying a human resource (for example, an employee), and information specifying a place where the human resource is arranged and a time zone (working time zone) where the human resource is to be arranged.
  • Logistics plan and logistics standard plan are the plans to transport goods and human resources to the place specified by the time specified by supply and demand information and human resource information. Including.
  • a personnel information update unit for updating personnel information using the adjustment result of the logistics standard plan.
  • the personnel information includes, for example, information on working conditions such as information for identifying employees and information on remuneration.
  • the operational risk and the delivery risk can be considered as the stable production risk.
  • the operation risk includes, for example, an action risk that is a possibility that an operation error may occur during human work.
  • the operation risk may include a failure risk that the device does not operate normally during operation due to aging or exceeding the maintenance cycle.
  • the delivery risk includes a shortage risk that may cause a predetermined schedule to not be executed due to, for example, a delivery delay of human resources or goods.
  • the delivery risk may include a demand fluctuation in which the demand for delivery goods to be delivered suddenly fluctuates.
  • factors that affect the overall schedule of processes defined in the production management table can be extracted and various definitions can be made.
  • the defined risk is embodied as a model or formula that is processed in the system.
  • behavioral risk can be represented using a human state model that is a function of time difference from the logistics reference plan.
  • a low-risk and low-cost logistics plan can be made by considering various risks.
  • notations such as “first”, “second”, and “third” are attached to identify the constituent elements, and do not necessarily limit the number or order.
  • a number for identifying a component is used for each context, and a number used in one context does not necessarily indicate the same configuration in another context. Further, it does not preclude that a component identified by a certain number also functions as a component identified by another number.
  • FIG. 1 is a diagram showing a configuration example of an apparatus according to the first embodiment of the present invention.
  • the data management server 101, the logistics plan generation server 111, and the monitoring server 121 are connected by a network 100.
  • the network 100 is a LAN (Local Area Network) or an Internet line.
  • LAN Local Area Network
  • FIG. 1 three servers advance the process in cooperation, but this server division method is an example and is not limited to this. Each server may be further divided or integrated.
  • the data management server 101 includes a CPU (Central Processing Unit) 102, an output device 103, an input device 104, a memory 105, a network interface 106, and an external storage device 107 connected to each other via a bus.
  • CPU Central Processing Unit
  • the CPU 102 is an arithmetic processing unit that executes various processes by processing a program stored in the memory 105.
  • the external storage device 107 is a storage device that stores data used by a program main body stored in the memory 105 or a program stored in the memory 105.
  • the memory 105 is a storage device that stores a program processed by the CPU 102 and data used. Programs and data that are not processed by the CPU 102 are stored in the external storage device 107.
  • the memory 105 stores a program that realizes the function of the demand calculation unit 203.
  • the external storage device 107 stores a personnel information table 201, a production management table 202, a material demand table 204, and a human resource management table 205.
  • a table used for logistic plan generation for example, transportation equipment data, production Data of necessary equipment may be stored.
  • the output device 103 is a display device such as a display.
  • the output device 103 displays information on the personnel information table 201, the production management table 202, the material demand table 204, and the personnel management table 205. Further, other data, an interface for managing these data, and the like may be displayed as necessary.
  • the input device 104 is an input device such as a keyboard or a mouse. Using the input device 104, it is possible to add, change, and delete information in the personnel information table 201, production management table 202, material demand table 204, and human resource management table 205.
  • the network interface 106 is an interface device for connecting and communicating with the logistics plan generation server 111, the monitoring server 121, and other external computers and monitoring devices.
  • the logistics plan generation server 111 includes a CPU 112, an output device 113, an input device 114, a memory 115, a network interface 116, and an external storage device 117 connected to each other by a bus.
  • the external storage device 117 stores a human state model table 207.
  • the memory 115 stores programs for realizing the functions of the logistics plan generation unit 211 and the logistics plan setting unit 212.
  • the monitoring server 121 includes a CPU 122, a memory 123, an input device 124, an output device 125, a network interface 126, and an external storage device 127 that are connected to each other via a bus.
  • the external storage device 127 stores a monitoring data table 206.
  • FIG. 2 is a software block diagram for realizing a logistics plan generation process performed in the system of FIG. As described above, processing can be arbitrarily shared by the three servers. The overall flow of the logistics plan generation process will be described with reference to FIG.
  • the demand calculation unit 203 supplies the material based on the future production plan stored in the production management table 202 and the individual worker information stored in the personnel information table 201. And demand for both people.
  • the necessary materials and people are different between the stage of oil well development for oil extraction and the stage of extracting crude oil from the developed oil well. Therefore, the demand for goods and people is determined according to the future production plan and the nature of the well to be developed.
  • a known method is used to determine a person to be actually assigned to a necessary person.
  • a technique called nurse scheduling a person in charge of work is determined based on a combination of individual abilities and skills, whether or not a vacation is acquired, and the like.
  • the nurse scheduling technique may be used to determine demand information for human resources, or other techniques may be used.
  • the calculated demand for supplies is stored in the supply demand table 204, and the demand for people is stored in the personnel management table 205.
  • the logistics plan generation unit 211 generates a logistics plan using the calculated demand, various types of monitoring information stored in the monitoring table 206, and the human state model stored in the human state model table 207.
  • the plurality of generated logistics plans are presented to the user in the logistics plan setting unit 212. Then, the logistics plan selected from them is executed, and the data of the personnel information table 201 is updated according to the execution result.
  • a plurality of logistics plans are generated using indices such as cost, risk, and lead time and presented to the user side.
  • a single logistics plan may be generated.
  • the information in the personnel information table 201 is updated.
  • the update is performed in order to feed back the contents of the execution result to the person who worked. For example, to reduce the logistics cost, raise the assessment for those who have worked overtime.
  • the logistics plan generation unit 211 includes a reference plan generation unit 221, a stable production risk calculation unit 222, a risk adjustment unit 223, and a plan evaluation unit 224.
  • the reference plan generation 221 further includes a material distribution plan generation unit 231 and a human resource distribution plan unit 232.
  • the stable production risk calculation unit 222 includes an operation risk calculation unit 233 and a delivery risk calculation unit 234. Further, the operation risk calculation unit 233 includes a human behavior risk calculation unit 235 and a failure risk calculation unit 236, and the delivery risk calculation unit 234 includes a shortage risk calculation unit 237 and a demand fluctuation risk calculation unit 238.
  • FIG. 3 is a diagram showing a flow for generating a logistics plan using these components.
  • step 301 a period for which a logistics plan is to be input is input. For example, from the following month to 3 months later, or for the next year. This step may be omitted by holding a set value in advance.
  • step 302 the demand for goods and people required in the planning period determined in step 301 is calculated. This corresponds to the processing of the demand calculation unit 203.
  • Steps 303 to 308 correspond to processing of the logistics plan generation unit 211, and step 309 corresponds to processing of the logistics plan setting unit 212.
  • a material delivery plan is generated from data obtained from the material demand table 204 and the monitoring table 206.
  • This is equivalent to the conventional delivery plan generation method, and is also disclosed in Patent Document 2.
  • the calculation may be performed in consideration of external factors such as weather data included in the monitoring table 206, that is, weather, waves, and wind speed. This processing corresponds to the processing of the material delivery plan generation unit 231.
  • step 304 a person to be transported is assigned to the delivery plan using the data of the personnel management table 205 and the monitoring table 206.
  • This allocation indicates that people will be allocated as much as they can be transported without changing the schedule of transport equipment used for goods transportation. For those who cannot deliver only with the schedule of goods transportation, new transportation equipment is newly allocated. Transport equipment is set for helicopters and transport ships in consideration of cost and lead time. This corresponds to the processing of the personnel delivery plan generation unit 232.
  • step 305 the stable production risk is calculated and the plan is adjusted. This corresponds to the processing of the stable production risk calculation unit 222 and the risk adjustment unit 223.
  • the cost change due to the adjustment is calculated in step 306 and evaluated in step 307. If it is determined in step 307 that the total cost has been reduced from before the adjustment, step 309 is executed, otherwise step 308 is executed. Evaluation criteria may be stable production risk and lead time, not total cost.
  • step 308 parameters relating to delivery plan generation and assignment of people are changed, and step 303 is executed again. This means that the parameters used in step 303 and step 304 are changed, and the plan that becomes the reference before adjustment is regenerated.
  • Step 306, step 307, and step 308 correspond to the processing of the plan evaluation unit 224.
  • step 309 the personnel information is updated. This corresponds to the processing of the logistics plan setting unit 212.
  • the logistics plan executed by the user is selected, and the data stored in the personnel information table 201 is updated using the selection result.
  • the update may not be after the selection but after the logistics plan is actually executed.
  • FIG. 4 is a diagram showing an example of the personnel information table 201.
  • the personnel information table 201 stores records indicating workers and individual employees.
  • a typical example is employee data managed by the personnel department of a company, and includes information for identifying the employee, information such as qualification, salary, various benefits, and treatment.
  • the Person ID (Person IDentifier) 401 is an identifier for uniquely identifying the record, and any expression may be used as long as it can be uniquely identified.
  • Job 402 is an identifier for identifying an individual's job type, and may be a character string or some identifier that refers to data stored in another table.
  • Base Salary 403 is an employee's monthly salary amount
  • Assessment Value 404 is a value used for salary assessment, and here indicates an amount that is specially given at the next bonus. These values are values for performing personnel evaluation, and may be in other forms other than the amount.
  • Good Compatibility 405 and Bad Compatibility 406 indicate compatibility between individuals, Good Compatibility 405 indicates good compatibility, and Bad Compatibility 406 indicates poor compatibility. These values are used in the above-described processing of the demand calculation unit 203 to determine whether the compatibility is good or not when determining the team formation. Therefore, another format may be used as long as compatibility can be determined.
  • the individual is a Crane Operator who operates a crane, and the salary is $ 4,000 per month. Also, it is determined that $ 400 will be added at the next bonus.
  • the individual has a good compatibility with the person whose Person ID 401 is P2, and has a bad compatibility with the person whose Person is P4.
  • FIG. 4 shows two points of salary and compatibility, but other information such as ownership qualification, age, educational history, etc. may be stored.
  • FIG. 5 is a diagram illustrating an example of the production management table 202.
  • Each record of the production management table 202 stores each phase for each operation site and their start and end dates and associated items.
  • Phase ID (Phase IDentifier) 501 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
  • the target 502 is an identifier indicating what each record is targeted for, and may be a character string or an identifier stored in another table.
  • Phase 503 is an identifier indicating the phase of the activity, and may be in any format as long as the phase can be expressed.
  • Bdate 504 and Edit 505 represent the start date / time and end date / time of the phase, respectively. In the figure, it is described in the format of “year / month / day-hour / minute / second”, but other expression formats may be used, or only the date / year or the time may be used.
  • Remarks 506 describes information associated with the phase.
  • a format other than a character string may be used as long as the contents of information can be expressed. Moreover, it may be expressed by a plurality of columns.
  • Ph1 starts at 19:00 on November 13, 2014 and ends at 19:00 on December 13, 2014. It is shown that Ph2 starts at 19:00 on December 13, 2014 and ends at 19:00 on January 30, 2015.
  • the material demand table and the human resource management table which will be described later, are created in accordance with the constraints of the overall schedule defined by the production management table 202. For example, since the schedule of Ph1 in FIG. 5 is scheduled to start at 19:00 on November 13, 2014 and end at 19:00 on December 13, 2014, supplies and human resources are supplied in accordance with this schedule. It will be.
  • FIG. 6 is a diagram showing an example of the material demand table 204.
  • the material demand table 204 information on where and what from what to carry to each operation site is stored.
  • Demand ID (IDentifier) 601 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
  • Name 602 represents the name of the goods, and may be in a form other than a character string as long as similar contents can be represented.
  • Qty (Quantity) 603 indicates a necessary number or amount of the material, and is expressed in a format corresponding to the material, such as an amount when the content of the material is a medicine.
  • Source 604 and Destination 605 represent the start and end points when the goods are transported.
  • the Delivery date 606 expresses the deadline of the delivery, and other formats may be used as long as the same contents can be expressed.
  • a record whose Demand ID 601 is D1 indicates that it is necessary to carry one pipe from Port1 to Platform1. Moreover, it expresses that the deadline is 21:00 on December 13, 2014.
  • the material demand table 204 shown in FIG. 6 stores only minimum information related to the demand and delivery of goods, but other information such as delivery cost and price, precautions regarding delivery, and the like may also be stored.
  • FIG. 7 is a diagram showing an example of the human resource management table 205.
  • a person's work schedule is stored in each record.
  • the work schedule information is, for example, information indicating who is at what time and where.
  • a Shift ID (Shift IDentifier) 701 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
  • Work begin 702 and work end 703 respectively indicate the work start date and time and the work end date and time of each individual. Further, Location 704 indicates a work place.
  • the shift of P1 starts at 17:00 on December 13, 2014 and is scheduled to end at 17:00 on December 26, 2014. Further, it is indicated that the work place is Platform1.
  • the human resource management table 205 shown in FIG. 7 presents only the minimum data that should be provided as a work schedule, but other data such as necessary equipment and a detailed schedule may be presented.
  • FIG. 8 is a diagram illustrating an example of the monitoring table 206.
  • Each record indicates the status of the monitoring target, and indicates, for example, an individual, transportation equipment, weather, or the like.
  • a Monitor ID (IDentifier) 801 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
  • Update Time 802 is the date and time when the target information was last acquired.
  • Target 803 indicates a monitoring target
  • Location 804 indicates the location of the monitoring target.
  • Remarks 805 indicates information other than those described above, and stores, for example, labor status and sickness status for individuals, weather for weather, and fatigue status and operating cost of devices for equipment. These pieces of information may be stored in a plurality of columns or another table, instead of a single column. Each record also holds all past monitoring results, but only the latest results may be held.
  • FIG. 9 is a flowchart showing the plan adjustment process, which corresponds to step 305.
  • step 901 a location that can be adjusted to a low-cost transport device is detected by changing the time of departure and arrival times of the transport device and changing the start and end times of the person.
  • Step 902 Steps 903 to 905 are repeated for all the adjustable portions detected in Step 901. An example of the place where the plan can be adjusted is described with reference to FIG.
  • step 903 a delivery risk is calculated, and in step 904, an operation risk is calculated.
  • step 905 a stable production risk is calculated from the calculated delivery risk and operation risk.
  • step 906 the type and time of the delivery device and the working hours of the employee are changed for the portion where the stable production risk after the change is equal to or less than the stability threshold.
  • the locations that can be adjusted may be searched by a desired index such as the maximum number of locations that can be adjusted or the lowest total cost value by computer simulation or the like.
  • FIG. 10 is a diagram showing an example of a place where the plan can be adjusted.
  • a logistics plan between Port1 and Platform1 and a work plan in Platform1 are targeted.
  • the situation 1001 shows the reference plan before the change, that is, the adjustment plan created in Step 303.
  • An example of the situation 1001 represents information in the material information table 204 and the human resource information table 205.
  • Port 1 is a mainland port
  • Platform 1 is an offshore platform. That is, the exemplary schedule is not a railroad or a bus, but a plan having uncertain elements such as a ship or an airplane.
  • a delivery plan using the helicopter H1 and the transport ship V1 is set up from Port1. That is, the plan is to carry the person P1 who is the substitute for the person P4 by the helicopter H1, and the plan to carry the materials necessary for the operation of the Platform 1 by the transport ship V1.
  • Helicopter H1 departs from Port 1 at 15:00 on December 13, 2014 and arrives at Platform 1 at 16:00 on December 13, 2014.
  • the helicopter H1 carries a person P1 who is a substitute for the person P4 who finishes working at 17:00 on December 13, 2014. And after work shift, the person P4 is carried to Port1. At this time, the helicopter H1 departs from Platform 1 at 18:00 on December 13, 2014, and arrives at Port 1 at 19:00 on December 13, 2014.
  • the transport ship V1 is supposed to carry a pipe whose Demand ID 601 is D1, and needs to arrive by Platform 1 on December 13, 2014 at 21:00. Therefore, Port 1 departs at 17:00 on December 13, 2014, and arrives at Platform 1 at 20:00 on December 13, 2014. After that, loading and unloading of goods and receiving of unnecessary goods are performed over 5 hours, and the platform 1 is departed at 1 o'clock on December 14, 2014. And it returns to Port1 at 6:00 on December 14, 2014.
  • the change time of the person P4 and the person P1 is different from the scheduled delivery time of the pipe D1, and cannot be carried by a single transport device.
  • the working hours are simply shifted backward, the risk that the employee will make operational mistakes due to fatigue or the like increases.
  • the arrangement location is not secured or the subsequent consumption plan is affected. Therefore, simple time adjustment is difficult because it contains various risks.
  • the result of the planned adjustment in this example is shown in the situation 1002.
  • the planned adjustment is a result of considering various risks shown in FIGS. 11 and 12.
  • the plan is adjusted so that the pipe D1 and the person P1 are simultaneously carried by the transport ship V1. Thereby, it becomes possible to reduce the cost of using the helicopter H1.
  • the working hours of person P4 will be until 20:00 on December 13, 2014, and overtime will be added for 3 hours.
  • a risk such as an operation error during overtime is calculated as a human behavior risk using the human state model shown in FIG.
  • this adjustment is performed within the range of the constraint conditions defined by the production management table 202. Whether adjustment is physically possible is determined by referring to the monitoring table 206. Adjustments shall be made within the scope of various laws and regulations to be followed. For example, if there is a law that regulates the working hours of workers or a law that regulates the operating speed of a transport ship, adjustments are made within a range that satisfies the conditions.
  • FIG. 11 is a diagram showing an example of a human state model.
  • FIG. 11 it is written in the form of a graph, but it may be a mathematical expression or a model obtained by machine learning.
  • a model 1101 and a model 1102 respectively represent human condition risk models of Crane Operator and Ballast Control Operator.
  • Such a model can be created on the basis of statistical data for each type of business and type of error. Alternatively, it may be generated for each employee using data of past work results and prepared for each individual.
  • the definition of business content and error content is arbitrary and may be subdivided or may be defined to some extent.
  • a human state model is defined for each occupation, but a known human error model or the like may be used as long as it is possible to calculate the risk of occurrence of human operation errors such as individual or age.
  • FIG. 12 shows an example of a stable production risk calculation method using various risks.
  • the delivery risk calculation formula 1201 is an example of a method for calculating a delivery risk, that is, a risk of delivery stagnation and a missing item from a factor due to weather and a time difference that is a difference from the initial schedule, for simplicity.
  • the shortage risk is a possibility that the entire schedule defined by the production management table 202 cannot be executed due to, for example, a delivery delay of human resources or supplies.
  • this risk is defined by the delivery risk calculation formula 1201 and assumes that the shortage risk becomes unacceptable when the value reaches a predetermined value.
  • the weather factor coefficient varies depending on the weather. For example, the value is 0.5 depending on the weather, 2 if raining, and the like.
  • the delivery adjustment coefficient is a constant for adjusting the range.
  • the operation risk calculation formula 1202 is a formula for calculating a human behavior risk that causes an operation mistake, and is calculated from the human state model shown in FIG.
  • the operational risk is, for example, the possibility of an operational error occurring during human work.
  • various types of information are introduced as coefficients using the model 1101 is shown.
  • the injury and illness state coefficient, the immediately preceding state coefficient, and the activity history coefficient are coefficients that are determined by an individual's injury and illness state, the latest activity such as sleep and rest, and the time required for the latest work.
  • the behavior adjustment coefficient is a constant for adjusting the area of operational risk. As described with reference to FIG. 11, the model is determined depending on the work content, the operator, and the type of operation error.
  • the stable production risk calculation formula 1203 is calculated by treating the delivery risk calculation formula 1201 and the operation risk 1202 as probability values.
  • the calculation is based on the example shown in FIG. 10, the weather factor coefficient is 2, the delivery adjustment coefficient is 4, the sickness condition coefficient is 0.5, the immediately preceding condition coefficient is 1, the activity history coefficient is 1, The behavior adjustment coefficient is calculated as 3.
  • the shortage risk is considered as the delivery risk
  • the human behavior risk related to the behavior such as the operation mistake is considered as the operation risk
  • other various risks may be considered.
  • demand fluctuation risk that demand of delivery goods suddenly fluctuates due to demand fluctuation for example, possibility that supplies can not be procured as planned or suddenly necessary supplies
  • risks may be taken into consideration, such as a failure risk that a replacement part is required due to damage to the equipment, and a human relationship risk that the combined team does not perform as planned.
  • One of the methods for calculating stable production risk using these risks is the same as the method shown in FIG. 12, in which various risks are calculated as probability values, and the probability that an accident will occur due to one of the risks is calculated. However, other methods may be used.
  • the probability that a failure or operation error will occur when operating the equipment is determined from the human behavior risk and failure risk.
  • the probability that the necessary goods are not in the required time and place from the demand fluctuation risk is defined as the delivery risk, and the probability that either the operation risk or the delivery risk occurs is defined as the stable production risk.
  • Demand fluctuation risk is calculated using economics, and failure risk is calculated using known techniques such as predictive diagnosis.
  • step 309 adds such information to the personnel information in order to reward such extension or shortening with a subsequent bonus or special reward.
  • the working time of the person P4 is extended.
  • the Asset Value 404 in the personnel information table 201 is increased in order to be reflected in overtime pay and later rewards.
  • Such personnel information may be updated by simply acquiring a substitute holiday or lengthening a later holiday in addition to simply increasing the amount.
  • FIG. 13 shows a GUI (Graphical User Interface) used in the logistics plan setting unit 212.
  • a window 1301 inputs parameters necessary for the logistics plan generation unit 211 and displays the generated plan.
  • the planning target period 1302 is an input field for designating a period for generating a logistics plan.
  • the stability threshold 1303 is set to a value used in step 906. These values may be input by the user, or the automatically set values may be displayed.
  • Cost weight 1304 and risk weight 1305 are parameters used when presenting the adjustment result to the user.
  • the table starting with Plan No. 1306 presents a part of a plurality of plans generated by the logistics plan generation unit 211.
  • Plan No. 1306 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
  • the cost 1307 indicates the cost required for the generated plan
  • the average stable production risk 1308 indicates a value obtained by averaging the stable production risks at all locations adjusted by the risk adjustment unit 223.
  • the performance 1309 is a value calculated from the cost weight 1304, the cost 1307, the risk weight 1305, and the average stable production risk 1308, and is used for the user to select a plan to be executed from a plurality of plans. For example, in the record whose Plan No. 1306 is 1, calculation is performed by dividing the value obtained by multiplying the average stable production risk 1308 by the risk weight 1305 and the cost 1307 by the cost weight 1304.
  • the cost 130 can be calculated by, for example, predetermining the unit price per hour for each means of transportation and work based on the logistics plan shown in FIG.
  • the graph display 1310 is a graph for clearly showing the trade-off relationship of each generated plan.
  • the values of the cost 1307, the average stable production risk 1308, and the performance 1309 are successively shown, and the positions of the plans are illustrated. As a result, it is possible to easily grasp whether the plan generated by the user is cost advantage or risk advantage.
  • the cost and average stable production risk are shown, but the lead time and the number of adjustment points may be displayed as selection indicators.
  • the plan details 1311 indicate a part of the contents of the selected plan and a part of personnel information changed by execution of the plan. All or a part of the personnel information can be hidden by the viewing authority determined by the ID of the accessing user.
  • Vehicle 1312 indicates the ID of the transport device
  • Target 1313 indicates the ID of the transport target.
  • Begin 1314 and End 1315 indicate the transportation start date and time and the transportation end date and time, respectively.
  • Source 1316 and Destination 1317 indicate a transportation source and a transportation destination.
  • the transport device V1 departs Port1 at 16:00 on December 13, 2014 and arrives at Platform1 at 19:00 on the same day. Thereafter, the employee P4 and the pipe D1 are lowered, and the employee P1 is put on. Then, it is shown that Platform1 departs at 0 o'clock on December 14, 2014 and arrives at Port 1 at 5 o'clock on the same day.
  • the post-update personnel information table 1318 is a part of the personnel information table 201, and shows a record updated when the selected plan is executed and its contents.
  • GUI it is possible to generate a logistics plan for a specified period and allow the user to select a plan to be executed from the viewpoint of cost and risk.
  • the user may have a function of modifying the details of the selected plan.
  • a different interface may be used or another input / output may be added.
  • FIG. 14 is a diagram showing a configuration example of the second embodiment of the present invention. In the following description, the same components as those in FIG.
  • the second embodiment includes a human state model automatic generation unit 1401 in addition to the components of the first embodiment (see FIG. 1) described above.
  • the human state model automatic generation unit 1401 automatically generates a human state model using data in the monitoring data table 206.
  • FIG. 15 is a block diagram illustrating human state model automatic generation according to the second embodiment of this invention. The overall flow of the human state model automatic generation will be described with reference to FIG. In the following description, the same components as those in FIG.
  • the automatic generation process of the human state model is executed with the update of the personnel information table 201, the user input, and the update of other tables as a trigger.
  • the human state model automatic generation unit 1401 extracts monitoring data to be learned. Then, among the data, data related to work behavior is acquired from the monitoring data table 206, a human state model is generated, and stored in the human state model table 207.
  • FIG. 16 is a flowchart of the human state model automatic generation process.
  • step 1601 data that is personal data to be processed and whose Work is included in the action of Remarks 805 is extracted from the monitoring table 206.
  • step 1602 classification is performed for each status of Remarks 805 in the extracted data.
  • step 1604 and step 1605 are repeated for each extracted status.
  • step 1604 the time required for the target work is set from the work start time to Update time 802, and work that is more than twice the standard deviation from the average of the time required fails, and otherwise, the work success is counted as failure.
  • step 1605 a sigmoid function is estimated with failure as 1 and success as 0 and the required time as input, and the estimated result function is stored in the human state table 207.
  • each embodiment of the present invention has been described above. However, each of the above embodiments shows one application example of the present invention, and the technical scope of the present invention is limited to the specific configuration of each of the above embodiments. It is not the purpose.
  • the present invention is not limited to the embodiments described above, and includes various modifications. For example, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace the configurations of other embodiments with respect to a part of the configurations of the embodiments.
  • the above configuration may be configured by a single computer, or may be configured by another computer in which any part of the input device, output device, processing device, and storage device is connected via a network.
  • functions equivalent to those configured by software can also be realized by hardware such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit). Such an embodiment is also included in the scope of the present invention.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Quality & Reliability (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The purpose of the present invention is to form a low-risk, low-cost logistics plan for dealing with both goods and people simultaneously by considering various risks. Provided is a logistics plan generation method that is executed by a computer capable of performing at least data input, data output, and inputted data processing, the method provided with: a reference plan generation unit for generating a logistics reference plan from supply and demand information of goods and human resource information of people; a stable production risk calculation unit for calculating stable production risk; and a risk adjustment unit for adjusting, on the basis of the stable production risk calculated by the stable production risk calculation unit, the logistics reference plan generated by the reference plan generation unit. The logistics plan generation method is characterized by extracting, with respect to the logistics plan generated by the reference plan generation unit, a plan-changeable part on the basis of the stable production risk calculated by the stable production risk calculation unit, and generating a logistics plan by adjusting the plan within the changeable range by the risk adjustment unit.

Description

ロジスティクス計画生成方法およびシステムLogistics plan generation method and system
 本発明はロジスティクス計画生成方法およびシステムに関する。 The present invention relates to a logistics plan generation method and system.
 Oil&Gas分野を含む資源採掘等の分野においては、操業に必要な物資と人を運ぶロジスティクスが必要不可欠である。例えば、洋上プラットフォームで油田開発を行う場合、当該洋上プラットフォームに対して、開発に必要な機器や、当該機器を運用するための消耗品、またそれらを扱う作業員を運ぶ必要がある。そのため、物資と人を運ぶための配送計画、すなわちロジスティクス計画を立案する必要がある。当該ロジスティクス計画の効率はコストに直接影響するため、可能な限り効率的な計画を立案し、コストを低減する必要がある。一方で、物資の欠品等で操業停止に陥った場合、深刻な損害を被ることから、リスクを十分考慮する必要がある。そのため、リスクおよびコストを考慮しつつ、物資と人を運ぶロジスティクス計画を立案する必要がある。 In logistics and other fields, including the Oil & Gas field, logistics necessary to carry materials and people necessary for operation are indispensable. For example, when oil field development is performed on an offshore platform, it is necessary to carry equipment necessary for development, consumables for operating the equipment, and workers who handle them to the offshore platform. Therefore, it is necessary to make a delivery plan for carrying goods and people, that is, a logistics plan. Since the efficiency of the logistics plan directly affects the cost, it is necessary to formulate an efficient plan as much as possible to reduce the cost. On the other hand, if the operation is stopped due to a shortage of goods, etc., it will be seriously damaged, so it is necessary to fully consider the risks. Therefore, it is necessary to develop a logistics plan that carries goods and people while taking risks and costs into consideration.
 そのようなロジスティクス計画立案方法の一例として、例えば、特許文献1には人の技術情報や休暇取得状況等も考慮して、多数の人員を所定の場所にアサインする技術が開示されている。また、物資の配送に関しては、特許文献2に、需給情報から輸送機器の割り当てを行う技術が開催されている。 As an example of such a logistics planning method, for example, Patent Document 1 discloses a technique for assigning a large number of personnel to a predetermined place in consideration of human technical information, vacation acquisition status, and the like. Regarding delivery of goods, Patent Document 2 discloses a technique for assigning transportation equipment from supply and demand information.
特開2003-157343号公報JP 2003-157343 A 特開平11-328573号公報Japanese Patent Laid-Open No. 11-328573
 しかしながら、従来のロジスティクス計画立案に関する技術は、物資または人のどちらか一方にのみ着目しており、両方を考慮して効率的なロジスティクス計画を立案することは困難であった。例えば、物資と人を単に配送する対象と捉えてロジスティクス計画立案を行った場合、勤務計画上、配送対象の人物が1時間早出することにすれば物資と人を両方同時に運べるが、そうでなければ2台の輸送機器が必要になる等、効率化可能な箇所を考慮できないという問題があった。 However, conventional techniques related to logistics planning focus only on either goods or people, and it is difficult to formulate an efficient logistics plan considering both. For example, if a logistics plan is created by simply considering supplies and people as objects to be delivered, it will be possible to carry both goods and people at the same time if the person to be delivered is one hour earlier in the work plan. For example, two transport devices are required, and there is a problem that it is not possible to consider a place where the efficiency can be improved.
 なお、特許文献1で開示されている技術は、求められる仕事に対して必要な人をアサインするのみであり、勤務地までの配送方法は考慮されていない。また、特許文献2では、輸送機器の割り当ては行っているが、需給情報が固定であるため、上述のような、早出によって効率化可能な部分を考慮することはできない。 Note that the technique disclosed in Patent Document 1 only assigns necessary persons to the required work, and does not consider a delivery method to the office. In Patent Document 2, although transportation equipment is allocated, since supply and demand information is fixed, it is not possible to consider a portion that can be made efficient by early departure as described above.
 本発明は、上述のような問題を考慮したものであって、安全かつ低コストである、物資と人のロジスティクス計画を生成することを目的とする。 The present invention takes the above-mentioned problems into consideration and aims to generate a logistics plan for goods and people that is safe and low in cost.
 本願において開示される発明の代表的な一例を示せば以下の通りである。本発明は、物資の需給情報および人の人材情報からロジスティクス基準計画を生成する基準計画生成部と、ロジスティクス基準計画から安定生産リスクを計算する安定生産リスク算出部と、安定生産リスク算出部から算出された安定生産リスクに基づいてロジスティクス基準計画を調整するリスク調整部と、を備えるシステムである。基準計画生成部によって生成されたロジスティクス計画に対し安定生産リスク算出部が算出する安定生産リスクから計画変更可能な部分を抽出し、リスク調整部が当該変更可能な範囲で計画を調整しロジスティクス計画を生成する。 A typical example of the invention disclosed in the present application is as follows. The present invention is calculated from a standard plan generation unit that generates a logistics standard plan from supply and demand information of goods and human resource information, a stable production risk calculation unit that calculates stable production risk from the logistics standard plan, and a stable production risk calculation unit And a risk adjustment unit that adjusts the logistics standard plan based on the determined stable production risk. From the stable production risk calculated by the stable production risk calculation unit, the plan changeable part is extracted from the logistics plan generated by the standard plan generation unit, and the risk adjustment unit adjusts the plan within the changeable range and creates the logistics plan. Generate.
 本発明の他の側面は、データ入力部、データ出力部、入力されたデータの処理を行う処理部を有する計算機で実行されるロジスティクス計画生成方法である。処理部は、物資の需給情報および人の人材情報からロジスティクス基準計画を生成する基準計画生成部と、安定生産リスクを計算する安定生産リスク算出部と、ロジスティクス基準計画に対し、安定生産リスクに基づいて計画変更可能な部分を抽出し、変更可能な範囲で計画を調整しロジスティクス計画を生成する、リスク調整部と、を備える。 Another aspect of the present invention is a logistics plan generation method executed by a computer having a data input unit, a data output unit, and a processing unit that processes input data. The processing unit is based on the stable production risk against the logistics standard plan, the standard plan generation unit that generates the logistics standard plan from the supply and demand information of goods and the human resource information, the stable production risk calculation unit that calculates the stable production risk A risk adjustment unit that extracts a plan changeable part and adjusts the plan within a changeable range to generate a logistics plan.
 より具体的な例を以下に例示する。物資の需給情報とは、対象とする物資を特定する情報と、当該物資が供給される場所、および供給されるべき時間を指定する情報を含む。人材情報とは、人材(例えば従業者)を特定する情報と、当該人材が配置される場所、および配置されるべき時間帯(作業時間帯)を指定する情報を含む。ロジスティクス計画、ロジスティクス基準計画とは、物資および人材を、需給情報および人材情報の指定する時間までに指定する場所に輸送する計画であり、輸送手段、輸送対象物、出発地、目的地の情報を含む。 More specific examples are shown below. The supply and demand information of goods includes information specifying the target goods, information specifying the place where the goods are supplied, and the time to be supplied. The human resource information includes information specifying a human resource (for example, an employee), and information specifying a place where the human resource is arranged and a time zone (working time zone) where the human resource is to be arranged. Logistics plan and logistics standard plan are the plans to transport goods and human resources to the place specified by the time specified by supply and demand information and human resource information. Including.
 さらに好ましい具体的な例では、ロジスティクス基準計画の調整結果を用いて人事情報を更新する人事情報更新部を有する。人事情報は、例えば、従業員を識別する情報と報酬に関する情報などの勤務条件に関する情報を含む。また、リスクの具体例としては、安定生産リスクは、操業リスクや配送リスクを考慮することができる。操業リスクは、例えば、人の作業中に操作ミスが発生する可能性である行動リスクを含む。また、操業リスクは、経年劣化またはメンテナンスサイクルの超過により操業中に機器が正常に動作しなくなる故障リスク等を含んでもよい。また、配送リスクは、例えば人材または物資の配送遅延により、定められたスケジュールを実行できなくなる可能性である欠品リスクを含む。また、配送リスクは配送すべき配送物資の需要が急に変動する需要変動を含んでもよい。これらのリスクについては、例えば、生産管理テーブルで定義される工程の全体スケジュールに影響を与える要因を抽出し、種々の定義を行うことができる。定義されたリスクは、システム内で処理されるモデルまたは数式として具現化される。例えば、行動リスクは、ロジスティクス基準計画からの時間差分の関数である人間状態モデルを用いて表すことができる。 In a more preferable specific example, a personnel information update unit for updating personnel information using the adjustment result of the logistics standard plan is provided. The personnel information includes, for example, information on working conditions such as information for identifying employees and information on remuneration. As a specific example of the risk, the operational risk and the delivery risk can be considered as the stable production risk. The operation risk includes, for example, an action risk that is a possibility that an operation error may occur during human work. In addition, the operation risk may include a failure risk that the device does not operate normally during operation due to aging or exceeding the maintenance cycle. Further, the delivery risk includes a shortage risk that may cause a predetermined schedule to not be executed due to, for example, a delivery delay of human resources or goods. Further, the delivery risk may include a demand fluctuation in which the demand for delivery goods to be delivered suddenly fluctuates. For these risks, for example, factors that affect the overall schedule of processes defined in the production management table can be extracted and various definitions can be made. The defined risk is embodied as a model or formula that is processed in the system. For example, behavioral risk can be represented using a human state model that is a function of time difference from the logistics reference plan.
 ロジスティクス基準計画の調整手法は種々考えられるが、コストに着目した例では、物資輸送に用いられる輸送機器のスケジュールを一切変更せずに、人を追加で輸送可能な分だけ割り当てる。その後、当該調整によって生じる上記のリスクを評価し、許容範囲内かどうか閾値等を用いて判定する。許容リスク範囲内で調整された計画は、コストを再評価され、コスト低減効果があれば、当該計画を採用する。 There are various methods for adjusting the logistics standard plan, but in the case of paying attention to the cost, all the people who can be transported are allocated without changing the schedule of transport equipment used for transporting goods. After that, the above-mentioned risk caused by the adjustment is evaluated, and it is determined using a threshold value or the like whether or not it is within an allowable range. The plan adjusted within the allowable risk range is re-evaluated, and if there is a cost reduction effect, the plan is adopted.
 本発明によれば、各種リスクを考慮することで、低リスクかつ低コストであるロジスティクス計画を立案することができる。 According to the present invention, a low-risk and low-cost logistics plan can be made by considering various risks.
本発明の第1の実施形態のロジスティクス計画生成装置の構成例を示すブロック図である。It is a block diagram which shows the structural example of the logistics plan production | generation apparatus of the 1st Embodiment of this invention. 本発明の第1の実施形態のロジスティクス計画生成処理を説明するブロック図である。It is a block diagram explaining the logistics plan production | generation process of the 1st Embodiment of this invention. 本発明の第1の実施形態のロジスティクス計画生成処理を示すフローチャートである。It is a flowchart which shows the logistics plan production | generation process of the 1st Embodiment of this invention. 本発明の第1の実施形態の人事情報テーブルの一例を示す表図である。It is a table | surface figure which shows an example of the personnel information table of the 1st Embodiment of this invention. 本発明の第1の実施形態の生産管理テーブルの一例を示す表図である。It is a table | surface figure which shows an example of the production management table of the 1st Embodiment of this invention. 本発明の第1の実施形態の物資需要テーブルの一例を示す表図である。It is a table | surface figure which shows an example of the goods demand table of the 1st Embodiment of this invention. 本発明の第1の実施形態の人材管理テーブルの一例を示す表図である。It is a table | surface figure which shows an example of the human resource management table of the 1st Embodiment of this invention. 本発明の第1の実施形態のモニタリングテーブルの一例を示す表図である。It is a table | surface figure which shows an example of the monitoring table of the 1st Embodiment of this invention. 本発明の第1の実施形態の計画調整処理を示すフローチャートである。It is a flowchart which shows the plan adjustment process of the 1st Embodiment of this invention. 本発明の第1の実施形態の調整可能箇所の一例を示すタイミング図である。It is a timing diagram which shows an example of the adjustable location of the 1st Embodiment of this invention. 本発明の第1の実施形態の人間状態リスクモデルの一例を示すグラフ図である。It is a graph which shows an example of the human condition risk model of the 1st Embodiment of this invention. 本発明の第1の実施形態の安定生産リスクの算出方法の一例を示す表図である。It is a table | surface figure which shows an example of the calculation method of the stable production risk of the 1st Embodiment of this invention. 本発明の第1の実施形態の管理用GUIの一例を示す平面図である。It is a top view which shows an example of management GUI of the 1st Embodiment of this invention. 本発明の第2の実施形態の人間状態モデル自動生成処理の構成例を示すブロック図である。It is a block diagram which shows the structural example of the human state model automatic generation process of the 2nd Embodiment of this invention. 本発明の第2の実施形態の人間状態モデル自動生成処理を説明するブロック図である。It is a block diagram explaining the human state model automatic generation process of the 2nd Embodiment of this invention. 本発明の第2の実施形態の人間状態モデル自動生成処理を示すフローチャートである。It is a flowchart which shows the human state model automatic generation process of the 2nd Embodiment of this invention.
 以下、本発明の実施形態について図面を用いて説明する。 Hereinafter, embodiments of the present invention will be described with reference to the drawings.
 実施の形態について、図面を用いて詳細に説明する。ただし、本発明は以下に示す実施の形態の記載内容に限定して解釈されるものではない。本発明の思想ないし趣旨から逸脱しない範囲で、その具体的構成を変更し得ることは当業者であれば容易に理解される。 Embodiments will be described in detail with reference to the drawings. However, the present invention is not construed as being limited to the description of the embodiments below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or the spirit of the present invention.
 以下に説明する発明の構成において、同一部分又は同様な機能を有する部分には同一の符号を異なる図面間で共通して用い、重複する説明は省略することがある。 In the structure of the invention described below, the same portions or portions having similar functions are denoted by the same reference numerals in different drawings, and redundant description may be omitted.
 本明細書等における「第1」、「第2」、「第3」などの表記は、構成要素を識別するために付するものであり、必ずしも、数または順序を限定するものではない。また、構成要素の識別のための番号は文脈毎に用いられ、一つの文脈で用いた番号が、他の文脈で必ずしも同一の構成を示すとは限らない。また、ある番号で識別された構成要素が、他の番号で識別された構成要素の機能を兼ねることを妨げるものではない。 In this specification and the like, notations such as “first”, “second”, and “third” are attached to identify the constituent elements, and do not necessarily limit the number or order. In addition, a number for identifying a component is used for each context, and a number used in one context does not necessarily indicate the same configuration in another context. Further, it does not preclude that a component identified by a certain number also functions as a component identified by another number.
 図面等において示す各構成の位置、大きさ、形状、範囲などは、発明の理解を容易にするため、実際の位置、大きさ、形状、範囲などを表していない場合がある。このため、本発明は、必ずしも、図面等に開示された位置、大きさ、形状、範囲などに限定されない。 The position, size, shape, range, etc. of each component shown in the drawings and the like may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. For this reason, the present invention is not necessarily limited to the position, size, shape, range, and the like disclosed in the drawings and the like.
 以下の実施例では、物資の需給情報と、人の情報を管理する人材情報から各種リスクを算出し、それらのリスクとコストから、安全かつ低コストである物資と人のロジスティクス計画を生成する。 In the following embodiment, various risks are calculated from supply and demand information of goods and human resources information managing human information, and a logistics plan of goods and people that is safe and low cost is generated from those risks and costs.
 図1は、本発明の第1の実施形態の装置の構成例を示す図である。データ管理サーバ101、ロジスティクス計画生成サーバ111、モニタリングサーバ121はネットワーク100によって接続されている。ネットワーク100とはLAN(Local Area Network)やインターネット回線である。図1では3つのサーバが連携して処理を進めるが、このサーバの分け方は、一例であって、これに限るものではない。各サーバはさらに分割されていても統合されていてもよい。 FIG. 1 is a diagram showing a configuration example of an apparatus according to the first embodiment of the present invention. The data management server 101, the logistics plan generation server 111, and the monitoring server 121 are connected by a network 100. The network 100 is a LAN (Local Area Network) or an Internet line. In FIG. 1, three servers advance the process in cooperation, but this server division method is an example and is not limited to this. Each server may be further divided or integrated.
 データ管理サーバ101は、バスによって相互に接続されたCPU(Central Processing Unit)102、出力装置103、入力装置104、メモリ105、ネットワークインターフェース106、外部記憶装置107を備える。 The data management server 101 includes a CPU (Central Processing Unit) 102, an output device 103, an input device 104, a memory 105, a network interface 106, and an external storage device 107 connected to each other via a bus.
 CPU102は、メモリ105に記憶されているプログラムを処理することによって、各種処理を実行する演算処理装置である。外部記憶装置107は、メモリ105に記憶されているプログラム本体又はメモリ105に記憶されているプログラムによって利用されるデータを格納する記憶装置である。メモリ105は、CPU102によって処理されるプログラム及び使用されるデータを格納する記憶装置である。CPU102によって処理されないプログラム及びデータは、外部記憶装置107に格納される。 The CPU 102 is an arithmetic processing unit that executes various processes by processing a program stored in the memory 105. The external storage device 107 is a storage device that stores data used by a program main body stored in the memory 105 or a program stored in the memory 105. The memory 105 is a storage device that stores a program processed by the CPU 102 and data used. Programs and data that are not processed by the CPU 102 are stored in the external storage device 107.
 メモリ105は、需要算出部203の機能を実現するプログラムを格納する。外部記憶装置107は、人事情報テーブル201、生産管理テーブル202、物資需要テーブル204、人材管理テーブル205を格納しており、また、他にロジスティクス計画生成に用いられるテーブル、例えば輸送機器データ、生産に必要な機器のデータ等を格納してもよい。 The memory 105 stores a program that realizes the function of the demand calculation unit 203. The external storage device 107 stores a personnel information table 201, a production management table 202, a material demand table 204, and a human resource management table 205. In addition, a table used for logistic plan generation, for example, transportation equipment data, production Data of necessary equipment may be stored.
 出力装置103は、例えばディスプレイなどの表示装置である。この出力装置103は、人事情報テーブル201、生産管理テーブル202、物資需要テーブル204、人材管理テーブル205それぞれの情報を表示する。また、必要に応じてその他のデータや、それらのデータの管理用インターフェース等を表示してもよい。 The output device 103 is a display device such as a display. The output device 103 displays information on the personnel information table 201, the production management table 202, the material demand table 204, and the personnel management table 205. Further, other data, an interface for managing these data, and the like may be displayed as necessary.
 入力装置104は、例えばキーボードやマウスなどの入力装置である。入力装置104を用いて、人事情報テーブル201、生産管理テーブル202、物資需要テーブル204、人材管理テーブル205の情報の追加、変更、削除を行うことが可能である。 The input device 104 is an input device such as a keyboard or a mouse. Using the input device 104, it is possible to add, change, and delete information in the personnel information table 201, production management table 202, material demand table 204, and human resource management table 205.
 ネットワークインターフェース106は、ロジスティクス計画生成サーバ111、モニタリングサーバ121及びその他の外部の計算機やモニタリング用の機器と接続し、通信するためのインターフェース装置である。 The network interface 106 is an interface device for connecting and communicating with the logistics plan generation server 111, the monitoring server 121, and other external computers and monitoring devices.
 ロジスティクス計画生成サーバ111は、バスによって相互に接続されたCPU112、出力装置113、入力装置114、メモリ115、ネットワークインターフェース116、外部記憶装置117を備える。外部記憶装置117は人間状態モデルテーブル207を格納する。メモリ115はロジスティクス計画生成部211、ロジスティクス計画設定部212の機能を実現するプログラムを格納する。 The logistics plan generation server 111 includes a CPU 112, an output device 113, an input device 114, a memory 115, a network interface 116, and an external storage device 117 connected to each other by a bus. The external storage device 117 stores a human state model table 207. The memory 115 stores programs for realizing the functions of the logistics plan generation unit 211 and the logistics plan setting unit 212.
 モニタリングサーバ121は、バスによって相互に接続されたCPU122、メモリ123、入力装置124、出力装置125、ネットワークインターフェース126、外部記憶装置127を備える。外部記憶装置127はモニタリングデータテーブル206を格納する。 The monitoring server 121 includes a CPU 122, a memory 123, an input device 124, an output device 125, a network interface 126, and an external storage device 127 that are connected to each other via a bus. The external storage device 127 stores a monitoring data table 206.
 図2は図1のシステムで行われる、ロジスティクス計画生成処理を実現するソフトウェアブロック図である。先に述べたように、3つのサーバで任意に処理を分担することができる。図2を用いてロジスティクス計画生成処理の全体的な流れを説明する。ロジスティクス計画の生成が必要になった時点で、需要算出部203は、生産管理テーブル202に格納されている今後の生産計画と人事情報テーブル201に格納されている作業員個々人の情報を基に物資と人両方の需要を算出する。 FIG. 2 is a software block diagram for realizing a logistics plan generation process performed in the system of FIG. As described above, processing can be arbitrarily shared by the three servers. The overall flow of the logistics plan generation process will be described with reference to FIG. When it is necessary to generate a logistics plan, the demand calculation unit 203 supplies the material based on the future production plan stored in the production management table 202 and the individual worker information stored in the personnel information table 201. And demand for both people.
 ロジスティクス計画の生成が必要になった時点とは、例えば、前回生成時から状況が大きく変更された時、ユーザがシステムに指示した時、生成済みの計画が対象としている期間が終了する時、等である。 When a logistics plan needs to be generated, for example, when the situation has changed significantly since the previous generation, when the user instructs the system, when the period covered by the generated plan ends, etc. It is.
 例えば、Oil&Gas分野においては、石油採掘のための油井開発の段階と、開発された油井から原油を抽出する段階では必要な物資、人が異なる。そのため、物資と人の需要は今後の生産計画と、開発する油井の性質等に応じて決定される。
また、必要な人材に対して、実際に割り当てる人の決定には既知の手法を用いる。一般に、ナーススケジューリングと呼ばれる技術では、個々人の相性やスキルの組み合わせ、休暇の取得有無等から作業担当者を決定する。人材の需要情報決定には、当該ナーススケジューリングの技術を用いても良いし、他の技術を用いても良い。
For example, in the Oil & Gas field, the necessary materials and people are different between the stage of oil well development for oil extraction and the stage of extracting crude oil from the developed oil well. Therefore, the demand for goods and people is determined according to the future production plan and the nature of the well to be developed.
In addition, a known method is used to determine a person to be actually assigned to a necessary person. In general, in a technique called nurse scheduling, a person in charge of work is determined based on a combination of individual abilities and skills, whether or not a vacation is acquired, and the like. The nurse scheduling technique may be used to determine demand information for human resources, or other techniques may be used.
 そして、算出された物資の需要は物資需要テーブル204に、人の需要は人材管理テーブル205に格納される。 Then, the calculated demand for supplies is stored in the supply demand table 204, and the demand for people is stored in the personnel management table 205.
 ロジスティクス計画生成部211は、算出された需要と、モニタリングテーブル206に格納されている各種モニタリング情報、および人間状態モデルテーブル207に格納されている人間状態モデルを用いてロジスティクス計画を生成する。 The logistics plan generation unit 211 generates a logistics plan using the calculated demand, various types of monitoring information stored in the monitoring table 206, and the human state model stored in the human state model table 207.
 複数生成されたロジスティクス計画は、ロジスティクス計画設定部212において、ユーザに提示される。そして、それらの中から選択されたロジスティクス計画が実行され、実行結果に応じて人事情報テーブル201のデータが更新される。 The plurality of generated logistics plans are presented to the user in the logistics plan setting unit 212. Then, the logistics plan selected from them is executed, and the data of the personnel information table 201 is updated according to the execution result.
 なお、本実施例では、コスト、リスク、リードタイム等の指標を用いて複数のロジスティクス計画を生成し、ユーザ側に提示することを想定しているが、個別または複数の指標から最良と判断される単一のロジスティクス計画を生成しても良い。 In this embodiment, it is assumed that a plurality of logistics plans are generated using indices such as cost, risk, and lead time and presented to the user side. A single logistics plan may be generated.
 ロジスティクス計画の選択後、人事情報テーブル201の情報が更新される。当該更新は、実行結果の内容を作業した人にフィードバックするために行われる。例えば、ロジスティクスコストを低減するために、残業を行った人に対する査定を上げる等、である。 After selecting the logistics plan, the information in the personnel information table 201 is updated. The update is performed in order to feed back the contents of the execution result to the person who worked. For example, to reduce the logistics cost, raise the assessment for those who have worked overtime.
 ロジスティクス計画生成部211は、基準計画生成部221および安定生産リスク算出部222、リスク調整部223、計画評価部224から構成される。基準計画生成221は、さらに物資配送計画生成部231と人材配送計画部232から構成される。また、安定生産リスク算出部222は、操業リスク算出部233と、配送リスク算出部234から構成される。さらに、操業リスク算出部233は人間行動リスク算出部235、故障リスク算出部236から構成され、配送リスク算出部234は欠品リスク算出部237と需要変動リスク算出部238から構成される。 The logistics plan generation unit 211 includes a reference plan generation unit 221, a stable production risk calculation unit 222, a risk adjustment unit 223, and a plan evaluation unit 224. The reference plan generation 221 further includes a material distribution plan generation unit 231 and a human resource distribution plan unit 232. The stable production risk calculation unit 222 includes an operation risk calculation unit 233 and a delivery risk calculation unit 234. Further, the operation risk calculation unit 233 includes a human behavior risk calculation unit 235 and a failure risk calculation unit 236, and the delivery risk calculation unit 234 includes a shortage risk calculation unit 237 and a demand fluctuation risk calculation unit 238.
 図3は、これらの構成要素を用いてロジスティクス計画を生成するフローを示した図である。まずステップ301にて、ロジスティクス計画の対象となる期間を入力する。例えば翌月から3カ月後まで、あるいは次年度1年間分等である。本ステップはあらかじめ設定値を保持しておく等して省略してもよい。 FIG. 3 is a diagram showing a flow for generating a logistics plan using these components. First, in step 301, a period for which a logistics plan is to be input is input. For example, from the following month to 3 months later, or for the next year. This step may be omitted by holding a set value in advance.
 次にステップ302において、ステップ301で定められた計画立案期間において必要となる物資と人の需要を算出する。これは、需要算出部203の処理に該当する。そして、ステップ303からステップ308までがロジスティクス計画生成部211の処理に、ステップ309がロジスティクス計画設定部212の処理に該当する。 Next, in step 302, the demand for goods and people required in the planning period determined in step 301 is calculated. This corresponds to the processing of the demand calculation unit 203. Steps 303 to 308 correspond to processing of the logistics plan generation unit 211, and step 309 corresponds to processing of the logistics plan setting unit 212.
 まず、ステップ303では、物資需要テーブル204およびモニタリングテーブル206より得られるデータから物資配送計画を生成する。これは、従来からの配送計画生成手法と同等であり、特許文献2でも開示されている。なお、モニタリングテーブル206に含まれる天候のデータ、すなわち天気、波浪、風速といった外的要因を考慮して算出してもよい。当該処理は物資配送計画生成部231の処理に該当する。 First, in step 303, a material delivery plan is generated from data obtained from the material demand table 204 and the monitoring table 206. This is equivalent to the conventional delivery plan generation method, and is also disclosed in Patent Document 2. The calculation may be performed in consideration of external factors such as weather data included in the monitoring table 206, that is, weather, waves, and wind speed. This processing corresponds to the processing of the material delivery plan generation unit 231.
 次にステップ304において、人材管理テーブル205およびモニタリングテーブル206のデータを用いて配送計画に輸送対象の人を割り当てる。本割り当てでは、物資輸送に用いられる輸送機器のスケジュールを一切変更せずに、人を追加で輸送可能な分だけ割り当てることを示す。物資輸送のスケジュールだけでは配送できない人に対しては、別の輸送機器を新規に割り当てる。輸送機器はヘリや輸送船等をコストとリードタイム等を考慮して設定する。これは、人材配送計画生成部232の処理に該当する。 Next, in step 304, a person to be transported is assigned to the delivery plan using the data of the personnel management table 205 and the monitoring table 206. This allocation indicates that people will be allocated as much as they can be transported without changing the schedule of transport equipment used for goods transportation. For those who cannot deliver only with the schedule of goods transportation, new transportation equipment is newly allocated. Transport equipment is set for helicopters and transport ships in consideration of cost and lead time. This corresponds to the processing of the personnel delivery plan generation unit 232.
 そして、ステップ305において、安定生産リスクを算出し、計画を調整する。これは安定生産リスク算出部222、およびリスク調整部223の処理に該当する。調整された計画は、ステップ306において調整によるコスト変化が算出され、ステップ307において評価される。ステップ307において、総コストが調整前より低減されたと判断された場合、ステップ309を、そうでなければステップ308を実行する。評価基準は総コストではなく、安定生産リスクや、リードタイムでもよい。 In step 305, the stable production risk is calculated and the plan is adjusted. This corresponds to the processing of the stable production risk calculation unit 222 and the risk adjustment unit 223. In the adjusted plan, the cost change due to the adjustment is calculated in step 306 and evaluated in step 307. If it is determined in step 307 that the total cost has been reduced from before the adjustment, step 309 is executed, otherwise step 308 is executed. Evaluation criteria may be stable production risk and lead time, not total cost.
 ステップ308では、配送計画生成、人の割り当てに関するパラメータを変更して再度ステップ303を実行する。これは、ステップ303、およびステップ304で利用されるパラメータを変更し、調整前の基準となる計画を再生成することを意味する。ステップ306およびステップ307、ステップ308は計画評価部224の処理に該当する。 In step 308, parameters relating to delivery plan generation and assignment of people are changed, and step 303 is executed again. This means that the parameters used in step 303 and step 304 are changed, and the plan that becomes the reference before adjustment is regenerated. Step 306, step 307, and step 308 correspond to the processing of the plan evaluation unit 224.
 ステップ309では、人事情報の更新を行う。これは、ロジスティクス計画設定部212の処理に該当する。ユーザ側が実行するロジスティクス計画を選択し、その選択結果を用いて人事情報テーブル201に格納されているデータが更新される。なお、当該更新は、選択後でなくとも、実際にロジスティクス計画が遂行された後でもよい。 In step 309, the personnel information is updated. This corresponds to the processing of the logistics plan setting unit 212. The logistics plan executed by the user is selected, and the data stored in the personnel information table 201 is updated using the selection result. The update may not be after the selection but after the logistics plan is actually executed.
 図4は人事情報テーブル201の一例を示す図である。人事情報テーブル201には、作業員や従業員個々人を示すレコードが格納されている。典型的な例としては、企業の人事部門が管理する従業員のデータであり、従業員を識別す情報、資格、給与、各種手当、処遇などの情報を含む。Person ID(Person IDentifier)401は、当該レコードを一意に識別するための識別子であり、一意に識別可能であればどのような表現でもよい。 FIG. 4 is a diagram showing an example of the personnel information table 201. The personnel information table 201 stores records indicating workers and individual employees. A typical example is employee data managed by the personnel department of a company, and includes information for identifying the employee, information such as qualification, salary, various benefits, and treatment. The Person ID (Person IDentifier) 401 is an identifier for uniquely identifying the record, and any expression may be used as long as it can be uniquely identified.
 Job402は個々人の職種を識別するための識別子であり、文字列であってもよいし、他のテーブルに格納されたデータを参照する何かしらの識別子でもよい。Base Salary403は従業員の月額給与額を、Assessment Value404は給与査定のために使われる値であり、ここでは次回賞与時に特別付与される額を示している。これらの値は、人事評価を行うための値であり、金額以外の別の形式でもよい。 Job 402 is an identifier for identifying an individual's job type, and may be a character string or some identifier that refers to data stored in another table. Base Salary 403 is an employee's monthly salary amount, and Assessment Value 404 is a value used for salary assessment, and here indicates an amount that is specially given at the next bonus. These values are values for performing personnel evaluation, and may be in other forms other than the amount.
 Good Compatibility405、Bad Compatibility406はそれぞれ、個人同士の相性を示し、Good Compatibility405が相性の良い人を、BadCompatibility406が相性の悪い人を示す。これらの値は、上述した需要算出部203の処理において、チーム編成を決定する際に相性の良し悪しを判断するために用いられる。そのため、相性の良し悪しを判断できれば別の形式でもよい。 Good Compatibility 405 and Bad Compatibility 406 indicate compatibility between individuals, Good Compatibility 405 indicates good compatibility, and Bad Compatibility 406 indicates poor compatibility. These values are used in the above-described processing of the demand calculation unit 203 to determine whether the compatibility is good or not when determining the team formation. Therefore, another format may be used as long as compatibility can be determined.
 Person ID401がP1である個人のレコードを例にすれば、当該個人はクレーンを操作するCrane Operatorであり、給料は月額4,000ドルである。また、次回賞与時には400ドル加算されることが決定されている。そして、当該個人はPerson ID401がP2である個人と相性がよく、P4である人物と相性が悪いことを示している。 Taking an individual record with Person ID 401 of P1, for example, the individual is a Crane Operator who operates a crane, and the salary is $ 4,000 per month. Also, it is determined that $ 400 will be added at the next bonus. The individual has a good compatibility with the person whose Person ID 401 is P2, and has a bad compatibility with the person whose Person is P4.
 図4では、給与と相性の2点を示しているが、所有資格や年齢、教育歴等の他の情報を格納してもよい。 FIG. 4 shows two points of salary and compatibility, but other information such as ownership qualification, age, educational history, etc. may be stored.
 図5は、生産管理テーブル202の一例を示す図である。生産管理テーブル202の各レコードには、操業現場ごとの各フェーズおよびそれらの開始、終了日時と付随事項が格納される。 FIG. 5 is a diagram illustrating an example of the production management table 202. Each record of the production management table 202 stores each phase for each operation site and their start and end dates and associated items.
 Phase ID(Phase IDentifier)501は各レコードを一意に識別するための識別子であり、一意に識別可能であればどのような形式でもよい。Target502は各レコードが何を対象としているかを示す識別子であり、文字列や他のテーブルに格納されている識別子などでもよい。Phase503は活動のフェーズを表す識別子であり、フェーズが表現できればどのような形式でもよい。 A Phase ID (Phase IDentifier) 501 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified. The target 502 is an identifier indicating what each record is targeted for, and may be a character string or an identifier stored in another table. Phase 503 is an identifier indicating the phase of the activity, and may be in any format as long as the phase can be expressed.
 Bdate504,Edate505はそれぞれ当該フェーズの開始日時、終了日時を表現する。図中では“年月日-時分秒”の形式で記載されているが、他の表現形式でもよいし、また年月日のみや、時間までの表記でもよい。 Bdate 504 and Edit 505 represent the start date / time and end date / time of the phase, respectively. In the figure, it is described in the format of “year / month / day-hour / minute / second”, but other expression formats may be used, or only the date / year or the time may be used.
 Remarks506は、当該フェーズに付随する情報を記載している。情報の内容が表現できれば文字列以外の形式でもよい。また、複数のカラムで表現されていてもよい。 Remarks 506 describes information associated with the phase. A format other than a character string may be used as long as the contents of information can be expressed. Moreover, it may be expressed by a plurality of columns.
 たとえば、Platform1に着目すると、2つのフェーズPh1およびPh2が予定されており、その内容がそれぞれWell TestingとWell Developmentであることがわかる。また、Ph1は2014年11月13日の19時に開始され、2014年12月13日の19時に終了する予定であることが表現されている。そして、Ph2は2014年12月13日の19時に開始され、2015年1月30日の19時に終了する予定であることが示されている。 For example, paying attention to Platform1, it can be seen that two phases Ph1 and Ph2 are scheduled, and the contents are Well Testing and Well Development, respectively. Further, it is expressed that Ph1 starts at 19:00 on November 13, 2014 and ends at 19:00 on December 13, 2014. It is shown that Ph2 starts at 19:00 on December 13, 2014 and ends at 19:00 on January 30, 2015.
 本実施例では、後述の物資需要テーブルや人材管理テーブルは、生産管理テーブル202が定義する全体スケジュールの制約条件に従って、作成されるものとする。例えば、図5のPh1のスケジュールは、2014年11月13日の19時に開始され、2014年12月13日の19時に終了する予定であるため、このスケジュールに合わせて物資や人材が供給されることになる。 In this embodiment, the material demand table and the human resource management table, which will be described later, are created in accordance with the constraints of the overall schedule defined by the production management table 202. For example, since the schedule of Ph1 in FIG. 5 is scheduled to start at 19:00 on November 13, 2014 and end at 19:00 on December 13, 2014, supplies and human resources are supplied in accordance with this schedule. It will be.
 図6は物資需要テーブル204の一例を示した図である。物資需要テーブル204には、各操業現場に対し、いつまでにどこから何を運ぶかという情報が格納されている。 FIG. 6 is a diagram showing an example of the material demand table 204. In the material demand table 204, information on where and what from what to carry to each operation site is stored.
 Demand ID(IDentifier)601は各レコードを一意に識別するための識別子であり、一意に識別可能であればどのような形式でもよい。また、Name602は物資の名称を表現しており、同様の内容を表現可能であれば文字列以外の形式でもよい。 Demand ID (IDentifier) 601 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified. Name 602 represents the name of the goods, and may be in a form other than a character string as long as similar contents can be represented.
 Qty(Quantity)603は、当該物資の必要な数または量を示しており、物資の内容が薬品であった場合は量である等、物資に対応した形式で表現される。Source604、Destination605は当該物資が運ばれる際の始点と終点を表している。Delivery date606は当該配送の締め切りを表現しており、同様の内容を表現できれば他の形式でもよい。 Qty (Quantity) 603 indicates a necessary number or amount of the material, and is expressed in a format corresponding to the material, such as an amount when the content of the material is a medicine. Source 604 and Destination 605 represent the start and end points when the goods are transported. The Delivery date 606 expresses the deadline of the delivery, and other formats may be used as long as the same contents can be expressed.
 例えば、Demand ID601がD1のレコードは、Port1からPlatform1までパイプを一本運ぶ必要があることを示している。またその締め切りが2014年12月13日の21時であることを表現している。 For example, a record whose Demand ID 601 is D1 indicates that it is necessary to carry one pipe from Port1 to Platform1. Moreover, it expresses that the deadline is 21:00 on December 13, 2014.
 図6で示した物資需要テーブル204は、物資の需要と配送に関する最低限の情報のみ格納しているが、他の情報、例えば配送コストや値段、配送に関する注意点等を格納してもよい。 The material demand table 204 shown in FIG. 6 stores only minimum information related to the demand and delivery of goods, but other information such as delivery cost and price, precautions regarding delivery, and the like may also be stored.
 図7は人材管理テーブル205の一例を示す図である。人材管理テーブル205には、各レコードには、人の勤務予定が格納されている。勤務予定の情報とは、例えば、誰が、何時、何処にいるかを示す情報である。Shift ID(Shift IDentifier)701は各レコードを一意に識別するための識別子であり、一意に識別可能であればどのような形式でもよい。 FIG. 7 is a diagram showing an example of the human resource management table 205. In the human resource management table 205, a person's work schedule is stored in each record. The work schedule information is, for example, information indicating who is at what time and where. A Shift ID (Shift IDentifier) 701 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
 Work begin702およびWork end703はそれぞれ各個人の勤務開始日時と勤務終了日時を示す。また、Location704は勤務場所を示す。 Work begin 702 and work end 703 respectively indicate the work start date and time and the work end date and time of each individual. Further, Location 704 indicates a work place.
 例えば、P1のシフトは2014年12月13日の17時に開始され、2014年12月26日の17時に終了する予定である。また、勤務場所はPlatform1であることを示している。 For example, the shift of P1 starts at 17:00 on December 13, 2014 and is scheduled to end at 17:00 on December 26, 2014. Further, it is indicated that the work place is Platform1.
 図7で示した人材管理テーブル205は勤務表として備えるべき最低限のデータのみを提示しているが、それ以外のデータ、たとえば必要装備や詳細なスケジュールを提示してもよい。 The human resource management table 205 shown in FIG. 7 presents only the minimum data that should be provided as a work schedule, but other data such as necessary equipment and a detailed schedule may be presented.
 図8はモニタリングテーブル206の一例を示す図である。各レコードはモニタリング対象の状態を示しており、例えば個人や輸送機器、天候等を示している。Monitor ID(IDentifier)801は各レコードを一意に識別するための識別子であり、一意に識別可能であればどのような形式でもよい。 FIG. 8 is a diagram illustrating an example of the monitoring table 206. Each record indicates the status of the monitoring target, and indicates, for example, an individual, transportation equipment, weather, or the like. A Monitor ID (IDentifier) 801 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified.
 Update Time802は最後に対象の情報を取得した日時である。Target803はモニタリングの対象を示し、Location804はモニタリング対象の所在を示している。Remarks805は上述以外の情報を示すものであり、例えば個人であれば労働状況や傷病状況、天候であれば天気、機器であれば機器の疲労状況や稼働コストが格納されている。これらの情報は単一のカラムでなくとも、複数のカラムや別のテーブルに格納してもよい。また、各レコードは過去のモニタリング結果もすべて保持しているが、最新の結果のみを保持してもよい。 Update Time 802 is the date and time when the target information was last acquired. Target 803 indicates a monitoring target, and Location 804 indicates the location of the monitoring target. Remarks 805 indicates information other than those described above, and stores, for example, labor status and sickness status for individuals, weather for weather, and fatigue status and operating cost of devices for equipment. These pieces of information may be stored in a plurality of columns or another table, instead of a single column. Each record also holds all past monitoring results, but only the latest results may be held.
 図9は計画調整の処理を示すフローチャートであり、ステップ305に相当する。ステップ901において、輸送機器の出発および到着時刻の時間変更および人の勤務開始、終了時間の変更により、低コストの輸送機器へ調整可能な箇所を検出する。ステップ902では、ステップ901で検出された調整可能な箇所すべてに対し、ステップ903からステップ905を繰り返す。計画調整可能箇所の例は図10にて述べる。 FIG. 9 is a flowchart showing the plan adjustment process, which corresponds to step 305. In step 901, a location that can be adjusted to a low-cost transport device is detected by changing the time of departure and arrival times of the transport device and changing the start and end times of the person. In Step 902, Steps 903 to 905 are repeated for all the adjustable portions detected in Step 901. An example of the place where the plan can be adjusted is described with reference to FIG.
 ステップ903では、配送リスクを算出し、ステップ904では、操業リスクを算出する。そして、ステップ905では、算出された配送リスクと操業リスクから安定生産リスクを算出する。これらリスクの算出方法の一例は図11、図12にて述べる。 In step 903, a delivery risk is calculated, and in step 904, an operation risk is calculated. In step 905, a stable production risk is calculated from the calculated delivery risk and operation risk. An example of these risk calculation methods will be described with reference to FIGS.
 ステップ906では、変更後の安定生産リスクが安定閾値以下となる箇所に対し、配送機器の種類、時間の変更および、従業員の勤務時間変更を行う。ステップ906において、調整の対象となる箇所が複数存在する場合、計算機シミュレーション等により、調整可能箇所が最多、あるいはコストの合計値が最低等、望ましい指標により調整可能箇所を探索してもよい。 In step 906, the type and time of the delivery device and the working hours of the employee are changed for the portion where the stable production risk after the change is equal to or less than the stability threshold. In step 906, when there are a plurality of locations to be adjusted, the locations that can be adjusted may be searched by a desired index such as the maximum number of locations that can be adjusted or the lowest total cost value by computer simulation or the like.
 図10は、計画調整可能箇所の一例を示した図である。ここでは例示のため、Port1とPlatform1間でのロジスティクス計画およびPlatform1での勤務計画を対象とする。状況1001は、変更前、すなわち、ステップ303で作成された調整前の基準計画を示す。また、状況1001の例は、物資情報テーブル204、人材情報テーブル205の情報を表している。具体的な例としては、Port1は本土の港湾であり、Platform1は洋上プラットフォームである。すなわち、例示のスケジュールは鉄道やバスなどではなく、船や飛行機等のスケジュール上不確定要素を有する計画である。 FIG. 10 is a diagram showing an example of a place where the plan can be adjusted. Here, for the sake of illustration, a logistics plan between Port1 and Platform1 and a work plan in Platform1 are targeted. The situation 1001 shows the reference plan before the change, that is, the adjustment plan created in Step 303. An example of the situation 1001 represents information in the material information table 204 and the human resource information table 205. As a specific example, Port 1 is a mainland port, and Platform 1 is an offshore platform. That is, the exemplary schedule is not a railroad or a bus, but a plan having uncertain elements such as a ship or an airplane.
 状況1001では、Port1からヘリH1および輸送船V1を用いた配送計画が組まれている。すなわち、ヘリH1により、人P4の交代要員である人P1を運ぶ計画と、輸送船V1により、Platform1の操業に必要な物資を運ぶ計画である。 In the situation 1001, a delivery plan using the helicopter H1 and the transport ship V1 is set up from Port1. That is, the plan is to carry the person P1 who is the substitute for the person P4 by the helicopter H1, and the plan to carry the materials necessary for the operation of the Platform 1 by the transport ship V1.
 ヘリH1は、2014年12月13日の15時にPort1から出発し、2014年12月13日の16時にPlatform1に到着する。ヘリH1は、2014年12月13日の17時に勤務終了する人P4の交代要員である人P1を運ぶ。そして、勤務交代後、人P4をPort1まで運ぶ。この時、ヘリH1は、2014年12月13日18時にPlatform1より出発し、2014年12月13日の19時にPort1に到着する。 Helicopter H1 departs from Port 1 at 15:00 on December 13, 2014 and arrives at Platform 1 at 16:00 on December 13, 2014. The helicopter H1 carries a person P1 who is a substitute for the person P4 who finishes working at 17:00 on December 13, 2014. And after work shift, the person P4 is carried to Port1. At this time, the helicopter H1 departs from Platform 1 at 18:00 on December 13, 2014, and arrives at Port 1 at 19:00 on December 13, 2014.
 輸送船V1は、Demand ID601がD1であるパイプを運ぶことを想定しており、2014年12月13日21時にPlatform1までに到着する必要がある。そのため、2014年12月13日の17時にPort1を出発し、2014年12月13日の20時にPlatform1に到着する。そのあと、5時間かけて物資の積み下ろしおよび不要物資の受け取りを行い、2014年12月14日の1時にPlatform1を出発する。そして、2014年12月14日の6時にPort1に戻る。 The transport ship V1 is supposed to carry a pipe whose Demand ID 601 is D1, and needs to arrive by Platform 1 on December 13, 2014 at 21:00. Therefore, Port 1 departs at 17:00 on December 13, 2014, and arrives at Platform 1 at 20:00 on December 13, 2014. After that, loading and unloading of goods and receiving of unnecessary goods are performed over 5 hours, and the platform 1 is departed at 1 o'clock on December 14, 2014. And it returns to Port1 at 6:00 on December 14, 2014.
 状況1001の例の場合、人P4、人P1の交代時間とパイプD1の配送予定時刻が異なり、単一の輸送機器で運ぶことはできない。また、単純に勤務時間を後ろにずらした場合、疲労等により従業員が操作ミスをするリスクが大きくなる。また、配送を前倒しにした場合、配置場所が未確保であったり、その後の消費計画に影響を与えたりする。そのため、単純な時間調整は各種のリスクを内包するため困難である。 In the case of the example of the situation 1001, the change time of the person P4 and the person P1 is different from the scheduled delivery time of the pipe D1, and cannot be carried by a single transport device. In addition, if the working hours are simply shifted backward, the risk that the employee will make operational mistakes due to fatigue or the like increases. Moreover, when delivery is brought forward, the arrangement location is not secured or the subsequent consumption plan is affected. Therefore, simple time adjustment is difficult because it contains various risks.
 本実施例における計画調整を行った結果を状況1002に示す。当該計画調整は図11および図12で示す各種リスクを考慮した行われた結果である。計画調整の結果、パイプD1および人P1を輸送船V1で同時に運ぶ計画に調整されている。これにより、ヘリH1を用いるコストを低減することが可能になる。 一方で、人P4の勤務時間が2014年12月13日20時までとなり、3時間の残業が追加されることとなっている。当該残業中の操作ミス等のリスクを、人間行動リスクとして図11に示す人間状態モデルを用いて算出する。 The result of the planned adjustment in this example is shown in the situation 1002. The planned adjustment is a result of considering various risks shown in FIGS. 11 and 12. As a result of the plan adjustment, the plan is adjusted so that the pipe D1 and the person P1 are simultaneously carried by the transport ship V1. Thereby, it becomes possible to reduce the cost of using the helicopter H1. On the other hand, the working hours of person P4 will be until 20:00 on December 13, 2014, and overtime will be added for 3 hours. A risk such as an operation error during overtime is calculated as a human behavior risk using the human state model shown in FIG.
 本実施例では、この調整は生産管理テーブル202が定める制約条件の範囲内で行うものとする。また、調整が物理的に可能かどうかは、モニタリングテーブル206を参照して判定する。また、調整は従うべき各種の法令や規則の範囲内で行うものとする。例えば、作業員の作業時間を規制する法令や、輸送船の運転速度を規制する法令がある場合は、その条件を満たす範囲で調整を行う。 In this embodiment, this adjustment is performed within the range of the constraint conditions defined by the production management table 202. Whether adjustment is physically possible is determined by referring to the monitoring table 206. Adjustments shall be made within the scope of various laws and regulations to be followed. For example, if there is a law that regulates the working hours of workers or a law that regulates the operating speed of a transport ship, adjustments are made within a range that satisfies the conditions.
 図11は、人間状態モデルの一例を示した図である。図11中では、グラフの形式で書かれているが、数式や、機械学習で得られたモデルであってもよい。モデル1101、モデル1102はそれぞれCrane Operator、Ballast Control Operatorの人間状態リスクモデルを示す。このようなモデルは、業務内容やエラーの種類ごとに、統計的なデータに基づいて作成することができる。また、従業員ごとに過去の労働実績のデータを用いて生成し、個人ごとに準備してもよい。業務内容やエラーの内容の定義は任意であり、細分化してもよいし、ある程度纏めて定義してもよい。ここでは職種ごとに人間状態モデルを定義しているが、個人ごとや年齢ごと等、人間の操作ミス発生リスクを算出できるのであれば、既知のヒューマンエラーのモデル等を用いてもよい。 FIG. 11 is a diagram showing an example of a human state model. In FIG. 11, it is written in the form of a graph, but it may be a mathematical expression or a model obtained by machine learning. A model 1101 and a model 1102 respectively represent human condition risk models of Crane Operator and Ballast Control Operator. Such a model can be created on the basis of statistical data for each type of business and type of error. Alternatively, it may be generated for each employee using data of past work results and prepared for each individual. The definition of business content and error content is arbitrary and may be subdivided or may be defined to some extent. Here, a human state model is defined for each occupation, but a known human error model or the like may be used as long as it is possible to calculate the risk of occurrence of human operation errors such as individual or age.
 図12は各種リスクを用いた安定生産リスク算出方法の一例である。 FIG. 12 shows an example of a stable production risk calculation method using various risks.
 配送リスク算出式1201は、ここでは簡単のため、天候による要因および当初予定との差分である時間差分から配送リスク、すなわち配送が滞り欠品を引き起こすリスクを算出する方法の一例である。欠品リスクとは、例えば人材または物資の配送遅延により、生産管理テーブル202が定義する全体スケジュールを実行できなくなる可能性である。ここでは、一例として配送リスク算出式1201でこのリスクを定義することにし、値が所定値となった場合に欠品リスクが許容できなくなると擬制する。天候要因係数は天候により異なり、例えば晴れであれば0.5、雨であれば2等と天候によって値が与えられる。配送調整係数は値域を調整するための定数である。 The delivery risk calculation formula 1201 is an example of a method for calculating a delivery risk, that is, a risk of delivery stagnation and a missing item from a factor due to weather and a time difference that is a difference from the initial schedule, for simplicity. The shortage risk is a possibility that the entire schedule defined by the production management table 202 cannot be executed due to, for example, a delivery delay of human resources or supplies. Here, as an example, this risk is defined by the delivery risk calculation formula 1201 and assumes that the shortage risk becomes unacceptable when the value reaches a predetermined value. The weather factor coefficient varies depending on the weather. For example, the value is 0.5 depending on the weather, 2 if raining, and the like. The delivery adjustment coefficient is a constant for adjusting the range.
 操業リスク算出式1202は、操作ミスが引き起こされる人間行動リスクを算出する式であり、図11で示した人間状態モデルから算出される。操業リスクは、例えば、人の作業中に操作ミスが発生する可能性である。ここでは、モデル1101を用い、各種情報を係数として導入した例を示している。傷病状態係数、直前状態係数、活動履歴係数は、それぞれ個人のけがや病気等の傷病状態、睡眠や休息等の直近の活動、直近の作業の所要時間によって決定される係数である。また、行動調整係数は操業リスクの地域を調整するための定数である。図11で説明したように、モデルは作業内容や作業者、操作ミスの種類に依存して定められる。 The operation risk calculation formula 1202 is a formula for calculating a human behavior risk that causes an operation mistake, and is calculated from the human state model shown in FIG. The operational risk is, for example, the possibility of an operational error occurring during human work. Here, an example in which various types of information are introduced as coefficients using the model 1101 is shown. The injury and illness state coefficient, the immediately preceding state coefficient, and the activity history coefficient are coefficients that are determined by an individual's injury and illness state, the latest activity such as sleep and rest, and the time required for the latest work. The behavior adjustment coefficient is a constant for adjusting the area of operational risk. As described with reference to FIG. 11, the model is determined depending on the work content, the operator, and the type of operation error.
 安定生産リスク算出式1203は、配送リスク算出式1201および操業リスク1202を確率値として扱うことで算出される。ここでは、図10で示した例をもとに算出しており、天候要因係数を2、配送調整係数を4、傷病状態係数を0.5、直前状態係数を1、活動履歴係数を1、行動調整係数を3として算出している。 The stable production risk calculation formula 1203 is calculated by treating the delivery risk calculation formula 1201 and the operation risk 1202 as probability values. Here, the calculation is based on the example shown in FIG. 10, the weather factor coefficient is 2, the delivery adjustment coefficient is 4, the sickness condition coefficient is 0.5, the immediately preceding condition coefficient is 1, the activity history coefficient is 1, The behavior adjustment coefficient is calculated as 3.
 状況1001から状況1002に変更する場合、配送を1時間前倒しし、従業員P4の勤務時間を3時間延長することで調整可能になる。その時の時間差分は、それぞれ1と3である。これらの値を用いて安定生産リスクを算出した場合、約0.280となる。当該値が、あらかじめ設定された安定閾値以下であれば、当該調整は可能であると判断される。 When changing from the situation 1001 to the situation 1002, it is possible to adjust the delivery by bringing the delivery time one hour ahead and extending the working hours of the employee P4 by three hours. The time differences at that time are 1 and 3, respectively. When these values are used to calculate the stable production risk, it is about 0.280. If the value is equal to or less than a preset stability threshold, it is determined that the adjustment is possible.
 なお、ここでは配送リスクには欠品リスクを、操業リスクには操作ミス等の行動に関する人間行動リスクを考慮しているが、他の各種リスクを考慮してもよい。例えば、需要変動により配送物資の需要が急に変動する需要変動リスク(例えば物資が予定どおり調達できない可能性や、突発的に物資が必要になる可能性)、経年劣化またはメンテナンスサイクルの超過により操業中に機器が破損することで交換部品が必要になる故障リスク、組み合わせたチームが予定通りの能力を発揮しない人間関係リスク等、様々なリスクを考慮してもよい。また、これらのリスク算出には既知の方法を用いてもよい。 In this case, the shortage risk is considered as the delivery risk, and the human behavior risk related to the behavior such as the operation mistake is considered as the operation risk, but other various risks may be considered. For example, demand fluctuation risk that demand of delivery goods suddenly fluctuates due to demand fluctuation (for example, possibility that supplies can not be procured as planned or suddenly necessary supplies), deterioration due to aging or maintenance cycle exceeded Various risks may be taken into consideration, such as a failure risk that a replacement part is required due to damage to the equipment, and a human relationship risk that the combined team does not perform as planned. Moreover, you may use a known method for these risk calculation.
 これらのリスクを用いて安定生産リスクを算出する方式の一つは、図12で示した方式同様、各種リスクを確率値として算出し、いずれかのリスクにより事故が発生する確率を算出する方式であるが、他の方式を用いてもよい。 One of the methods for calculating stable production risk using these risks is the same as the method shown in FIG. 12, in which various risks are calculated as probability values, and the probability that an accident will occur due to one of the risks is calculated. However, other methods may be used.
 例えば、人間行動リスクと故障リスク、欠品リスクと需要変動リスクの4つを用いる場合、人間行動リスクと故障リスクから、機器操作時に故障または操作ミスが発生する確率を操業リスクとし、欠品リスクと需要変動リスクから必要な物資が必要な時間と場所に無い確率を配送リスクとし、その操業リスク、配送リスクのいずれかが生じる確率を安定生産リスクとする。需要変動リスクには経済学の、故障リスクには予兆診断等の既知の技術を用いて算出する。 For example, when using human behavior risk and failure risk, shortage risk and demand fluctuation risk, the probability that a failure or operation error will occur when operating the equipment is determined from the human behavior risk and failure risk. The probability that the necessary goods are not in the required time and place from the demand fluctuation risk is defined as the delivery risk, and the probability that either the operation risk or the delivery risk occurs is defined as the stable production risk. Demand fluctuation risk is calculated using economics, and failure risk is calculated using known techniques such as predictive diagnosis.
 本調整の結果、勤務時間の延長や短縮が行われる場合がある。そのような延長や短縮に対し、その後の賞与や特別報酬で報いる等するために、人事情報にそのような情報を加えるのがステップ309で行われる処理である。例えば、図10で示した調整の結果、人P4は労働時間が延長される。そのような場合、残業手当や後の報酬に反映させるため、人事情報テーブル201のAssessment Value404を増加させる。 * As a result of this adjustment, working hours may be extended or shortened. The processing performed in step 309 adds such information to the personnel information in order to reward such extension or shortening with a subsequent bonus or special reward. For example, as a result of the adjustment shown in FIG. 10, the working time of the person P4 is extended. In such a case, the Asset Value 404 in the personnel information table 201 is increased in order to be reflected in overtime pay and later rewards.
 このような人事情報の更新は、単純に金額の増加以外にも、代休の取得や、後の休暇を長くすること等でもよい。 Such personnel information may be updated by simply acquiring a substitute holiday or lengthening a later holiday in addition to simply increasing the amount.
 図13は、ロジスティクス計画設定部212で利用されるGUI(Graphical User Interface)である。ウィンドウ1301は、ロジスティクス計画生成部211に必要なパラメータの入力および生成された計画の表示を行う。計画対象期間1302は、ロジスティクス計画を生成する期間を指定する入力フィールドである。また、安定閾値1303はステップ906で用いられる値を設定する。これらの値はユーザに入力させてもよいし、自動設定した値を表示するだけでもよい。 FIG. 13 shows a GUI (Graphical User Interface) used in the logistics plan setting unit 212. A window 1301 inputs parameters necessary for the logistics plan generation unit 211 and displays the generated plan. The planning target period 1302 is an input field for designating a period for generating a logistics plan. The stability threshold 1303 is set to a value used in step 906. These values may be input by the user, or the automatically set values may be displayed.
 コスト重み1304およびリスク重み1305は、ユーザに対して調整結果を提示するときに用いられるパラメータである。Plan No1306から始まるテーブルは、ロジスティクス計画生成部211が生成した複数の計画の一部を提示している。Plan No1306は各レコードを一意に識別するための識別子であり、一意に識別可能であればどのような形式でもよい。コスト1307は、生成された計画に要するコストを示し、平均安定生産リスク1308は、リスク調整部223が調整した全箇所の安定生産リスクを平均した値を示す。 Cost weight 1304 and risk weight 1305 are parameters used when presenting the adjustment result to the user. The table starting with Plan No. 1306 presents a part of a plurality of plans generated by the logistics plan generation unit 211. Plan No. 1306 is an identifier for uniquely identifying each record, and may be in any format as long as it can be uniquely identified. The cost 1307 indicates the cost required for the generated plan, and the average stable production risk 1308 indicates a value obtained by averaging the stable production risks at all locations adjusted by the risk adjustment unit 223.
 パフォーマンス1309はコスト重み1304、コスト1307、リスク重み1305、平均安定生産リスク1308から算出される値であり、ユーザが複数のプランから実行するプランを選択するために用いられる。例えば、Plan No1306が1のレコードでは、平均安定生産リスク1308にリスク重み1305を乗じた値から、コスト1307にコスト重み1304を乗じた値を割ることで算出している。 The performance 1309 is a value calculated from the cost weight 1304, the cost 1307, the risk weight 1305, and the average stable production risk 1308, and is used for the user to select a plan to be executed from a plurality of plans. For example, in the record whose Plan No. 1306 is 1, calculation is performed by dividing the value obtained by multiplying the average stable production risk 1308 by the risk weight 1305 and the cost 1307 by the cost weight 1304.
 コスト130は、例えば図10に示すロジスティクス計画を基に、輸送手段や作業ごとに時間単価を予め定めておくことにより計算することができる。 The cost 130 can be calculated by, for example, predetermining the unit price per hour for each means of transportation and work based on the logistics plan shown in FIG.
 グラフ表示1310は生成された各プランのトレードオフ関係を明示するためのグラフである。グラフ表示1310中には、コスト1307、平均安定生産リスク1308、パフォーマンス1309それぞれの値が連続的に示され、各プランの位置を図示している。これにより、ユーザが生成されたプランがコスト優位かリスク優位かを容易に把握することが可能になる。 The graph display 1310 is a graph for clearly showing the trade-off relationship of each generated plan. In the graph display 1310, the values of the cost 1307, the average stable production risk 1308, and the performance 1309 are successively shown, and the positions of the plans are illustrated. As a result, it is possible to easily grasp whether the plan generated by the user is cost advantage or risk advantage.
 本例では、コストと平均安定生産リスクを示したが、リードタイムや調整箇所の数を選択指標として表示してもよい。 In this example, the cost and average stable production risk are shown, but the lead time and the number of adjustment points may be displayed as selection indicators.
 プラン詳細1311は、選択されたプランの内容の一部と、当該プランの実行により変更される人事情報の一部を示している。人事情報の全部または一部は、アクセスするユーザのIDで判別される閲覧権限により、非表示にすることもできる。Vehicle1312は輸送機器のIDを、Target1313は輸送対象のIDを示す。Begin1314およびEnd1315はそれぞれ輸送開始日時、輸送終了日時を示す。Source1316およびDestination1317は、輸送元および輸送先を示す。 The plan details 1311 indicate a part of the contents of the selected plan and a part of personnel information changed by execution of the plan. All or a part of the personnel information can be hidden by the viewing authority determined by the ID of the accessing user. Vehicle 1312 indicates the ID of the transport device, and Target 1313 indicates the ID of the transport target. Begin 1314 and End 1315 indicate the transportation start date and time and the transportation end date and time, respectively. Source 1316 and Destination 1317 indicate a transportation source and a transportation destination.
 例えば、輸送機器V1は、従業員P4、およびパイプD1を輸送するため、Port1を2014年12月13日の16時に出発し、同日の19時にPlatform1に到着する。その後、従業員P4、パイプD1を降ろし、従業員P1を乗せる。そして、2014年12月14日の0時にPlatform1を出発し、同日の5時にPort1に到着することを示している。 For example, in order to transport the employee P4 and the pipe D1, the transport device V1 departs Port1 at 16:00 on December 13, 2014 and arrives at Platform1 at 19:00 on the same day. Thereafter, the employee P4 and the pipe D1 are lowered, and the employee P1 is put on. Then, it is shown that Platform1 departs at 0 o'clock on December 14, 2014 and arrives at Port 1 at 5 o'clock on the same day.
 更新後人事情報テーブル1318は、人事情報テーブル201の一部であり、選択されたプランが実行された場合に更新されるレコードとその内容を示している。 The post-update personnel information table 1318 is a part of the personnel information table 201, and shows a record updated when the selected plan is executed and its contents.
 以上のGUIにより、指定された期間を対象として、ロジスティクス計画を生成し、コストやリスクの観点から、実行する計画をユーザに選択させることが可能になる。また、選択したプランの詳細をユーザがあらためて改変するような機能を持たせてもよい。さらに、以上のような機能が実現されるのであれば、異なるインターフェースを用いたり、他の入出力を追加したりしてもよい。 With the above GUI, it is possible to generate a logistics plan for a specified period and allow the user to select a plan to be executed from the viewpoint of cost and risk. In addition, the user may have a function of modifying the details of the selected plan. Furthermore, if the above functions are realized, a different interface may be used or another input / output may be added.
 以上に示した本発明の第1の実施形態によれば、各種リスクを考慮した上で、人と物両方を考慮した、低リスクかつ低コストであるロジスティクス計画を立案することができる。 According to the first embodiment of the present invention described above, it is possible to make a low-risk and low-cost logistics plan that considers both people and things in consideration of various risks.
 前述の第1の実施形態では、人間状態モデルをあらかじめ作成しておく必要があった。第2の実施形態では、モニタリングデータから人間状態モデルを自動生成する形態を説明する。 In the above-described first embodiment, it is necessary to create a human state model in advance. In the second embodiment, a form in which a human state model is automatically generated from monitoring data will be described.
 図14は、本発明の第2の実施形態の構成例を示す図である。なお、以下では図1と同様の構成要素には同一の符号を付して重複する説明を適宜省略する。 FIG. 14 is a diagram showing a configuration example of the second embodiment of the present invention. In the following description, the same components as those in FIG.
 第2の実施形態は、前述の第1の実施形態(図1参照)の各構成要素に加えて、人間状態モデル自動生成部1401を有する。人間状態モデル自動生成部1401は、モニタリングデータテーブル206のデータを用いて人間状態モデルを自動生成する。 The second embodiment includes a human state model automatic generation unit 1401 in addition to the components of the first embodiment (see FIG. 1) described above. The human state model automatic generation unit 1401 automatically generates a human state model using data in the monitoring data table 206.
 図15は、本発明の第2の実施形態の人間状態モデル自動生成を説明するブロック図である。図15を用いて、人間状態モデル自動生成の全体的な流れを説明する。なお、以下では図2と同様の構成要素には同一の符号を付して重複する説明を適宜省略する。 FIG. 15 is a block diagram illustrating human state model automatic generation according to the second embodiment of this invention. The overall flow of the human state model automatic generation will be described with reference to FIG. In the following description, the same components as those in FIG.
 人間状態モデルの自動生成処理は、人事情報テーブル201の更新や、ユーザ入力、その他テーブルの更新をトリガとして実行される。当該トリガが発生した後、人間状態モデル自動生成部1401は、学習対象となるモニタリングデータを抽出する。そして、当該データの中でも作業行動に関連するデータをモニタリングデータテーブル206から取得し、人間状態モデルを生成して人間状態モデルテーブル207に格納する。 The automatic generation process of the human state model is executed with the update of the personnel information table 201, the user input, and the update of other tables as a trigger. After the trigger is generated, the human state model automatic generation unit 1401 extracts monitoring data to be learned. Then, among the data, data related to work behavior is acquired from the monitoring data table 206, a human state model is generated, and stored in the human state model table 207.
 図16は人間状態モデル自動生成処理のフローチャートである。まず、ステップ1601において、モニタリングテーブル206から、対象となる個人のデータで、かつRemarks805のActionにWorkが含まれるデータを抽出する。 FIG. 16 is a flowchart of the human state model automatic generation process. First, in step 1601, data that is personal data to be processed and whose Work is included in the action of Remarks 805 is extracted from the monitoring table 206.
 そして、ステップ1602において、抽出したデータ中のRemarks805のStatusごとに分類する。ステップ1603では、抽出したStatusごとにステップ1604およびステップ1605を繰り返す。 In step 1602, classification is performed for each status of Remarks 805 in the extracted data. In step 1603, step 1604 and step 1605 are repeated for each extracted status.
 ステップ1604では、対象の作業の所要時間を、勤務開始時刻からUpdate time802までとし、所要時間の平均から標準偏差2倍以上大きい作業は失敗、それ以外は作業成功として失敗、成功をカウントする。そして、ステップ1605において、失敗を1、成功を0の出力とし、所要時間を入力としたシグモイド関数を推定し、推定結果の関数を人間状態テーブル207に格納する。 In step 1604, the time required for the target work is set from the work start time to Update time 802, and work that is more than twice the standard deviation from the average of the time required fails, and otherwise, the work success is counted as failure. In step 1605, a sigmoid function is estimated with failure as 1 and success as 0 and the required time as input, and the estimated result function is stored in the human state table 207.
 以上に示した本発明の第2の実施形態によれば、第1の実施形態の利点に加え、個々人の人間状態モデルを自動生成し、人間状態モデル作成の手間を削減することが可能となる。 According to the second embodiment of the present invention described above, in addition to the advantages of the first embodiment, it is possible to automatically generate a human state model of an individual and reduce the labor of creating a human state model. .
 以上、本発明の各実施形態について説明したが、上記各実施形態は本発明の適用例の一つを示したものであり、本発明の技術的範囲を上記各実施形態の具体的構成に限定する趣旨ではない。本発明は上記した実施形態に限定されるものではなく、様々な変形例が含まれる。例えば、ある実施例の構成の一部を他の実施例の構成に置き換えることが可能であり、また、ある実施例の構成に他の実施例の構成を加えることが可能である。また、各実施例の構成の一部について、他の実施例の構成の追加・削除・置換をすることが可能である。 Each embodiment of the present invention has been described above. However, each of the above embodiments shows one application example of the present invention, and the technical scope of the present invention is limited to the specific configuration of each of the above embodiments. It is not the purpose. The present invention is not limited to the embodiments described above, and includes various modifications. For example, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace the configurations of other embodiments with respect to a part of the configurations of the embodiments.
 以上の構成は、単体のコンピュータで構成してもよいし、あるいは、入力装置、出力装置、処理装置、記憶装置の任意の部分が、ネットワークで接続された他のコンピュータで構成されてもよい。 The above configuration may be configured by a single computer, or may be configured by another computer in which any part of the input device, output device, processing device, and storage device is connected via a network.
 本実施例中、ソフトウエアで構成した機能と同等の機能は、FPGA(Field Programmable Gate Array)、ASIC(Application Specific Integrated Circuit)などのハードウエアでも実現できる。そのような態様も本願発明の範囲に含まれる。 In this embodiment, functions equivalent to those configured by software can also be realized by hardware such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit). Such an embodiment is also included in the scope of the present invention.
101 データ管理サーバ
111 ロジスティクス計画生成サーバ
121 モニタリングサーバ
201 人事情報テーブル
202 生産管理テーブル
203 需要算出部
204 物資需要テーブル
205 人材管理テーブル
206 モニタリングテーブル
207 人間状態モデルテーブル
211 ロジスティクス計画生成部
212 ロジスティクス計画設定部
DESCRIPTION OF SYMBOLS 101 Data management server 111 Logistics plan production | generation server 121 Monitoring server 201 Personnel information table 202 Production management table 203 Demand calculation part 204 Material demand table 205 Human resource management table 206 Monitoring table 207 Human condition model table 211 Logistics plan production | generation part 212 Logistics plan setting part

Claims (15)

  1.  データ入力部、データ出力部、入力されたデータの処理を行う処理部を有する計算機で実行されるロジスティクス計画生成方法であって、
     前記処理部は、
     物資の需給情報および人の人材情報からロジスティクス基準計画を生成する基準計画生成部と、
     安定生産リスクを計算する安定生産リスク算出部と、
     前記ロジスティクス基準計画に対し、前記安定生産リスクに基づいて計画変更可能な部分を抽出し、当該変更可能な範囲で計画を調整しロジスティクス計画を生成する、リスク調整部と、
     を備えることを特徴とするロジスティクス計画生成方法。
    A logistic plan generation method executed by a computer having a data input unit, a data output unit, and a processing unit for processing input data,
    The processor is
    A base plan generation unit for generating a logistics base plan from supply and demand information of goods and human resource information;
    A stable production risk calculator that calculates stable production risk;
    A risk adjustment unit that extracts a plan changeable portion based on the stable production risk with respect to the logistics standard plan, adjusts the plan within the changeable range, and generates a logistics plan;
    A logistics plan generation method characterized by comprising:
  2.  請求項1に記載のロジスティクス計画生成方法であって、
     前記計算機が、
     前記調整されたロジスティクス計画を用いて、前記人の人事情報を更新する、人事情報更新部、
     を備えることを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 1,
    The calculator is
    Using the adjusted logistics plan, the personnel information update unit that updates the personnel information of the person,
    A logistics plan generation method characterized by comprising:
  3.  請求項1に記載のロジスティクス計画生成方法であって、
     前記安定生産リスク算出部は、
     操業上の事故リスクを算出する操業リスクと、物資配送上のリスクを算出する配送リスクの少なくとも一つから前記安定生産リスクを算出し、
     前記操業リスクは、
     前記人の勤務状況を入力として将来の事故発生確率を算出する人間状態モデルから算出される行動リスクと、
     前記操業に用いる稼働機器の経年劣化またはメンテナンスサイクルから算出される故障リスクとの、
     どちらか一方または両方から算出される、
     ことを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 1,
    The stable production risk calculation unit
    Calculating the stable production risk from at least one of an operation risk for calculating an operational accident risk and a delivery risk for calculating a material delivery risk;
    The operational risk is
    Behavioral risk calculated from a human condition model that calculates the probability of a future accident occurrence using the work status of the person as input,
    With the risk of failure calculated from aging or maintenance cycle of operating equipment used for the operation,
    Calculated from one or both,
    A logistics plan generation method characterized by that.
  4.  請求項3に記載のロジスティクス計画生成方法であって、
     前記人間状態モデルは、
     前記勤務状況として、前記人の勤務シフト、傷病状況、オペレーションの所要時間のうち少なくとも一つを入力として将来の事故発生確率を算出するものである、
     ことを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 3,
    The human state model is
    As the work status, calculating the future accident occurrence probability by inputting at least one of the work shift of the person, the sickness status, and the time required for the operation,
    A logistics plan generation method characterized by that.
  5.  請求項3に記載のロジスティクス計画生成方法であって、
     前記配送リスクは、
     前記ロジスティクス計画の実行に用いられる輸送機器のカタログ値、天候予測、および波浪予測のうち少なくとも一つを用いて配送遅延確率を算出する欠品リスクと、
     将来の需要変動から算出される需要変動リスクとの、
     どちらか一方または両方から算出される、
     ことを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 3,
    The delivery risk is
    The shortage risk for calculating the delivery delay probability using at least one of the catalog value of the transport equipment, weather forecast, and wave forecast used for execution of the logistics plan,
    With demand fluctuation risk calculated from future demand fluctuation,
    Calculated from one or both,
    A logistics plan generation method characterized by that.
  6.  請求項3に記載のロジスティクス計画生成方法であって、
     前記計算機が、
     前記作成されたロジスティクス計画の内容および当該計画の安定生産リスクの表示データを生成する、
     ことを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 3,
    The calculator is
    Generating display data of contents of the created logistics plan and stable production risk of the plan;
    A logistics plan generation method characterized by that.
  7.  請求項3に記載のロジスティクス計画生成方法であって、
     前記人間状態モデルは、
     前記人の過去の労働実績のデータを用いて生成された、個々の人に対応した複数のモデルを含む、
     ことを特徴とするロジスティクス計画生成方法。
    A logistics plan generation method according to claim 3,
    The human state model is
    A plurality of models corresponding to individual persons, generated using the past work performance data of the person,
    A logistics plan generation method characterized by that.
  8.  データ入力部、データ出力部、入力されたデータの処理を行う処理部を有するロジスティクス計画生成システムであって、
     前記処理部は、
     物資の需給情報および人の人材情報からロジスティクス基準計画を生成する基準計画生成部と、
     安定生産リスクを計算する安定生産リスク算出部と、
     前記ロジスティクス基準計画に対し、前記安定生産リスクに基づいて計画変更可能な部分を抽出し、当該変更可能な範囲で計画を調整しロジスティクス計画を生成する、リスク調整部と、
     を備えることを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system having a data input unit, a data output unit, and a processing unit for processing input data,
    The processor is
    A base plan generation unit for generating a logistics base plan from supply and demand information of goods and human resource information;
    A stable production risk calculator that calculates stable production risk;
    A risk adjustment unit that extracts a plan changeable portion based on the stable production risk with respect to the logistics standard plan, adjusts the plan within the changeable range, and generates a logistics plan;
    A logistics plan generation system characterized by comprising:
  9.  請求項8に記載のロジスティクス計画生成システムであって、
     前記計算機が、
     前記調整されたロジスティクス計画を用いて、前記人の人事情報を更新する、人事情報更新部、
     を備えることを特徴とするロジスティクス計画生成システム。
    The logistics plan generation system according to claim 8,
    The calculator is
    Using the adjusted logistics plan, the personnel information update unit that updates the personnel information of the person,
    A logistics plan generation system characterized by comprising:
  10.  請求項8に記載のロジスティクス計画生成システムであって、
     前記安定生産リスク算出部は、
     操業上の事故リスクを算出する操業リスクと、物資配送上のリスクを算出する配送リスクの少なくとも一つから前記安定生産リスクを算出し、
     前記操業リスクは、
     前記人の勤務状況を入力として将来の事故発生確率を算出する人間状態モデルから算出される行動リスクと、
     前記操業に用いる稼働機器の経年劣化またはメンテナンスサイクルから算出される故障リスクとの、
     どちらか一方または両方から算出される、
     ことを特徴とするロジスティクス計画生成システム。
    The logistics plan generation system according to claim 8,
    The stable production risk calculation unit
    Calculating the stable production risk from at least one of an operation risk for calculating an operational accident risk and a delivery risk for calculating a material delivery risk;
    The operational risk is
    Behavioral risk calculated from a human condition model that calculates the probability of a future accident occurrence using the work status of the person as input,
    With the risk of failure calculated from aging or maintenance cycle of operating equipment used for the operation,
    Calculated from one or both,
    A logistics plan generation system characterized by that.
  11.  請求項9に記載のロジスティクス計画生成システムであって、
     前記人間状態モデルは、
     前記勤務状況として、従業員の勤務シフト、傷病状況、オペレーションの所要時間のうち少なくともいずれか一つを入力として将来の事故発生確率を算出するものである、
     ことを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system according to claim 9,
    The human state model is
    As the work status, the future accident occurrence probability is calculated by inputting at least one of the work shift of the employee, the sickness status, and the time required for the operation,
    A logistics plan generation system characterized by that.
  12.  請求項10に記載のロジスティクス計画生成システムであって、
     前記配送リスクは、
     前記ロジスティクス計画の実行に用いられる輸送機器のカタログ値、天候予測、および波浪予測のうち少なくとも一つを用いて配送遅延確率を算出する欠品リスクと、
     将来の需要変動から算出される需要変動リスクとの、
     どちらか一方または両方から算出される、
     ことを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system according to claim 10,
    The delivery risk is
    The shortage risk for calculating the delivery delay probability using at least one of the catalog value of the transport equipment, weather forecast, and wave forecast used for execution of the logistics plan,
    With demand fluctuation risk calculated from future demand fluctuation,
    Calculated from one or both,
    A logistics plan generation system characterized by that.
  13.  請求項10に記載のロジスティクス計画生成システムであって、
     前記リスク調整部は、
     シミュレーションにより前記安定生産リスクが安定閾値以下となるように調整箇所を探索し設定する、
     ことを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system according to claim 10,
    The risk adjustment unit
    Search and set adjustment points so that the stable production risk is below the stability threshold by simulation,
    A logistics plan generation system characterized by that.
  14.  請求項10に記載のロジスティクス計画生成システムであって、
     前記計算機が、
     前記作成されたロジスティクス計画の内容および当該計画の安定生産リスクの表示データを生成する、
     ことを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system according to claim 10,
    The calculator is
    Generating display data of contents of the created logistics plan and stable production risk of the plan;
    A logistics plan generation system characterized by that.
  15.  請求項11に記載のロジスティクス計画生成システムであって、
     前記人間状態モデルは、
     前記人の過去の労働実績のデータを用いて生成された、個々の人に対応した複数のモデルを含む、
     ことを特徴とするロジスティクス計画生成システム。
    A logistics plan generation system according to claim 11,
    The human state model is
    A plurality of models corresponding to individual persons, generated using the past work performance data of the person,
    A logistics plan generation system characterized by that.
PCT/JP2015/056847 2015-03-09 2015-03-09 Logistics plan generation method and system WO2016143037A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/056847 WO2016143037A1 (en) 2015-03-09 2015-03-09 Logistics plan generation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/056847 WO2016143037A1 (en) 2015-03-09 2015-03-09 Logistics plan generation method and system

Publications (1)

Publication Number Publication Date
WO2016143037A1 true WO2016143037A1 (en) 2016-09-15

Family

ID=56878830

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/056847 WO2016143037A1 (en) 2015-03-09 2015-03-09 Logistics plan generation method and system

Country Status (1)

Country Link
WO (1) WO2016143037A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112348422A (en) * 2019-08-13 2021-02-09 北京京东振世信息技术有限公司 Information generation method and device
EP4080432A1 (en) * 2021-04-23 2022-10-26 Fujitsu Limited Information processing device, information processing method, and information processing program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1153680A (en) * 1997-08-06 1999-02-26 Mitsubishi Electric Corp Transportation plan generating device
JP2001322591A (en) * 2000-03-09 2001-11-20 Japan Drilling Co Ltd Excavating work support ship and excavating work support method
US20060206387A1 (en) * 2005-03-11 2006-09-14 Oracle International Corporation Transportation planning with multi-level firming
JP2014130468A (en) * 2012-12-28 2014-07-10 Mitsubishi Heavy Ind Ltd Production and transportation planning device, production and transportation planning method, program, and recording medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1153680A (en) * 1997-08-06 1999-02-26 Mitsubishi Electric Corp Transportation plan generating device
JP2001322591A (en) * 2000-03-09 2001-11-20 Japan Drilling Co Ltd Excavating work support ship and excavating work support method
US20060206387A1 (en) * 2005-03-11 2006-09-14 Oracle International Corporation Transportation planning with multi-level firming
JP2014130468A (en) * 2012-12-28 2014-07-10 Mitsubishi Heavy Ind Ltd Production and transportation planning device, production and transportation planning method, program, and recording medium

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112348422A (en) * 2019-08-13 2021-02-09 北京京东振世信息技术有限公司 Information generation method and device
CN112348422B (en) * 2019-08-13 2023-11-03 北京京东振世信息技术有限公司 Information generation method and device
EP4080432A1 (en) * 2021-04-23 2022-10-26 Fujitsu Limited Information processing device, information processing method, and information processing program
US11914608B2 (en) 2021-04-23 2024-02-27 Fujitsu Limited Information processing device, information processing method, and storage medium

Similar Documents

Publication Publication Date Title
US8606624B2 (en) Risk reports for product quality planning and management
US8229791B2 (en) Methods, systems, and computer integrated program products for supply chain management
JP5697624B2 (en) Project management support system and project management support program
Wesz et al. Planning and controlling design in engineered-to-order prefabricated building systems
JP2004501447A (en) How to model maintenance systems
Krishnaiyer et al. Cloud Kanban framework for service operations management
US20160048785A1 (en) A computer implemented system and method for project controls
Lu et al. Asynchronous stochastic learning curve effects in engineering-to-order customisation processes
US20170199514A1 (en) System and methods for managing changes to a product in a manufacturing environment including a minor model relational design
US20190107815A1 (en) Data architecture and improved model object interfaces for supporting integration of multiple disparate databases useable to model availability of a fleet of vehicles
JP2018206000A (en) Production planning system, production planning method and personnel ability calculation method
WO2016143037A1 (en) Logistics plan generation method and system
US20130197952A1 (en) Product producible number calculation apparatus and computer-readable recording medium
Devaux Total Project Control: A Practitioner's Guide to Managing Projects as Investments
Shou Enhanced value stream mapping for improving turnaround process efficiency in oil and gas industry
JP2006119917A (en) Process management support system, process management support method, and process management support program
JP6695298B2 (en) Order control device
Lux et al. Business process management as basis for enterprise management systems
Kumaravadivel et al. Performance measurement and determination of optimal base stock level inventory system to improve the customer satisfaction in the Six Sigma environment
US20170199516A1 (en) System and methods for managing changes to a product in a manufacturing environment including an anytime design check
Choo Best practices in aircraft engine MRO: A study of commercial and military systems
Abreu et al. Contribution in Increasing the Design Quality in Automation Project.
Plung et al. The Practical Guide to Transforming Your Company
Stingel et al. The utilization of modeling and simulation as a supply chain management tool for a recapitalization program
Kyakulumbye et al. CHAPTER FIVE PROJECT SCOPE MANAGEMENT

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: 15884533

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15884533

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP